Kaizen Retrospective (Muda, Mura, Muri)
Toyota's lean lens for sprint retros — hunt waste, unevenness, and overload instead of vague complaints.
Free · No credit card · Guests join by link
The board
01
MUDA
What effort created no value?
02
MURA
Where did work arrive unevenly?
03
MURI
Where were people or systems overloaded?
Kaizen — Toyota's philosophy of continuous, small-step improvement — is where the modern sprint retrospective actually comes from. This template brings back the original lean vocabulary: instead of generic "what went well / what didn't" columns, it asks the team to hunt for the three classic wastes Toyota engineers were trained to spot on the factory floor.
Muda is effort that created no value — rework, gold-plating, a feature nobody used. Mura is unevenness — work arriving in unpredictable bursts instead of a steady flow. Muri is overburden — a person or system pushed past sustainable capacity. Naming a problem by its lean category, rather than just "this was annoying," tends to point straight at a fixable process cause instead of a vague mood.
When to use a Kaizen Retrospective
- Teams that keep raising the same process complaints without ever naming the root cause
- After a rough sprint with visible burnout, crunch, or last-minute scrambling (a Muri signal)
- When work feels chaotic rather than broken — Mura describes unevenness that other formats miss
- Engineering-heavy teams already comfortable with lean/Toyota Production System vocabulary
How to run a Kaizen Retrospective
- 1
Sort by the three wastes, not vibes
Ask people to write cards as concrete moments, then place each in Muda (wasted effort), Mura (uneven work), or Muri (overload) — the category alone often reframes a complaint into a process problem.
- 2
Put a number on it
Ask for a rough cost on each card: hours lost, how often it happens, how many people it hits. Numbers make the vote about impact, not about who wrote the most passionate card.
- 3
Vote on the costliest waste
Spend votes on the waste the team can reduce, weighted by the numbers on the cards.
- 4
Ask "why" before you write the action
For the top-voted card, ask why it happened, then why that happened, up to five times — Kaizen's classic root-cause technique. Retromik's Action phase has a built-in 5 Whys tool for exactly this.
- 5
Keep the action small
Kaizen means small continuous steps, not one big fix. Commit to one or two concrete, low-effort changes for next sprint rather than a sweeping overhaul — small steps are what actually stick.
Anonymous writing, voting, grouping and action items work the same as in any Retromik retro.
Example cards
What good cards look like for a software team. Specific, about the work, never about a person.
MUDA
- Writing a weekly status report nobody reads.
- Re-entering the same data in the tracker and the spreadsheet.
MURA
- Ten tickets arrived in the last two days of the sprint.
- Code reviews pile up every Friday.
MURI
- One person handled all on-call this month.
- The build server runs at full capacity every afternoon.
A 45-minute agenda
- 0–5 minExplain Muda, Mura and Muri with one example each
- 5–15 minWrite cards with a rough cost on each
- 15–20 minVote on the costliest waste
- 20–35 minRun 5 Whys on the top card
- 35–45 minAgree one or two small changes
Common mistakes
- Cards filed in the wrong column. Uneven arrival is Mura, not Muri; fix it during grouping.
- Vague cards without a cost. "Meetings are wasteful" can't be compared with anything.
- Reaching for a big fix. Kaizen is one small step at a time.
- Skipping the whys and treating the symptom.
Frequently asked questions
What do Muda, Mura, and Muri mean?
They are the three wastes from the Toyota Production System. Muda is non-value-adding effort (waste). Mura is unevenness — work that arrives in unpredictable spikes instead of a steady flow. Muri is overburden — pushing people or systems past sustainable capacity. Toyota treats all three as connected: unevenness (Mura) causes overburden (Muri), which causes waste (Muda).
How is this different from Start, Stop, Continue?
Start/Stop/Continue sorts by behaviour change; Kaizen sorts by lean waste category. The lean lens tends to surface process and workload problems (handoffs, task-switching, uneven sprint load) that behaviour-focused formats can miss, because it gives people specific vocabulary to name what "this felt off" actually was.
Do we need to know Lean or Toyota's methods to use this?
No. The column questions translate each concept into plain language — no value, uneven arrival, overload — so the format works even if nobody on the team has read about the Toyota Production System.
Why does this connect to root-cause analysis?
Kaizen's discipline is small continuous improvement grounded in the real cause, not the first plausible fix. Pairing this template with a 5 Whys pass on the top card — asking "why" repeatedly until you hit the real cause — is the classic Kaizen pattern, and it is why Retromik's Action phase includes a 5 Whys tool.
Can you combine Kaizen with a Waste Snake?
Yes, they fit well. Keep a Waste Snake during the sprint, a running log of time lost to waste, then paste its entries into Muda at the start of the retro. Retromik has a guide to running a Waste Snake.
Related templates
Start, Stop, Continue Retrospective
Start · Stop · Continue
The most actionable retro format — every column maps directly to a behaviour change.
ViewStrengths, Risks, Learnings Retrospective
Strengths · Risks · Learnings
A balanced sprint review that looks backward and forward at once — Retromik's signature format.
ViewStarfish Retrospective
More of · Less of · Keep
Calibrate instead of overhaul — dial behaviours up and down rather than starting from zero.
ViewTimeline Retrospective
Early · Mid · Late Sprint
Sorts by when it happened, not what kind — the only format built to catch narrative arcs other retros flatten into a single pile.
ViewRun a Kaizen Retrospective with your team
Create the board in under a minute, share the link, and your team joins anonymously — no accounts needed for participants.
Start free