Retrospective Before Planning¶
Ritual — instantiates Cycle Phase Alignment
A ritual that places review and learning before the next planning or commitment cycle.
Learning from the last cycle is worthless to the next one if it arrives after the plan is already set. Retrospective Before Planning is the recurring ritual that guarantees the review cycle's output lands in the planning cycle's usable window — by making it an unbreakable ordering: the retrospective always happens, and always before, the next planning session locks. Its defining idea is a standing sequence rule between two cycles of the same team — review-then-plan, every time, as a fixed social convention rather than a scheduling optimization. It is not about making the review faster or the plan better in themselves; it is about the phase relationship between them: the moment planning begins, the lessons of the last cycle are already on the table in a form planning can absorb.
Example¶
A wildland fire crew works in operational periods — each shift on the line is one cycle, and before the next shift they build an assignment plan. Early in the season, planning happened first thing each morning while the previous shift's crew was already asleep; hard-won lessons ("that ridge road washed out," "the south flank spotted across the line at 3 p.m.") never reached the people writing the next plan, and the same surprises recurred.
The crew adopts the ritual: no shift plan is built until a short after-action review of the previous period is complete and its findings written into a shared sheet.[n1] The phase offset is deliberate — the review runs in the handover overlap, close enough to the shift that memory is fresh, early enough that planning hasn't started. The handoff condition is explicit: the review isn't "done" until each lesson is stated as something actionable ("pre-position water on the south flank by 2 p.m."), not just a war story. And the synchronization rule is social and absolute: planning simply does not begin without it. Within weeks, repeated surprises drop, because the plan is now built on the last shift's ground truth.
How it works¶
- Fix the order, not the clock. The rule is review-then-plan every cycle; the exact times can float, but the sequence never inverts.
- Set the offset for freshness. Run the review close enough to the finished cycle that detail survives, early enough that planning hasn't locked.
- Define "review complete" as actionable. The handoff condition is that each lesson is captured in a form planning can use — a decision or an action, not a narrative.
- Make the sequence a social convention. The ordering holds because the team treats it as non-negotiable, not because a tool enforces it.
Tuning parameters¶
- Review depth — from a five-minute plus/delta to a full facilitated after-action review. Deeper reviews surface more but eat time and can delay planning; shallow ones are cheap but skim.
- Offset tightness — how close the review sits to the end of the cycle. Tighter preserves detail but crowds the handover; looser is calmer but loses freshness to memory decay.
- Capture formality — whether lessons must be written as actions or can stay verbal. Formal capture makes the handoff durable but adds friction; informal is fast but evaporates.
- Bindingness — how absolute "no plan without review" is. Strict ordering guarantees the phase relation but can hold planning hostage to a skipped review; lenient ordering flexes but erodes.
When it helps, and when it misleads¶
Its strength is closing the learning loop in phase: the after-action review is a well-worn discipline precisely because a review whose lessons arrive too late to change the next plan is merely therapy.[n1] Placing it before planning is what converts reflection into changed behavior.
Its failure mode is the hollow ritual: the retro happens on schedule but produces war stories rather than actionable lessons, so the handoff condition is unmet and planning proceeds unchanged — the sequence is preserved, the substance is not. A classic misuse is letting the review slide after planning "just this once" when the cycle is rushed, which is exactly when its lessons matter most and exactly when the ordering breaks. The guarding discipline is to hold the sequence sacred and to insist the review's output be actionable before it counts as done — a fresh review that changes nothing about the next plan is a signal the capture step, not the ritual, has failed.
How it implements the components¶
phase_offset— sets the review to land just before planning, close enough to the finished cycle to stay fresh and early enough to still shape the plan.handoff_condition— defines "review complete" as lessons captured in actionable form, so what passes to planning is usable, not anecdotal.synchronization_rule— enforces the standing review-then-plan ordering as a fixed team convention across every cycle.
It orders two cycles but does not anchor to an irreversible funding lock via commitment_boundary and timing_authority — that is Budget–Planning Alignment — and does not gate a single handoff instance through a readiness_gate or measure it with a handoff_quality_signal, which is Handoff Readiness Check.
Related¶
- Instantiates: Cycle Phase Alignment — places one cycle's learning into the next cycle's usable window by fixing their order.
- Sibling mechanisms: Budget–Planning Alignment · Maintenance Window Coordination · Synchronized Production Cycles · Release Train Alignment · Handoff Readiness Check · School–Work Schedule Coordination · Circadian Schedule Alignment · Shared Cycle Calendar
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: Retrospective Before Planning operates by enforces the recurring review-then-plan order and a freshness-preserving offset between the two stages. That concrete deployed or enacted form is Protocol, Workflow & Routine under the frozen taxonomy.
Nearest alternative: Communication, Facilitation & Learning — Although Communication, Facilitation & Learning can support this mechanism, the frozen evidence makes its operative form the act that enforces the recurring review-then-plan order and a freshness-preserving offset between the two stages; the alternative is therefore secondary rather than defining.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Placing reflection before the next commitment cycle is characteristic of iterative management and agile practice.
Related originating lineages:
- Computer Science & Software Engineering — Software iteration rituals materially established retrospective-before-planning cadence.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: a ritual that places review and learning before the next planning or commitment cycle.
Review resolution: Both blind reviewers agree that organizational_management is the primary historical origin. Explicit reconciliation of alternate origin disagreement, encyclopedia synthesis disagreement starts from reviewer_a’s mechanism-specific evidence: Placing reflection before the next commitment cycle is characteristic of iterative management and agile practice. Reviewer A proposed alternates=computer_science, origin_mode=single_lineage, domain_reach=multi_domain, and encyclopedia_synthesis=false; reviewer B proposed alternates=systems_cybernetics, origin_mode=single_lineage, domain_reach=multi_domain, and encyclopedia_synthesis=true. The final record retains every independently supported alternate from either review (computer_science, systems_cybernetics) without an arbitrary cap, selects origin_mode=single_lineage to represent the combined lineage evidence, and keeps domain_reach=multi_domain and encyclopedia_synthesis=false from the more mechanism-specific assessment. Present-day transfer is recorded as reach and is not treated as proof of historical origin.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] The After Action Review, developed by the U.S. Army, is a structured post-event review asking what was supposed to happen, what did, and why — deliberately conducted so its findings feed the next plan rather than sit in an archive. ↩a ↩b