A structured, process-focused retrospective for delivery teams whose pain lives in how the work flows — handoffs, rework, bottlenecks, dropped decisions — rather than in personal conflict.
Most retros surface complaints but rarely reach root causes or changes that stick. This board walks a team through a clear arc — find → cluster → prioritise → deep-dive → commit — and ends with written, owned actions you can actually check at the next session.
Best for: delivery / product / engineering teams of 4–12. Plan for roughly 90–160 minutes. Async-first: a little pre-work the day before, then run it live
How it works?
0 · Warm-up — a quick meme opener to set a relaxed tone.
1 · Last retro follow-up — vote done / not done on previous commitments.
2 · Flow map — drop "pain" cards onto the stages of your delivery pipeline (stages are an example — rename them to match your process).
3–4 · Cluster & vote — group similar problems and pick the top 3 to dig into.
5–7 · Problem deep dives — for each problem: state it, trace causes, generate and vote on solutions, commit to a change with an owner and a date.
8 · Action plan — collect all agreements in one table: problem, cause, change, owner, verification.
9 · Close-out — a quick emoji read on the atmosphere and a 1–5 vote on how useful the session was.
A built-in Parking Lot keeps personal or off-topic threads out of the group discussion, and a "Start here" guide plus per-block hint cards mean a first-time facilitator can run it without prep.
