Every system has one constraint that governs its output more than any other. Improve anything else and the system barely moves. Improve the constraint and the whole thing accelerates. Mission Planning spends its energy finding that one thing and pointing the quarter at it. The artifact is the Constraint Map.
One constraint governs the system
Organizations rarely fail for lack of effort spread across many fronts. They fail because effort is spread across many fronts while the single binding constraint goes untouched. Ten improvements that do not address the constraint produce almost nothing. One improvement that does can change the quarter. Planning that treats every problem as equally worth solving guarantees the constraint survives.
Locate it, do not guess
The constraint is usually not where the noise is. It hides in the handoff no one owns, the decision that waits four levels up, the approval that adds three weeks, the knowledge that lives in one person's head. Mapping the constraint means following the actual flow of work until you find the place everything waits on, then confirming it against the Readiness Score rather than against the loudest complaint.
Attack it, do not route around it
Once located, the constraint gets the quarter's best attention, not a workaround. Routing around a constraint feels like progress and leaves the governing limit exactly where it was, ready to bind the next quarter too. The Constraint Map exists so the whole team is looking at the same limiting condition and has agreed to spend real capacity removing it.
Naming the constraint often exposes disagreement that was hidden. The next lesson is about the difference between a quiet room and a truly aligned one.
How this fits the system
The constraint you locate here becomes the Constraint Map, so the quarter attacks the limit rather than working around it.