Kanban Retrospective Template

A kanban retrospective helps a team review how work flows, find recurring blockers, and agree on a small improvement to try. Use this free board's four columns - Flow, Blockers, Improvements, and Actions - to turn that discussion into an owned next step.

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?

Pairing cleared review queue in < 1 day
Small PRs landed without rework

Blockers

What slowed work down or stalled it?

Two items stuck in QA > 5 days
External API outage on Tuesday

Improvements

Small process changes worth trying.

Lower WIP limit on In Progress from 6 to 4
Daily 10-minute flow standup at board

Actions

Owned next steps with a name attached.

@alex: drop WIP limit before Monday
@sam: write QA handoff checklist

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.

Sprint retrospective vs. kanban retrospective at a glance.
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 WIP, throughput, work item age, cycle time; recurring blockers
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

  1. Pull the data first. Bring work in progress (WIP), throughput, work item age, and cycle time from the system that tracks your team's work. These are the four flow metrics in the Kanban Guide. A cumulative-flow diagram can help the team see where work is building up, alongside the items that were blocked in the last period.
  2. 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. Verified email access and no invites to manage.
  3. 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.
  4. 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.
  5. Vote (2 minutes). Each person spends a small budget of votes on the items they think matter most. Sort by votes.
  6. 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.
  7. Export to Markdown. One click drops the whole board into your wiki or issue tracker so the actions don't evaporate.

Turn a blocker into a measurable experiment

Use your delivery board or tracking tool to bring the flow data; the retrospective board captures the discussion and actions. At the next retro, compare the same measure over a similar period and decide whether to keep, adjust, or stop the change.

For example, if work often waits for review, record an action like this:

This is an illustrative example, not a measured result. You can record the agreed action on the board and export it to Markdown for your team's follow-up.

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:

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

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.

What flow metrics should I bring?

Bring work in progress (WIP), throughput, work item age, and cycle time from the system that tracks your team's work. These are the four flow metrics in the Kanban Guide. A cumulative-flow diagram can help the team discuss where work is building up.

FAQ

What is a kanban retrospective?

A continuous-improvement meeting for teams that work in flow rather than fixed sprints. It focuses on WIP, throughput, work item age, cycle time, 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 passwordless email access. Open the kanban template, share the board link with your team, and you're running.

Compare this with other formats in the retrospective templates guide — Sailboat, DAKI, and timeline retrospectives work well for flow-based teams too.

Choose a cadence around flow

Try a weekly 30-minute review, or review after every 20 completed items. Keep the same observation window so comparisons are useful. Bring cycle-time ranges, ageing work and blocked time; discuss changes in demand before treating a metric as a team failure.

Example: three items waited four days for review. Ask which handoff caused the queue, then try a review WIP limit of two for a fortnight. Give an owner the task of checking the oldest item daily, and compare blocked time at the next review.

Use the What Went Well template for a broader project reflection, the sprint template for a fixed iteration, or the format selection guide to choose another lens.