January 27, 2012
Tech Support

“gemba walk” (lean thinking term) to go to the actual place where value is added + “walkabout” (Australian aborigine) a short period of wandering bush life engaged as an occasional interruption of regular work

———————————————————————————————————-

A few years ago I someone shared this with me and I thought it was great:

Tech Support 1.0 

Dear Tech Support

Last year I upgraded from Girlfriend 7.0 to Wife 1.0.
   
I soon noticed that the new program began unexpected child processing that took up a lot of space and valuable resources. In addition, Wife 1.0 installed itself into all other programs and now monitors all other
system activity. Applications such as Poker Night 10.3, Football 5.0, Hunting and Fishing 7.5, and Racing 3.6 no longer run, crashing the system whenever selected.

I can’t seem to keep Wife 1.0 in the background while attempting to run my favorite applications I’m thinking about going back to Girlfriend 7.0, but the uninstall doesn’t work on Wife 1.0. Please help!

Thanks,
A Troubled User.! (KEEP READING)
—————————————————————————————————————

REPLY:

Dear Troubled User:
   
This is a very common problem that men complain about.

Many people upgrade from Girlfriend 7.0 to Wife 1.0, thinking that it is just a Utilities and Entertainment program.

Wife 1.0 is an OPERATING SYSTEM and is designed by its Creator to run EVERYTHING!!! It is also impossible to delete Wife 1.0 and to return to Girlfriend 70. It is impossible to uninstall, or purge the program files from the system once installed.

You cannot go back to Girlfriend 7.0 because Wife 1.0 is designed to not allow this. Look in your Wife 1.0 manual under Warnings-Alimony-Child Support. I recommend that you keep Wife1.0 and work on improving the situation. I suggest installing the background application “Yes Dear” to alleviate software augmentation.

The best course of action is to enter the command C:\APOLOGIZE because ultimately you will have to give the APOLOGIZE command before the system will return to normal anyway.

Wife 1.0 is a great program, but it tends to be very high maintenance. Wife 1.0 comes with several support programs, such as Clean and Sweep 3.0, Cook It 1.5 and Do Bills 4.2

However, be very careful how you use these programs. Improper use will cause the system to launch the program Nag Nag 9.5.

Once this happens, the only way to improve the performance of Wife 1.0 is to purchase additional software. I recommend Flowers 2.1 and Diamonds 5.0 !

WARNING!!! DO NOT, under any circumstances, install Secretary With Short Skirt 3.3. This application is not supported by Wife 1.0 and will cause irreversible damage to the operating system.

Best of luck,

Tech Support

—————————————————-

A friend of mine who read this thought that the other side of the story needed to be represented, so you can now read this:

Tech Support 2.0

 

Dear Tech Support,

 

Last year I upgraded from Boyfriend 25.3 to Husband 1.0 and noticed a distinct slow down in overall system performance - particularly in the flower and jewelry applications, which operated flawlessly under

Boyfriend 25.3.

 

In addition, Husband 1.0 uninstalled many other valuable programs, such as Romance 9.5 and Personal Attention 6.5, and then installed undesirable programs such as NFL 5.0, NBA 3.0.and Golf Clubs 4.1. Conversation 8.0 no longer runs, and Housecleaning 2.6 simply crashes the system. I’ve

tried running Nagging 5.3 to fix these problems, but to no avail.

 

What can I do?

Signed,

 

Desperate

 

———————————————————————————————————————————————————————————————-

Dear Desperate:

 

First keep in mind, Boyfriend 25.3 is an Entertainment Package, while Husband 1.0 is an Operating System.  Please enter the command: “http:// I Thought You Loved Me.htm” and try to download Tears 6.2 and don’t

forget to install the Guilt 3.0 update.

 

