Blog posts on pdsa improvement cycle

Posts selected fromManagement Blog - Engineering Blog - Investing Blog and other blogs

• Resources for Using the PDSA Cycle to Improve Results

  "Using the PDSA cycle (plan-do-study-act) well is critical to building a effective management system..."   

  continue reading: Resources for Using the PDSA Cycle to Improve Results
• Interview on PDSA, Deming, Strategy and More

  A really big key between people that use PDSA successfully and those who don’t is that the ones that do it successfully turn the cycle quickly.

  continue reading: Interview on PDSA, Deming, Strategy and More
• George Box Webcast on Statistical Design in Quality Improvement

  There is great value in creating iterative processes with fast feedback to those attempting to design and improve. Box and Deming (with rapid turns of the PDSA cycle) and others promoted this 20, 30 and 40 years ago and now we get the same ideas tweaked for startups. The lean startup stuff is as closely related to Box’s ideas of experimentation as an iterative process as it is to anything else.

  continue reading: George Box Webcast on Statistical Design in Quality Improvement
• The History and Evolution of the PDSA Cycle

  The experiment in the PDSA cycle is carried out to learn about the system in question. I like to call it the Do-the-experiment step to emphasize that doing in the PDSA cycle refers to “doing the experiment”. Otherwise people often forget that what we are doing is running an experiment to learn from.

  continue reading: The History and Evolution of the PDSA Cycle
• Cliff Norman and Ron Moen Discuss the History of the PDSA Cycle

  Ron emphasized the importance of the iterative nature of learning supported by the PDSA cycle. The importance of iterating the PDSA cycle multiple times is something that I find most organizations would benefit a great deal from. Another API consultant spoke on this importance at the 2006 Deming conference.

  continue reading: Cliff Norman and Ron Moen Discuss the History of the PDSA Cycle
• Bringing Lean Principles to Service Industries

  Iteration is very important. It is important in proper use of the PDSA cycle – many quick iterations are much better than one long slow one. And for software application development it is an excellent strategy.

  I think iteration is even more important in software application development than most other areas (for now anyway) because many stakeholders cannot visualize what they need from software. Therefore attempts to force rigid requirements up front fail...

  continue reading: Bringing Lean Principles to Service Industries
• Continually Improving Using a Focus on Delighting Customers

  A deep appreciation for the long term needs of your customers and potential customers should guide where in the system to continually improve. And my belief on how to continual improve is to create and continually improving management system with principles of experimentation (with the necessary understanding of what conclusion can be drawn from results and what cannot), an understanding of the organization as a system and respect for people as principles to be guided by to achieve continual improvement.

  Quality practices of experimentation directed at continually improving management practices and internal processes need to be completely integrated with the efforts to continual improve customer delight. Those efforts should be one process and therefore they automatically grow together.

  The success of improvements should be evaluated at the system level (outcome measures not merely efficiency measures). In process measures are useful in adding evaluating improvement and monitoring processes but the end result for the overall system must always remain the primary concern.

  continue reading: Continually Improving Using a Focus on Delighting Customers
• Should I be in the Check Phase of PDCA Daily?

  The check/study phase should be reviewing the results of the experiment done in the Do the experiment phase. "Checking" how things are going during the experiment makes sense but that isn't the check/study phase of PDSA .

  ...

  Remember one key to using the PDSA cycle is to turn through the whole cycle quickly. Daily would be exceptionally quick. Moving through the whole cycle in 2-6 weeks is more normal. Organizations successful using PDSA will quickly turn the cycle 4+ times for a specific effort (often the 2nd, 3rd... times through are much faster than the first time through).

  continue reading: Should I be in the Check Phase of PDCA Daily?
• Management is Prediction

  I believe Deming’s thoughts about prediction are most effectively put into action using the PDSA cycle. Specifically, you must predict the results in the planning phase (prior to piloting improvements). I find that this is rarely done. I don’t think the form of that prediction is critical (narrative with loose numerical guesses, precise numerical prediction…). The critical issue is making the prediction, then comparing the results to that prediction and then figuring out how your original understanding can be improved based on the new data.
  
  Learning will not only be about the specific case being examined, but also, over time, learning about your tendencies in prediction. 

  continue reading: Management is Prediction
• Using Design of Experiments

  Design of Experiments can seem complicated but at the core it is fairly simple and powerful. By applying the proper techniques it allows you to gage the effect of several variables and, very importantly, the interactions of those variables with a small number of experiments (or tests or pilots).

  George Box is a wonderful author (and friend) who can write for mangers who are not knowledgeable about statistics and statisticians. Statistics for Discovery does a good job of explaining how organizations should use experiments to improve.

  continue reading: Using Design of Experiments
• George Box Webcast on Statistical Design in Quality Improvement

  There is great value in creating iterative processes with fast feedback to those attempting to design and improve. Box and Deming (with rapid turns of the PDSA cycle) and others promoted this 20, 30 and 40 years ago and now we get the same ideas tweaked for startups. The lean startup stuff is as closely related to Box’s ideas of experimentation as an iterative process as it is to anything else.   

  continue reading: George Box Webcast on Statistical Design in Quality Improvement
• Learn From Success and Failure

  ...how the PDSA improvement cycle should be used: results are studied to increase knowledge. If results exceed expectations that should not be a reason to avoid learning. If you only study what results tell you when results are unsatisfactory you can fall into the trap that “you only learn from failure.” I guess many people only learn from failure, since that phrase is so popular, but that method leaves plenty of room for others to learn faster than you thus gaining an advantage (a more effective method of learning). Don’t wait to fail to learn.

  continue reading: Learn From Success and Failure
• Deming on Management: PDSA Cycle

  Blog posts

  • What are We Trying to Accomplish?“In The Improvement Guide, the authors add 3 questions to the PDSA cycle: What are we trying to accomplish? – How will we know that a change is an improvement? – What change can we make that will result in improvement?”
  • Keys to the Effective Use of the PDSA Improvement Cycle
  • Do the experiment

  ...

  continue reading: Deming on Management: PDSA Cycle
• Fooled by Randomness

  When people are asked to explain random variations in data they will make up special causes (that they often even believe are special causes even when they are not) but you can improve management a great deal by just stopping the requirement to “explain” common cause variation...

  Use that time instead to standardize processes. Create control charts for critical processes. Run experiments using PDSA cycle…

  continue reading: Fooled by Randomness