Concept
The decision review
A decision review, held on the tripwire date, records the outcome first and then, separately, judges the decision process given what was known at the time: which villain got through, how calibrated the probability was, and what to change. The lesson is about the process, never about the card.
Reviews go wrong in two ways: they never happen, because nothing prompts them, or they happen as resulting, judging the decision by how it turned out. The tripwire fixes the first and the four boxes fix the second. The order matters. First the outcome in plain terms. Then the process: given what I knew, were the options wide enough, was the assumption tested, was the probability honest, did the premortem see this coming. Then the lesson, which must be about something you could have done differently with the information you had. A good decision with a bad outcome produces no change to the process; a bad decision with a good outcome must, even though nothing hurt.
A real-life example
Nine months after opening, a second bakery branch is breaking even but the first shop's reviews have slipped, which was one of the premortem's reasons. The review changes staffing, not the decision to open, and the tripwire did its job.
How to use it
- 1Review on the tripwire date, not when you feel like it.
- 2Write the outcome first, then judge the process separately, then the lesson.
- 3Change the process only for decisions that were poor given what you knew.