If that application works as designed, Husband 1.0 should then automatically run the applications Jewelry 2.0 and Flowers 3.5. But remember, over use of the above application can cause Husband 1.0 to default to Grumpy Silence 2.5, Happy Hour 7.0, or Beer 6.1.  Beer 6.1 is a very bad program that will download the Snoring Loudly Beta.

 

Whatever you do, DO NOT, I repeat, DO NOT install Mother-in-law 1.0 (it runs a virus in the background, that will eventually seize control of all your system resources). Also, do not attempt to reinstall the Boyfriend 25.3 or any previous versions.  These are unsupported applications and will crash Husband 1.0.

 

In summary, Husband 1.0 is a great program, but it does have limited memory and cannot learn new applications quickly. You might consider buying additional software to improve memory and performance. We recommend Hot Food 3.0 and Lingerie 7.7.

 

Good Luck,

Tech Support

January 26, 2012
Standard Work and PDSA

“gemba walk” (lean thinking term) to go to the actual place where value is added + “walkabout” (Australian aborigine) a short period of wandering bush life engaged as an occasional interruption of regular work

———————————————————————————————————-

I saw this diagram in a presentation and it made a lot of sense to me.
Over time people try to improve going from current practice to better using the PDSA cycle (Dr. Deming called it the Shewhart Cycle).  Others call it PDCA (substituting “check” for “study”).  I (and Dr. Deming) preferred the word “study”.
As you turn the PDSA cycle and make progress, you agree on the new way to do things (standard work) which serves as a kind of a wedge that keeps you from slipping back to the old way.
What I have noticed is that sometimes people insert another wedge (shown as black) in the diagram below.  So, progress gets stopped because some seem to believe that standard work doesn’t get adjusted as you make improvement.

January 20, 2012
Red Dots

“gemba walk” (lean thinking term) to go to the actual place where value is added + “walkabout” (Australian aborigine) a short period of wandering bush life engaged as an occasional interruption of regular work

———————————————————————————————————-

When Dr. T. makes a powerpoint presentation, he always features hand-made videos of staff applying lean thinking.  One of the most powerful videos is a VP and manager talking at a visual management board.  The VP asks “do you have any quality problems with patients?”.  The manager responds, “I’m so excited! I’ve got a red dot!”.  She points to a graph which shows that there was a problem with a patient’s medication yesterday.  On the video, they trace through the problem-solving and current state.

Dr. T points out that most of us would not be excited about showing a red dot to our boss.  We want everything to be green all the time.  On a recent visit to an organization last week, Dr. T. said, “when I look at a visual board and I don’t see about 50% red, that tells me there is a problem”.  I am reminded of the quote attributed to John Shook and his work at NUMMI plant, when the Sensai stated “no problem is a problem”.

We’ve been trained for years and years and years that green is good, red is bad.  We’ve been rewarded for green and punished for red.  I think we simply don’t believe people when they say “red is good”.  I think it’s more complex than that.

We had a gemba visit at one of our member organizations and they showed us the work they were doing on daily management boards.  Good work.  The boards showed green dots and red dots.  You could tell people were proud of the green, apologized for the red and there was not a lot of excitement about digging deeper to get to root causes.

Our team meets frequently during these gemba visits and we had a discussion at the end of the first night to review the day.  There were green dots, but also a lot of red ones.  We acknowledged that this made us uncomfortable.  We want everything to be green - all “5s” on the evals.  But we talked through the causes, what we could have done to improve the process and what we could be doing to minimize similar mistakes at upcoming gemba visits.  We too are driven by strong systems to avoid talking about red dots.

I think about the 10 guiding shingo principles and in particular “seek perfection”, “focus on process” and “embrace scientific thinking”.  It takes real effort (and humility) to realize we have red dots and to see them as something that is good - that will help us learn.  It’s easy to focus on people, not the process.

January 15, 2012
Small Problems Become Bigger Problems

“gemba walk” (lean thinking term) to go to the actual place where value is added + “walkabout” (Australian aborigine) a short period of wandering bush life engaged as an occasional interruption of regular work

