Skip to content

Post-Resolution Debrief

Ritual — instantiates Tension–Resolution Cycle Design

After the cycle closes, tests whether the resolution's value was actually earned by the preceding tension — and feeds that verdict into how future cycles are spaced.

Every other mechanism here runs during the cycle. Post-Resolution Debrief runs after it — the retrospective ritual that closes the loop by asking the one question the cycle cannot answer about itself: did the tension actually earn the resolution's value, or would immediate delivery have done just as well? It is the archetype's honesty check. The debrief reconstructs what the buildup was supposed to buy, compares it against what the resolution actually delivered, judges whether the closure was clean or ragged, and — crucially — carries the verdict forward into how the next cycles are timed and spaced. Its signature is the counterfactual at its core: not "was the outcome good?" but "was the value linked to the tension we deliberately built?"

Example

A product team runs a hyped reveal — three weeks of teasers building toward a launch. After it ships, they hold a debrief. The tempting verdict is "launch-day signups were up, so the teaser worked." The debrief refuses that shortcut and runs the payoff-linkage test instead: it separates the reveal's outcome from the contribution of the buildup, looking for evidence the tension itself did work — did engagement compound over the three weeks, did the teased audience convert better than cold traffic, or would a plain announcement have produced the same bump?

It finds the buildup helped the already-warm segment but mostly annoyed cold prospects: closure was clean for insiders, ragged for everyone else. That verdict becomes an input to the spacing plan — fewer, better-targeted teaser cycles, not more. The debrief did not run the cycle; it decided whether that kind of cycle was worth repeating.

How it works

  • Reconstruct the intended payoff. State what the buildup was supposed to buy before looking at results, so the test isn't graded on a curve.
  • Run the linkage counterfactual. Ask whether the value came from the tension or would have arrived with immediate delivery — the outcome minus the buildup's real contribution.
  • Judge closure quality. Assess whether the resolution actually closed the loop — clean, satisfying, complete — or left it ragged, for whom, and why.
  • Feed the portfolio. Convert the verdict into concrete changes to how future cycles are chosen and spaced: repeat, retune, or retire this cycle type.

Tuning parameters

  • Counterfactual rigor — a gut "did it land?" versus a real comparison against a no-buildup baseline. More rigor catches self-flattery but costs measurement effort and can't always be clean.
  • Blame stance — blameless (learning) versus accountable (ownership). Blameless surfaces more honest signal; too blameless and nothing changes.
  • Cadence — debrief every cycle versus periodic sampling. Debriefing everything is thorough but heavy; sampling is lighter but misses drift.
  • Forward-coupling strength — how directly the verdict rewires the next spacing plan. Tight coupling learns fast but overfits to one cycle; loose coupling is stable but slow to correct.

When it helps, and when it misleads

Its strength is that it is the only mechanism that can tell a team its beautiful buildups are decoration — that the payoff would have landed just as well delivered straight — and it is what turns a one-off cycle into a portfolio that improves. It guards the whole archetype against its subtlest failure: cycles that feel earned but weren't.

The classic abuse is running the debrief backwards — convening it to justify the campaign already run and manufacture a success story rather than to test one, cherry-picking the metric that flatters the buildup. A debrief that can only conclude "it worked" is theatre. The discipline is to commit to the payoff-linkage question and its counterfactual before the results are in, and to let the debrief reach "the tension added nothing here" as a permitted, career-safe answer.[1]

How it implements the components

  • payoff_linkage_test — the core: the counterfactual check that the resolution's value was caused by the deliberately-built tension, not merely coincident with it.
  • closure_quality_criterion — the standard the debrief applies to judge whether the resolution actually closed the loop cleanly, and for whom.
  • cycle_portfolio_and_spacing_plan — the debrief's output: verdicts feed which cycle types to repeat, retune, or retire, and how to space them.

It does not generate or time tension (that is Harmonic Suspension and Resolution, Cadence Break and Restoration, or Adaptive Release-Timing Protocol) — it runs after resolution and audits what those produced.

Notes

The linkage counterfactual is often only roughly measurable — a clean no-buildup control rarely exists — so treat the debrief's verdict as a structured argument, not proof. Its portfolio output also assumes cycles are comparable enough to pool; when each cycle is truly one-of-a-kind, the debrief still improves judgment even if it can't build a real spacing plan.

References

[1] The After-Action Review, a structured retrospective developed by the U.S. Army, formalizes exactly this discipline: compare intended versus actual outcomes and extract lessons, with candor protected so the review can reach unflattering conclusions. Its power comes from being run to learn, not to justify. ↩