- Purpose of this article
- A3 Thinking - The Lean Problem Solving Approach
- How to Use Cause-Effect Diagrams
- Example 1: Long Release Cycle
- Example 2: Defects Released to Production
- Example 3: Lack of Pair Programming
- Example 4: Lots of Problems
- Practical Issues: How to Create and Maintain the Diagrams
Summary: Why to use cause-effect diagrams
- Create a common understanding
- Team-based problem is extremely effective, but requires a common understanding of the problem. Cause-effect diagrams are a very practical collaboration technique.
- Identify how problems affect the business
- So that you can focus on the most important problems first and make informed decisions.
- Find root causes
- So that you can maximize the effect of your changes.
- Find vicious cycles (negative reinforcing loops)
- So that you can break them, or turn them into positive reinforcing loops (good stuff leading to more good stuff, instead of bad stuff leading to more bad stuff).