Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
articles:pdca-how_we_miss_shewarts_point [2021/07/10 14:13] – [The Deming Cycle] rrandall | articles:pdca-how_we_miss_shewarts_point [2021/07/10 15:06] – [A Major PDCA / PDSA Cycle Obstacle] rrandall | ||
---|---|---|---|
Line 25: | Line 25: | ||
{{ : | {{ : | ||
- | + | So how did the " | |
- | ===== The Deming Cycle (1951) ===== | + | ===== The Deming Cycle (1950) ===== |
Inspired by the " | Inspired by the " | ||
Line 66: | Line 66: | ||
{{ : | {{ : | ||
- | The PDCA cycle emphasized the prevention of error recurrence by establishing standards and the ongoing modification of those standards. Even before the PDCA cycle is employed, it is essential that the current standards be stabilized. The process of stabilization is often called the SDCA (standardize-do-check-action) cycle. | + | The PDCA cycle emphasized the prevention of error recurrence by establishing standards and the ongoing modification of those standards. Even before the PDCA cycle is employed, it is essential that the current standards be stabilized. The process of stabilization is often called the SDCA (standardize-do-check-action) cycle. |
+ | |||
+ | ===== Using the PDCA Cycle for Improvement ===== | ||
+ | |||
+ | By the 1960’s the PDCA cycle was being used in Japan as an improvement cycle and a management tool. Lilrank and Kano state in their 1989 book "//Continuous Improvement: | ||
+ | |||
+ | ===== The Deming PDSA Cycle (1986) ===== | ||
+ | |||
+ | In 1986, Deming reintroduced his " | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | In his 4-day seminars during the 1980’s, Deming presented this version. Also, he warned Western audiences that the plan, do, check, and act version | ||
+ | |||
+ | For a more detailed article on the history of PDCA / PDSA, read: {{ : | ||
+ | ===== A Major PDCA / PDSA Cycle Obstacle ===== | ||
+ | A major obstacle for users of the PDCA / PDSA Cycle concept is observed when encountering a " | ||
+ | A Technical Contradiction is a situation that emerges when an attempt to improve a certain attribute (parameter) of a system leads to an unacceptable degradation of another attribute (parameter) of the same system. | ||
+ | The Soviet inventor and science-fiction author Genrich Altshuller (1926-1998) and his colleagues, began developing the concept of TRIZ (Teoriya Resheniya Izobretatelskikh Zadatch), typically translated into English as the " | ||
+ | By 1969, Altshuller had reviewed about 40,000 patent abstracts in order to find out in what way the innovation had taken place and developed the concept of technical contradictions, | ||
+ | Lacking knowledge of TRIZ can result in a recurring exercise in futility... leading to users constantly "// | ||
+ | To learn more about TRIZ and the 40 TRIZ Principles, explore the [[https:// | ||