———————————————————————————————————-

I had a chance to attend a meeting where Steven Spear led a discussion about systems, complexity, problem identification and problem-solving.  He used a video that I had seen before, but this time in a new way.

The video is the “First, do no harm” video that shows problems that occur with woman (Mrs. Romanov) and the bad things that happen to her and baby Romanov.  I had seen the video before and it seemed to make some useful points, but I saw new things this time.  The main reason (I think) is that we watched it backwards (and also, had Dr. Spear pointing out some important things.

The typical way the video is shown (forward) starts off with Scene #1 - initial OB appointment and scheduling of follow-up.  The “Partnership For Patient Safety” organization has some discussion guidelines that they provide for organizations to use to get the most out of watching the video.  These are the kinds of discussion questions that suggested: “do you have a policy that could help to create this particular set of circumstances in your office?”  ”how would you hand the situation that confronted this support person?” etc.

When we watched the video backwards, there was a lot more to see.  Things that were not even touched upon in the discussion document.  In particular, a receptionist made a note on a post-it note and that post-it note was then (inadvertently) picked up (and lost) by a stray chart.  Having the information on that note could have prevented a lot of bad stuff from happening down stream.

There were many other examples - too numerous to mention.  So, I need to read and re-read some of Dr. Spear’s books on this topic and also need to think about how our systems need to better identify unusual conditions and problem-solving for small things before they turn into big things.

January 12, 2012
Another Example of Non-Value-Added Activity & Lean Consumption

“gemba walk” (lean thinking term) to go to the actual place where value is added + “walkabout” (Australian aborigine) a short period of wandering bush life engaged as an occasional interruption of regular work

———————————————————————————————————-

This is a true story.  I was given a phone that I’m supposed to be able to hook up to the internet and it is going to cut down on the cost of my cell phone cost and will also make for a much better sound connection - so I am told.

I’ve been at it for 3 hours, made one trip to Best Buy to get a new router and it still will not work with my set-up at home.

Here are some photos of the process:

In their book “Lean Solutions”, Womack and Jones describe the problems of lean thinking as applied to consumption.  The problem is, we waste our free time trying to solve problems that should not be problems.

Don’t get me started with the various attempts I have made to make this work.  I will not waste one more second of my time to solve this problem.  I will not have anyone on my team waste a second of their time either.  Here’s a photo of the current state:

The phone is in the box on the bottom, the old router is on top of that and the new router is on the top.  Here they sit.

When I have some time, I might hire someone from the “geek squad” to work this out - maybe.  I don’t know why I should have to pay for someone else to waste their time on this foolishness.

I thought I had an idea that was easy and going to meet a high impact area on the PICK chart (see below).  But in reality, it has been moved to the “Kill” zone (some call this “Kibosh”). It is apparently more difficult than I thought (and more difficult than necessary) and I also believe this is a low impact idea (compared to other things I could be working on.

January 7, 2012
More Hope That There’s Hope - Improving Horizontally Across Organizations

“gemba walk” (lean thinking term) to go to the actual place where value is added + “walkabout” (Australian aborigine) a short period of wandering bush life engaged as an occasional interruption of regular work

———————————————————————————————————-

In my last post “My Old Job Had 8% Value-Added Work” I described how depressing it can be to realize that much of the activity in a process does not really add value from the standpoint of the customer (in this case, the patient).

Here’s some follow-up information and observations on what the team did the remainder of the week:

This team is comprised of representatives from two organizations: 1) a blood center (supplier), and 2) a hospital that is the customer of the blood center.  It’s hard enough to help people learn and apply lean concepts in one organization, and to do it across 2 organization is a bold experiment.  From what I saw, I think they will be successful and this will be a great example of thinking an improving horizontally, across vertical silos with organizations as well as across 2 organizations.

The team spent time describing the current state as shown in these 2 photos (I could not fit it onto one photo):

