Kanban Retrospective Template
A free, flow-based retrospective for teams that don't run sprints. Four columns — Flow, Blockers, Improvements, Actions — built around cycle time, WIP, and throughput instead of sprint ceremonies.
The template
Run this layout live with your team. Each card stays private during the writing phase, the board reveals all cards at once, and the final phase captures owned actions you can export to Markdown.
Flow
What helped work move smoothly?
Blockers
What slowed work down or stalled it?
Improvements
Small process changes worth trying.
Actions
Owned next steps with a name attached.
How a kanban retro differs from a sprint retro
Sprint retros are framed by a calendar iteration: review the last two weeks, decide what to change for the next two. Kanban retros are framed by flow. There's no iteration to look back on, so the conversation centers on the metrics that drive a continuous-delivery system.
| Aspect | Sprint retrospective | Kanban retrospective |
|---|---|---|
| Cadence | End of every sprint (1–4 weeks) | Weekly, biweekly, or after N completed items |
| Frame | What happened this sprint? | How is our flow behaving right now? |
| Key data | Sprint goal, velocity, carry-over | Cycle time, WIP, throughput, blocked time |
| Typical columns | Went well / To improve / Action items | Flow / Blockers / Improvements / Actions |
| Change horizon | Next sprint | Immediately, then observe in the metrics |
How to run a kanban retrospective
- Pull the data first. Bring a cycle-time chart, a cumulative-flow diagram, and the list of items that were blocked in the last period. Two minutes of context beats twenty minutes of guessing.
- Create the board and share the link. Pick the kanban template, name the retro (e.g. Week 47 — flow review), and paste the URL in chat. No accounts and no invites to manage.
- Write privately (5–7 minutes). Everyone drops cards into Flow, Blockers, and Improvements. Cards are masked from other participants so people commit to honest answers instead of socially safe ones.
- Reveal and group (5–10 minutes). Drag related cards together. A pattern usually shows up quickly — one repeating blocker often accounts for most of the cycle-time tail.
- Vote (2 minutes). Each person spends a small budget of votes on the items they think matter most. Sort by votes.
- Capture actions (10 minutes). For the top 2–3 items, write an action with an owner. Drop vague intentions; keep things you'll know are done by next week.
- Export to Markdown. One click drops the whole board into your wiki or issue tracker so the actions don't evaporate.
Suggested columns (and variants)
The default — Flow / Blockers / Improvements / Actions — keeps the conversation tied to the system. If your team prefers a different frame, two variants work well for kanban:
- Start / Stop / Continue — light-weight, good for teams new to retros. Pair each card with a flow data point if you can.
- What's flowing / What's stuck / Experiments / Owned next steps — more explicit about the kanban frame; useful when the team is actively tuning WIP limits or class-of-service policies.
Avoid columns that imply a sprint cadence (Went well this sprint, Sprint goal). They quietly drag the conversation back to iteration-thinking.
Discussion questions for a kanban retro
- Where did our cycle time get longer or shorter, and why?
- Which items spent the most time blocked? Was it always the same root cause?
- Are our WIP limits doing anything? Did we routinely exceed them?
- What's the smallest experiment we could run this week to improve flow?
- Did any class of work (bugs, support, big features) consistently underperform?
Tip: Resist the urge to ship five improvements at once. Kanban retros work best when you change one thing — a WIP limit, a class-of-service rule, a handoff — and watch the metrics for a week before changing the next.
How often should a kanban team retro?
Most flow-based teams run a retrospective every 1–2 weeks. Some pair it with a service-delivery review, others trigger it after a fixed number of completed items (e.g. every 20 cards). Retro often enough that the flow data is still warm and the team can connect a change to its effect.
FAQ
What is a kanban retrospective?
A continuous-improvement meeting for teams that work in flow rather than fixed sprints. It focuses on cycle time, WIP, throughput, and recurring blockers, and produces small process changes that can be applied immediately.
How is it different from a sprint retro?
A sprint retro reviews a fixed iteration. A kanban retro has no fixed cadence and looks at flow data and blockers instead of sprint goals — see the comparison table above.
What columns should it have?
Default to Flow / Blockers / Improvements / Actions. Start / Stop / Continue also works if the team is new to retros, as long as you connect cards back to flow data.
Is the template free?
Yes. Retro Harbour is free with no sign-up. Open the kanban template, share the board link with your team, and you're running.