Kanban Retrospective Template: Flow, Blockers and One Board Change

Kanban teams don't have sprints, but they still need to stop and look at how work moves. A Kanban retrospective asks four questions: What flowed well, Where work got stuck, What waited too long, and One change to our board. It looks at the path work takes, not at who was slow, and ends with exactly one change to try until the next retro.

The four columns

Stuck vs waited. "Where work got stuck" is about a place on the board: a column always over its limit is a bottleneck. "What waited too long" is about single cards and what they waited for. A bottleneck needs a policy change; a long wait often needs one conversation with another team.

Bring the data. Retro Rabbit doesn't measure flow. Before the retro, pull a cycle-time chart and the oldest open cards from the tool that runs your board.

Where it comes from. No single person is credited with a Kanban retro format. The Kanban Guide by John Coleman and Daniel Vacanti (2025 edition) prescribes no meetings, retros included. It does name four flow metrics, and this format draws on them: WIP, throughput, work item age and cycle time.

When to use it (and when not to)

Use it when:

• your team runs on continuous flow: support, platform, ops, maintenance
• cycle time is creeping up, or cards keep aging in one column
• you changed a WIP limit or a column and want to know if it helped
• a Scrum team's stories all finish on the last day, which is a flow problem too

Pick something else when:

• the problem is morale or trust, not flow. Run Mad Sad Glad.
• one blocker needs its root cause found. Use 5 Whys.
• the team wants to set its own agenda. Try Lean Coffee.

How to run it live (30 minutes)

1. Check the last change first. Open the Previous Retro tab in the Action Items panel, and Old / Unresolved Items for anything older. Did the team keep the new WIP limit? Did cards age less?
2. Walk the board right to left. Start from Done and stop at the oldest card in each column. Then look at the cycle-time chart.
3. Write silently. Set the shared timer for six minutes. Ask for card numbers: "PAY-212 waited six days for security sign-off" beats "reviews are slow".
4. Group by place. Drag notes about the same column or handoff together.
5. Vote, then ask what the work waited for. Sort by Most Votes. For each top item, ask what the card waited for and which policy allowed it.
6. Pick one change. Write it as a board policy ("Code Review WIP limit: 2"), give it an owner, and say how you'll check it next time.

How to run it async between retros

1. After each retro: click Start New Retro so the board is open for the next period. Retro Rabbit calls each period a sprint; for you it's the time between retros.
2. As it happens: when a card has been blocked for more than a day, add a note to What waited too long with the card number and what it's waiting for. Raise it at standup too; the note is for spotting patterns.
3. Halfway: the facilitator reads Where work got stuck. If three notes point at the same column, ask for board change ideas.
4. Two days before: everyone votes.
5. The day before: the facilitator groups notes, reads the CarrotIQ Sprint Summary and pulls the chart.
6. Retro day: a 15-minute call to agree the change. Or fully async: the facilitator posts the top-voted change, and the owner updates the policy if nobody objects.

See how to run an async retrospective for the full playbook.

11 example prompts

What flowed well

1. Which card went from start to done fastest, and what made it fast?
2. Which handoff worked without any back and forth?
3. Which WIP limit actually held?

Where work got stuck 4. Which column went over its limit, and for how long? 5. Where did we start new work instead of finishing old work?

What waited too long 6. What's the oldest card on the board right now, and what is it waiting for? 7. Which waits were for people outside the team? 8. Which cards were blocked but not marked as blocked?

One change to our board 9. If we changed one WIP limit, which one, and to what? 10. Which policy is written down but not followed? 11. What one change would cut the wait we saw most?

Facilitator tip and a common pitfall

Tip: change one thing at a time. If you lower a WIP limit, add a column and change the review rule at once, you won't know which one moved cycle time. One change per retro, checked at the next, tells you what works.

Pitfall: raising the WIP limit because it keeps being hit. A limit that's always full is doing its job: it's showing you the bottleneck. Raising it hides the queue without making work move faster. Ask why work piles up there, and whether people can help clear that column before pulling new work.

How AI helps with this format

On Pro AI (and during the free trial), CarrotIQ handles the admin:

• Group names. Drag "PAY-212 waited for security sign-off" onto "login card stuck in security review" and CarrotIQ names the group, for example "Security Review Waits".
• Summaries. The Sprint Summary covers each column. Over a few retros, it shows whether the same column keeps getting stuck.
• Suggested action items. CarrotIQ Suggest drafts an action from the notes, weighting the most-voted ones. It reads your notes, not your board data, so check the draft against the cycle-time chart.

Example action items

The next retro starts with these in the Previous Retro tab. More in retrospective action items that actually get done.

Use this template in Retro Rabbit

1. Start a 14-day free trial. No card is needed.
2. Pick Kanban Flow from the format library: choose "Browse all formats" when you create your Team Room, or later in the Team Room's Settings.
3. Pick a fixed rhythm, such as every two weeks, and click Start New Retro right after each retro so the board is always open.

See pricing for plans.

Related formats

• Lean Coffee: when the team wants to set its own agenda
• 5 Whys: when one blocker needs a root cause
• Fishbone: when a delay has many possible causes
• DAKI: pruning policies that no longer help
• More formats in Kanban and lean
• All retrospective templates