The red dots indicated steps that did not add value, and the few green dots represented value-added steps.  The team used the white slips of paper to go to gemba (where the work is actually done) and determine how long it really takes, what problems occur and how efficient the process is at this step (first-time throughput yield).

The team also described the many hand-offs (including information) in this hand-off chart:

The team then described what “ideal” would look like (no boundaries, no limitations, off into the future) and they came up with 2 ideal states that were pretty similar.

Some of the ideas were not that far fetched and are actually concepts that are currently in existence or being developed (artificial blood, chip identification, wireless communication).

The team could not stay in utopia, but described something in the future (a year away) that would be better than the present and work toward ideal.

As you can see from the last photo, the future looks better according to a number of measures.

The team then worked on some “if-then” statements or hypotheses (if we improve this, then we would expect these results).

Realizing that it was necessary to come up with some sort of prioritization, the team used a PICK chart which helps determine if an improvement idea is easy and high impact (has Potential), easy and low impact (Implement), hard and high impact (Consider) or hard and low impact (Kill or Kibosh).

This made the planning easier.  Some became projects, others were designated as rapid improvement events and others were “just do its”.  The planning calendar is shown below.

The team then got very specific about how they would go about these efforts developing these chartering documents.

So, this is impressive and important work.  I’m encouraged and I’m sure the team is as well.  I plan to keep tabs on the effort to see how it is going and share some of my own learnings and insights.

January 3, 2012
My Old Job Had 8% Value-Added-Steps

“gemba walk” (lean thinking term) to go to the actual place where value is added + “walkabout” (Australian aborigine) a short period of wandering bush life engaged as an occasional interruption of regular work

———————————————————————————————————-

This week I have the good fortune of participating on a team that is studying the blood transfusion process for elective surgical patients.  It involves staff from a blood center and a hospital.  It is a worthwhile experiment that will hopefully go well and there will be more attempts to follow with other hospitals in the area.

Today we mapped the current state and (roughly) approximated that 8% of the steps in the current process actually add value from the customer’s stand point.  8%.  My hunch is that, as we dig deeper, we’ll find that % to be even smaller.  This is a process that I used to be intimately involved in when I was a medical technologist.  Back then (30 years ago?) I realized that there had to be a better way and got started on the “quality improvement path”.

Have we seen improvement in 30 years?  Healthcare has a million broken processes that are not adding value - and they are becoming more and more expensive to maintain.   I can’t tell you that there’s hope, but I can tell you that there’s “hope that there’s hope”.

December 24, 2011
We’re Not Going To Mess With the Part of the Process That Adds Value

“gemba walk” (lean thinking term) to go to the actual place where value is added + “walkabout” (Australian aborigine) a short period of wandering bush life engaged as an occasional interruption of regular work

———————————————————————————————————-

I was on a visit to one of our member organizations with JT (Dr. T) and JB.  After some touring of the facility and seeing various (impressive) applications of lean thinking, we convened with senior leadership in a conference room.  Even though our goal is not “assessment”, people always want to know what we think.  So, we told them.

One question came from a physician - how do recommend that organizations handle the dynamic between physician autonomy and standard work?  I’ve heard that question (or something like it) before.  A big part of applying lean thinking is getting agreement from everyone who works in a process on the current best way of doing things, and then everyone does it that way, using this is the basis for continuous improvement.  The way physicians have been trained (and the way they have been allowed to practice) grants a lot of autonomy to individual physicians.

Dr. T’s response to the question was interesting.  He asked, “when you go to see a doctor, where is the value added?”  Silence.  Finally, someone offered up some measures of success - clinical outcomes, evidence-based practice, yada, yada, yada.  Dr. T asked the question again.  More silence.  Finally, he described the typical office visit to see a physician.  The waiting, and more waiting, collecting information, doing some testing, actually talking with the physician, then some follow-up steps.  Dr. T. explained that of all of the steps in the process, the part that adds value to the patient (from the patient’s perspective) are those few minutes with the doctor.  There may be other steps that are necessary or needed (under current process) - so they could be “necessary waste”.  But, from the patients perspective, only one part adds value.  ”And we’re not going to mess with that part of the process”, he added.

