The traditional retrospective asks "what should we improve," and gets a list of tasks. The debrief asks "what condition failed," and gets something durable. Locating the failure in a condition rather than a person is what makes the fix structural instead of personal.
People are rarely the cause
When a quarter falls short, the easy story is that someone underperformed. It is almost never true, and even when a person struggled, the more useful question is what condition allowed the struggle to matter. Capable people fail inside broken conditions; replacing the person leaves the condition intact and the failure waiting to recur.
Name the condition, in the Four A's
Every failure can be read back to a condition. Work stalled waiting for a decision: authority failed. Everyone was busy on the wrong things: attention failed. Teams pulled in different directions: alignment failed. The organization could not absorb the change: adaptability failed. Naming which of the Four A's gave way turns a vague disappointment into a specific, fixable diagnosis.
Fix the condition, not the instance
A task-level fix repairs one instance. A condition-level fix repairs the class. If authority failed this quarter, distributing decision rights protects every future quarter, not just the next task. That is why the debrief insists on the condition: it is the only fix that compounds.
Sometimes the failed condition was not the one planning expected. The next question finds the bottleneck planning missed.
How this fits the system
Locating the failure in a condition rather than a person is what makes the Mission Debrief produce a durable fix.