The traditional retrospective asks "what blocked us." The debrief asks something more precise: what bottleneck emerged that planning failed to see? The most instructive constraints are the ones no one predicted, because they reveal where the organization's vision of itself was wrong.
Planning names a constraint; reality names another
Good planning identifies the constraint it can see and points the quarter at it. Then execution runs, and a different bottleneck often appears somewhere planning was not looking. That gap between the predicted constraint and the actual one is pure signal: it shows the blind spot in how the organization reads itself.
The blind spot is the lesson
A bottleneck that surprised you is more valuable than one you expected, because it tells you where your diagnosis was thin. Maybe you underweighted a handoff, or missed that authority was more concentrated than it looked, or did not see attention fragmenting. Recording the emergent bottleneck is how the next planning cycle learns to look where it did not.
Feed it forward
The point is not to lament the surprise but to make sure the next plan is not surprised the same way. The bottleneck planning missed this quarter becomes a thing planning explicitly checks next quarter. Over cycles, the organization's blind spots shrink because each debrief maps one more of them.
The final question turns all of this into something the organization keeps.
How this fits the system
The constraint that emerged goes into the Mission Debrief, and becomes evidence for the next Constraint Map and Readiness Score.