So, we have lots of work to do to eliminate many of the non value-added steps, and to make the “necessary waste” as efficient and effective as possible, but we’re not going to mess with that doctor-patient time (some have called this “middle ware”).

Same thinking applies in the inpatient setting, although the roles are more intertwined and it is imperative that all participants adhere to standard work - including the physicians as it relates to the overall process.  But when it comes with the doctor-patient part, we’re not going to mess with that.

December 10, 2011
Lean Thinking Applied To Research

“gemba walk” (lean thinking term) to go to the actual place where value is added + “walkabout” (Australian aborigine) a short period of wandering bush life engaged as an occasional interruption of regular work

———————————————————————————————————-

I had a very interesting visit to one of the organizations that has joined the Healthcare Value Network.  One part of their mission is research and it is doing some very impressive work indeed.  During the course of our discussions, some of the research leaders (they call themselves “investigators”) explained that they honestly did not see how lean thinking could possibly apply to their world.
After some time to tour and go the gemba to see everyone’s work (in the operations and in the research areas), I recalled this simple grid that I picked up from another visit to another organization more than a year ago.  This organization had a model for innovation and they were also doing work that might be considered the lean work (continuous improvement).  What they told me was that they do both - make things better and better - lean thinking (horizontal axis), and try to make things different - innovation (vertical axis).  They also told me that it helps to be ambidextrous in order to do both well.  This approach made sense and I have made a note to go visit them again.
So, I thought this was similar to the question that the researchers were asking at our new HVN member organization.  I modified this grid below.
Here’s the way I’m thinking about it.  The researchers are trying to build new knowledge.  They described their process for having lab meetings where they review the work, update their thinking, review their hypotheses, reform their plan and go back and try new things.  That sounds like the PDSA cycle to me.  Dr. Deming described the cycle (he called it the Shewhart cycle, named after Dr. Walter Shewhart) as a cycle for improvement, but also a cycle for learning.  The researchers have been doing this kind of work a long time and they have gotten really good at it.
The staff in the operations side of the business have started to learn and apply lean thinking.  I saw some terrific examples of this.  They identify the problem they are trying to solve, come up with ideas for making their processes work better, they gather data and study the results.  Based on what they see, they revisit their thinking (their hypothesis about how the process works and how it could work better, then they adjust their plan.  This is also the application of the PDSA cycle.
So, my advice to the company is to think about how the two arms of the company (research and operations) could collaborate and learn from each other.  Operations could see how research uses the PDSA cycle to build knowledge and they could get better and better at understanding how their systems work - not just making them work better.  I hear organizations say they want to be a “learning organization” - I think this is what they need to do.  The researchers could also learn from operations to see how their research processes and support processes could be improved.  For instance - how to do some things more efficiently and effective in order to make the best use of their grant dollars.  They could work to improve the grant-writing process, to increase the likelihood of receiving grant money.
The intent would not be to tamper with the creativity, curiosity and inventiveness of the researchers.  That would be like asking Picasso to follow a rote method for making a painting - like painting by numbers.  The intent (I think) would be how to unleash the creativity of everyone in the organization in order to add value to their ultimate customer.
I’m very interested to visit this organization down the road to see what they have done.

December 10, 2011
Guiding Principles: Flow & Pull Value, Assure Quality at the Source

“gemba walk” (lean thinking term) to go to the actual place where value is added + “walkabout” (Australian aborigine) a short period of wandering bush life engaged as an occasional interruption of regular work

———————————————————————————————————-

Operational excellence cannot be achieved through top-down directives or piecemeal implementation of tools.  Something more is required.  The Shingo Model for Operational Excellence appears to be one of the best approaches available.  It has two elements: 1) the “house” (the principles, the “what”), and 2) the “diamond” (the transformational element, which is the method - the “how”).  The “who” is everyone, beginning with top management.  Achieving operational excellence requires a widespread commitment throughout the organization to execute according to the principles of operational excellence.  I’m going to describe my understanding of the 10 guiding principles (described in the house element) two at a time and also describe how top management might use these to transform culture using the diamond element of the model.

