Part of The GreenBox Story — a standalone reference for the full series.
Every planning layer needs its own feedback loop. Sprint retros catch process issues before they compound. Quarterly retros catch strategic drift between squads. Yearly retros catch business assumptions that have quietly gone stale. Same discipline at every scale: reflect, learn, adjust. This is the one-page reference.
The retro map
| Scale | Cadence | Who’s in the room | What it catches | Format | GreenBox moment |
|---|---|---|---|---|---|
| Sprint | Fortnightly | The squad (5-8 people) | Process issues, team dynamics, technical debt, blocked work | Five-stage retro (set the stage, gather data, generate insights, decide actions, close) | Lee’s first retro in The Wrong Kind of Fast — the retro that changed everything |
| Cross-team | After incidents or quarterly | Squad leads + affected team members | Coordination failures, duplicated work, API contract surprises | Incident-triggered: show the data, find patterns, agree actions | Charlotte runs a cross-team retro after the Perth API breaks Melbourne in Two Squads, One Direction |
| Quarterly | Quarterly (Block 1 of quarterly planning day) | Squad leads + engineering leadership + product | Strategic drift between squads, theme outcomes vs expectations, planning accuracy | Each squad lead narrates what worked / surprised / would change, then review incidents | First quarterly planning day in Two Squads, One Direction |
| Yearly | Annual (part of strategy refresh) | Leadership team: founder, eng lead, mentor, squad leads | Business assumptions that turned out wrong, market shifts, what the org would do differently | Strategic reflection: “What did we believe a year ago that we now know is wrong?” | Lee names the Brisbane assumption in From Weekly Habits to Yearly Vision |
The five-stage format
Lee introduces this in the very first retro (The Wrong Kind of Fast). By The First Sprints, the team runs it without prompting. The format scales to every retro layer — only the questions and the people change.
- Set the stage — Read the Prime Directive. Check in: one word per person describing how they feel about the sprint. This takes two minutes and surfaces mood before content.
- Gather data — Silent writing on sticky notes. Each person writes as many observations as they have. Read aloud, place on the wall. No discussion yet.
- Generate insights — Cluster the notes. Find patterns. Name root causes, not symptoms. “Deployments are slow” is a symptom. “No automated pipeline” is a root cause.
- Decide what to do — Propose concrete actions. Dot vote. Pick one or two. An action without an owner and a deadline is a wish.
- Close — Each person appreciates something about a colleague. Takes sixty seconds. Ends the retro on connection rather than criticism.
The five stages remain constant. At sprint scale, “gather data” means sticky notes about the last two weeks. At quarterly scale, it means each squad lead narrating outcomes against expectations. At yearly scale, it means reviewing which assumptions from the previous strategy refresh turned out wrong. Same structure, different scope.
How retros evolve with team size
You don’t need all four retro layers on day one. Add each layer when the problems it catches start appearing.
| Team size | Retro layers needed | Why |
|---|---|---|
| 1-5 | Sprint retro only | One team, one context. Sprint retro catches everything. |
| 5-15, multiple teams | + Cross-team retro | Coordination failures are invisible to single-team retros. |
| 15-25, multiple teams | + Quarterly retro | Strategic drift between squads. Theme outcomes need review. |
| 25+ | + Yearly retro | Business assumptions compound silently. Need explicit check. |
The GreenBox team added layers as they grew: sprint retros from The First Sprints, cross-team and quarterly retros from Two Squads, One Direction, and the yearly retro in From Weekly Habits to Yearly Vision.
Common failure modes
Retros that produce no actions. “What went well / what didn’t” without “what will we do differently” is just venting. The retro must end with owned, concrete actions or it’s a waste of everyone’s time.
Actions that never get done. The retro produces actions but nobody tracks them. Next retro: same problems, same frustration, growing cynicism about the process.
Same problems every time. If the same issue appears three retros in a row, the retro isn’t failing — the team is failing to act on it. Escalate. Surface it at the next layer up. If sprint retros can’t fix it, it’s a cross-team or quarterly problem.
Skipping retros under pressure. “We don’t have time for a retro, we need to ship.” This is precisely when you need a retro most — pressure creates the process problems retros are designed to catch. Skipping the retro under pressure is like skipping the brake check before driving faster.
Wrong people in the room. Sprint retros need the squad. Cross-team retros need the squad leads. Quarterly retros need leadership. If the people who can act on the problems aren’t present, the retro is theatre — it surfaces issues that nobody in the room has the authority to fix.
The principle
Every planning layer needs its own feedback loop. The sprint retro asks “how is our process working?” The quarterly retro asks “are we pursuing the right themes?” The yearly retro asks “are we in the right business?” Same muscle. Different scope. Different cadence. All essential.
Related references
- The GreenBox Cheat Sheet — every discovery and delivery technique in one place
- The Planning Onion — every planning layer in one place
- LLMs as Thinking Partners — how the team’s LLM usage evolved
- The GreenBox Story — the full series from first idea to scaled operation