retro

Captures structured learnings and persists them. The OS gets smarter every time this runs. Built on Five Whys (Taiichi Ohno) for root cause analysis and Start-Stop-Continue for action planning. The combination prevents "surface retros" - where the team identifies symptoms but repeats the same mistakes with different details.

Frameworks

Five Whys - Taiichi Ohno, Toyota Production System

When something goes wrong - or unexpectedly right - ask "why?" five times. Each answer becomes the basis for the next "why." The goal is the root cause, not the symptom.

Marketing example:

• Campaign missed pipeline target by 40%. Why?
• Lead quality was poor. Why?
• We targeted too broadly. Why?
• We hadn't updated our ICP definition. Why?
• No one owns ICP maintenance. Why?
• There's no process for reviewing ICP after each cycle.
• Root cause: missing process, not bad execution.