Last time, I discussed the two principles at the base of the house element -  Focus on Process and Embrace Scientific Thinking.  This time I will describe “Flow & Pull Value” and “Assure Quality at the Source”.

Flow & Pull Value

Flow thinking is the focus on shortening lead-time from the beginning of the value stream to the end of the value stream, and on removing all barriers (waste) that impeded the creation of value and its delivery to the customer.  Flow is the best drive to make processes faster, easier, cheaper and better.  Other potential drivers such as unit cost or process variability are too narrowly focused, distorting priorities and delivering suboptimal results.  A cost focus is particularly dangerous, when it creates perverse incentives and budget manipulations incidental to actual improvement.  

An example of the problem with “focus cost” rather than “flow” can be found in some of the previous work I found myself involved in with my last employer.  The thinking seemed to follow this line of logic: Based on some traditional cost account work (basically reviewing an organization’s income and expense statement) the finance department determined that the #1 cost item in the hospital (or clinic) was “labor expense”.  So, using analytic thinking (breaking the problem into parts) it is easy to find out which departments contributed to the highest labor costs.  The next step was to calculate a ratio (labor cost/unit of service), then find out how this ratio compared to other “like” organizations (what has become known as benchmarking).  This then led to pointing out how far each department’s ratio was from the benchmark.  Actually, “pointing out” was the first step.  What really happened is pressure to reduced the number, get it closer to the desired target. The goal became get better numbers - by department - (and by any method possible).  Brian Joiner once pointed out that if people are asked to produce better numbers they have 3 choices: 1) manipulate the data, 2) manipulate the system (sub-optimize the system, or 3) improve the system which drives the results.  In my experience, we see far too much emphasis on #1 & 2.  By thinking about flow and reducing the barriers that impede flow, we are working on strategy #3 - improve the system.

Pull is the concept of matching the rate of production to the level of demand, the goal in any environment.  Yet pull is not feasible or cost-effective without the flexibility and short lead times that result from flow.

I’ve not seen the concept of “pull” widely understood and applied in healthcare.  ”Push” is a much more common approach.  For example, how do we typically operate our clinics, or our operating rooms?  There is an appointment time and the patient (typically arrives early - sometimes way early - and waits.  So we have a queue that develops (thus waiting rooms) where we create an inventory of “work in process” (non-value-added activity.  The result is a push to get the patients in to see the doctor, have the procedure, etc. What would “pull” look like?  Have the patient arrive just in enough time to be pulled to the next step quickly, with less (or no) waiting.  Each step pulls one patient from the previous step in a continuos flow manner.  No need for waiting rooms.  The result is better value to the patient, better use of everyone’s time and one outcome is lower total cost.

Flow and pull create enormous positive benefits in all aspects of any business.  Focusing on flow will lead to improvements including: better safety and morale, more consistent quality with fewer defects, increases in on-time delivery and flexibility, and lower costs, without running into the traditional trade-offs.  In addition, daily and weekly results become more consistent and predictable. 

Assure Quality at the Source

Assuring quality at the source is the combination of three principles:1) do not pass defects forward, 2) stop and fix problems, and 3) respect the individual in the process.  Defects are a source of instability and waste, so assuring quality at the source requires the establishment of processes for recognizing errors in the process itself.  Organizations must commit to stopping and fixing processes that are creating defects, rather than keeping product or services moving while planning to fix the issue later.  Proper use of the human element in the process for thinking, analysis, problem solving, and countermeasures is vital to continuous improvement. 

