As pressure builds toward a delivery milestone, decisions can stop being made by the people closest to the work. They get raised, noted, and passed upward. That is not a competence failure. It can happen when success isn’t clearly defined and no one is sure what they’re authorised to decide.
Decision-making can drift upward. It’s one of the more consistent patterns in delivery under pressure, and one of the more damaging because it doesn’t announce itself as a problem. It looks like diligence. What it actually is is ambiguity doing the damage, not the people.
Unresolved decisions add friction, delay, and emotional load to the work. The team waits for an answer they could probably give themselves if they knew where the boundaries were. Leaders can find themselves pulled into trade-offs they shouldn’t need to make, while the people doing the work quietly lose confidence in their own judgement.
The fix is more specific than “empower the team.” It starts with making outcomes explicit so people understand what a good decision looks like in this context. Then clarifying who owns what decisions — not in a formal document, but in a shared, clear answer that removes the main source of ambiguity. That one clarification tends to remove a significant proportion of the delays that build in any delivery stretch.
A useful question: in the last two weeks, how many decisions came back to you that could have been made one level down? The answer usually tells you where the ambiguity is sitting, and how much it’s costing.
Making that ambiguity specific and addressable is what the Clarity First Diagnostic is built to do.