Story
Inspired by: A3 Report (Lean) | Behavior: Kaizen (closing the gap)
The Story documents the complete arc of an improvement opportunity — from identification to value realization. It is the team's learning artifact, produced during Circle.
Anatomy
| Section | Purpose |
|---|---|
| Background | Why does this matter? Connection to Matrix objectives |
| Current Condition | What is happening now? Data and observations |
| Target Condition | Where do we want to be? Measurable gap |
| Root Cause | Why does the gap exist? (5 Whys, fishbone, etc.) |
| Countermeasures | What will we do about the root cause? |
| Action Plan | Who does what, by when? |
| Follow-Up | Did it work? Results vs. expected value |
How It Lives
- Created during Circle (Team Members identify opportunity)
- Developed iteratively through coaching conversations
- Displayed on the Board in the Check/Act columns
- Closed when value is captured and a new standard is established
Key Principle
A Story is a thinking tool, not a reporting form. The act of writing it is the act of thinking. A completed Story with empty root cause analysis is a form that was filled, not a problem that was solved.
Anti-pattern: The Bureaucratic Story
The Story is filled out like a form — all sections completed, but no real thinking behind them. The root cause is superficial. The countermeasures are obvious. The follow-up says "monitor". No one learned anything.
How to detect: All Stories look the same in structure and depth. Root cause analysis contains a single sentence. Countermeasures are actions that would have been taken anyway. The Story was written after the improvement was already implemented, as a record rather than as a thinking tool.
How to recover: Coach through questions, not templates. A good Story begins with a conversation: "What did you observe? Why do you think it happens? How do you know?" The Story captures the thinking, not the other way around.