I see principle violated every day, and I’ve violated it myself - sometimes on purpose - so that we can all learn and work harder to apply the principle every day.  Here’s an example.  We were planning for one of the first shingo-based assessments that we offer for HVN members.  A critical first step is the preparation of a self-assessment document that the trained assessors use for baseline information.  The typical document is 30-50 pages which provides some details about the systems and activities that the organization has in place.  When I received the self-assessment document from one of our member organizations, it was 2 pages.  Clearly not enough and clearly a defect that I did not want to pass forward.  In hindsight, I could have “pulled the andon cord” and stopped the process.  But I didn’t and we all learned about the importance of a thorough self-assessment document.  On a going forward basis, I do not allow a sub-par self assessment document to proceed forward.

Supporting Principles

There are eight supporting principles related to these two guiding principles, some more strongly than others:
Stabilize processes - First, identify and remove causes of special cause variation.  Stability is a prerequisite for improvement, providing a basis for problem identification and continuous improvement.
Rely on data -  Dr. Shingo emphasized the importance of being data-driven in the pursuit of continuous improvement.
Standardize processes -  Standardization is the supporting principle behind maintaining improvement, rather than springing back to preceding practices and results.
Insist on direct observation -  ”Going to see” is the first step of the scientific method.
Focus on value stream -  Clearly understanding the value stream is the only way to improve the value delivered.
Keep in simple & visual -  Making information visual is the supporting principle that when combined with simplification solves the information defects, which are often the causes of waste.
Identify and eliminate waste -  This principle effectively engages the entire organization in the continuous improvement effort.
Integrate improvement with work -  Every employee becomes a scientist with capability to continually assess the current state of processes and improve. 

How does this relate to the “how”? - the Diamond Element

I’ll trace my understanding of how this works to affect and transform the culture in an organization.  When individual leaders (top management) in an organization think in terms of the guiding principles of “flow & pull value” and “assure quality at the source”, they will design systems that are far different than managers who are not guided by these principles.  For instance, .

The tools they would select would be used to enable the systems they designed which, in turn would drive an organizational focus on the principles.  The tools would be used to achieve results (such as ), and the results would be used to refine how the tools would be used - Plan, Do, Study, Act.  The results that are achieved would affirm the guiding principles, which would drive a focus on the results.

Over time and through the application of the guiding principles, the culture will change to one that achieves operational excellence.  Culture is the sum of the behaviors that are exhibited in the organization (from the board room to the patient bedside).  Two things drive behaviors: 1) systems and 2) what is measured.

Here’s another example.  

Guiding principles are universal truths.  They are like the laws of physics, like gravity.  They govern the consequences of those who understand them and of those who do not.  Managers who do not follow the principles of “flow & pull value” and “embrace scientific thinking” and “assure quality at the source” get and the culture they design - intentionally or unintentionally.  For instance, .  The culture they have (exhibited by the behaviors they see) is a direct result of the systems that they designed (or allowed to prevail) which are a direct result of the principles they use.

If management wants better culture and better results, they need to understand and apply the guiding principles of “flow & pull value” and “assure quality at the source”.  It’s that simple, and that hard.  To understand and apply these guiding principles means letting go of practices in the past.  Letting go of the incorrect notions we have been taught in management schools, by well-meaning managers who came before us (who were only doing their best) is what I believe Dr. Deming meant when he described the “transformation of management”.

In his 1993 book, The New Economics for Industry, Government and Education, Dr. Deming writes, “Once the individual understands the system of profound knowledge, he will apply its principles in every kind of relationship with other people.  He will have a basis for judgement of his own decisions and for transformation of the organizations that he belongs to.  The individual, once transformed, will: set an example; be a good listener, but will not compromise; continually teach other people; and help people to pull away from their current practices and beliefs and move into the new philosophy without a feeling of guilt about the past.”

Liked posts on Tumblr: More liked posts »