Tool 6 of 32 · an afternoon
Deadline Replay
Rebuilds the last urgent deadline from the records before anyone tells the story from memory. One question in it carries more signal than anything else in the kit.
During Reality, after the last urgent push has been reconstructed from artifacts and before anyone narrates it from memory.
What it is for
To see how the company actually operates under pressure, by rebuilding one urgent deadline from the records and answering five questions about it.
The failure it catches
How a company really operates shows itself in one urgent push: dates chosen for pressure, dependencies unresolved on day one, the top learning late, and the response to the miss being addition instead of subtraction.
Why it works
Rebuilding the timeline from records before memory speaks stops the company from grading its own story. The records cannot be managed the way a recollection can, and one question in the five, what happened after the miss, carries more signal than a month of meetings.
How to run it
- Take the last urgent deadline. Rebuild its timeline from the tickets, the commits, the notes and the calendar before anyone tells you the story from memory.
- Then fill only the gaps the records cannot, with people who lived the push, still against the timeline already sketched.
- Answer five questions. Where did the date come from? How many dependencies were unresolved on day one? How long did the team spend discovering whether the deadline was even possible? How long passed between the miss being knowable on the ground and known at the top? And when the date slipped, was the response to cut scope, or to add hours and people?
- Where the records and people's memory disagree, trust the records, and note the gap without attaching it to anyone.
- Write the knowable-to-known lag down as a baseline number.
How to read the result
The last question carries the most signal of anything in this toolkit. Cutting scope after a miss means the company can still subtract, which is healthy. Adding hours and people after a miss means load is compounding, and very little else can be fixed until that changes. The gap between knowable and known is information-travel time. Threats used as motivation after a miss are a late-stage marker, not a motivational style.
How to run it well
- Artifacts before narration, always. Memory fills gaps. It does not get to set the story.
- One replay is one sample. Write that on the page so a single crisis cannot pretend to be the culture.
Where it breaks
- One replay is one sample. A genuinely unusual crisis can look like a pattern when it is not.
- Where the records and people's memory of events disagree, attaching the gap to a person teaches the company to remember more carefully and write less down.
What would prove it wrong
A company showing addition after failure that then executes a subtraction-style recovery without a change to how it plans would count against the weight of that signal.
What we watch
Whether addition after a miss keeps predicting compounding load, or whether some companies add once and then learn to subtract on their own.
Ask yourself
- On the last urgent deadline, where did the date come from, as far as the records show?
- How many things did the work need from someone else that were not ready on day one?
- How far in was the team when it first knew, privately, whether the date was possible?
- How long passed between the miss being knowable on the ground and known at the top?
- When the date slipped, was something cut, or were hours and people added?
Feeds: Baseline Vitals, Gate-First Sequencing