An initiative is approved. A project owner is named. A timeline is prepared. Teams begin work, but progress slows as functions disagree about priorities, resources remain unavailable and key issues wait for senior approval.
The organisation describes the problem as poor execution. Yet the team may be doing exactly what the unresolved system allows it to do: wait, negotiate, work around constraints or make local decisions that others later reverse.
The execution gap often begins with a missing decision.
Activity cannot resolve an unresolved choice
A team cannot execute a priority that has not been made clear. It cannot allocate resources that have not been committed. It cannot resolve a cross-functional conflict when decision rights are ambiguous. It cannot deliver a customer promise when the scope, acceptance criteria or trade-offs remain unsettled.
These gaps often appear as operational symptoms: missed milestones, repeated meetings, escalation, rework, delayed approvals and shifting deadlines.
But the underlying cause may be strategic or managerial. The organisation has not decided what matters most, who has authority or what it is prepared to stop doing.
Diagnose the missing decision
When an initiative stalls, leaders should ask:
- What decision is preventing the next meaningful step?
- Who has the authority and information to make it?
- Which alternatives or trade-offs remain unresolved?
- What resource, dependency or priority must be committed?
- What happens if the decision is not made by a defined point?
This is different from asking for another status update. A status report describes delay; a decision review identifies what would remove it.
Separate execution problems from decision problems
Some execution failures are genuinely operational: a process is unreliable, a supplier misses commitments, a technical issue remains unresolved or a team lacks the required skill. Those need operational intervention.
But even these problems may require decisions about scope, risk tolerance, additional resources, customer communication or whether to change the plan. Treating every obstacle as a task for the project owner can leave the actual authority gap untouched.
Make decisions visible in the operating rhythm
A useful milestone review should include the outcome expected, evidence of progress, dependencies, risks and decisions required. Each decision should have an owner, a deadline and the consequences of proceeding, changing or stopping.
Escalation should not be considered a failure. It is a mechanism for bringing a decision to the level that has the authority to resolve it. The failure is allowing the issue to remain invisible while the timeline continues to move.
The strategic implication
Execution is not simply the completion of tasks after strategy has been decided. It is an ongoing process of resolving dependencies and making the choices required to keep work aligned with the intended outcome.
The leadership question is: “What decision is the organisation avoiding, delaying or leaving ambiguous—and who must make it for this initiative to move?”
Related reading
- Build an Operating Rhythm That Converts Strategy into Results
- A Strong Department Cannot Compensate for a Weak Enterprise System
Continue exploring this collection: Execution — Sustaining the Advantage
Browse all articles · Ideas & Insights
Interested in the decisions behind technology-led growth? Explore Work With Me →
Continue reading in this collection
Build an Operating Rhythm That Converts Strategy into Results
A strategic operating rhythm connects milestones, evidence, accountability and resource decisions so leaders can adapt execution as conditions change.
Read article →
From 30 Ideas to 3–5 High-Value Growth Opportunities
Narrowing a broad idea set requires a common evaluation logic that tests customer value, strategic fit, capability, economics and evidence.
Read article →
Why Most Growth Plans Contain Too Many Opportunities and Too Little Evidence
A long opportunity list can create the appearance of ambition while hiding weak validation, competing priorities and unexamined assumptions.
Read article →