Strategy execution becomes a leadership problem when an agreed priority meets commitments the organization has not changed. A company can have skilled teams, a clear plan and regular progress reports, yet still miss its goal because the people needed for the new work remain assigned elsewhere. Before treating the shortfall as a failure of effort, leaders need to ask whether their continuing decisions make the priority deliverable.
Execution is the connection between strategic choices, people and operations. Announcing a direction does not settle who may redirect work, which existing promise will give way or what evidence will prompt a change of course. Capable teams cannot resolve those conflicts simply by working harder. The strategy leader’s task is to identify the commitment that blocks delivery and decide whether to change it, change the strategic promise or address a genuine performance gap.
Why an agreed priority can lose in practice
Old commitments often survive for good reasons. They may serve customers, meet obligations or support the business that funds a new initiative. Reducing them creates an immediate question for a named leader: whose deadline, budget or service level will change? Keeping both commitments postpones that conversation. The cost appears later, spread across teams as delays, competing requests and work that must be redone.
The conflict can be hard to see when strategy, staffing and operations are discussed separately. A strategy meeting approves a new outcome. A staffing discussion finds capable people to own it. An operating review asks why progress is slow. None of those conversations necessarily changes the schedules or authority that govern the work. Each team can be acting responsibly within its remit while the enterprise remains committed to incompatible results.
In Execution: The Discipline of Getting Things Done, Larry Bossidy and Ram Charan, with Charles Burck, connect the people, strategy and operations processes. Bossidy’s account also stresses following through on strategic decisions and asking whether a plan has the people and resources it needs. The implication is not that senior leaders should take over every operating choice. It is that approving a strategy leaves them responsible for the cross-business decisions required to carry it out.
That responsibility matters most where a delivery owner cannot change the conditions of delivery. Giving someone an outcome target does not give them authority over another team’s capacity. A tighter reporting cycle may reveal the shortfall sooner, but it cannot decide which obligation takes precedence. Accountability helps when a person can act on the result; without that authority, it can obscure the decision that leadership has retained.
Follow the conflict to the decision-maker
Consider a hypothetical service company that chooses to resolve complex customer problems more quickly. Its service staff can diagnose the problems, but many resolutions require time from technical specialists. Those specialists remain scheduled against existing projects, whose leaders are expected to meet their own deadlines. Service can improve its response time and close routine cases promptly while complex customers continue waiting.
The company could ask service to escalate cases faster. That might help it spot delays, but it would not make specialist time available. It could appoint one person to own complex resolutions. That would clarify who tracks the result, but not who may change a project schedule. The binding choice belongs with the leader who can weigh the customer promise against the project commitments.
That leader has several defensible options. Reserving specialist time for complex cases would require an explicit change to project work. Narrowing the service promise would reduce the demand on specialists, but customers would receive a different offer. Additional expertise might be possible, though leaders would need to establish when it could actually help. The choice depends on the value and obligations attached to each commitment. What is not defensible is to keep promising faster resolution while treating the specialists’ existing schedule as untouchable.
The Execution Coherence Audit is a proposed OutcomesLab aid for examining such a choice. It traces six connections in one initiative—strategic choices, ownership, cadence, resources, measures and consequences—to find where the intended result stops governing recurring decisions. The point is to identify the weakest connection that calls for a leadership decision.
| Connection | What to examine in the service initiative | Decision that may follow |
|---|---|---|
| Strategic choices | Which complex problems does the faster-resolution promise cover? | Define or narrow the promise. |
| Ownership | Who can settle a conflict between service and project commitments? | Give a named leader decision authority or a prompt escalation route. |
| Cadence | Does that decision happen before cases spend days waiting? | Bring capacity conflicts to a review that can act in time. |
| Resources | Is specialist time available when the promise requires it? | Release time, change project obligations or revise the service plan. |
| Measures | Are closed cases rising while complex problems remain unresolved? | Examine customer results alongside activity and specialist waiting. |
| Consequences | Who changes course when an approved allocation is not honored? | Assign corrective action to the leader who controls the decision. |
The connections should be read together. In this example, a more frequent review has little value if no one attending can release specialist time. Reserving that time may still be the wrong answer if the promise covers problems the organization cannot resolve reliably. The audit helps leaders avoid launching a separate improvement effort for every symptom. It brings the decision about the promise and the decision about capacity into the same conversation.
Review the result, not just the activity
A useful execution review distinguishes what teams did from what the strategy was meant to achieve. For the service company, cases closed show delivery activity. Complex cases brought to a usable resolution show whether the intended customer result is following. Time waiting for specialist input points to a possible constraint. Leaders would need to inspect the affected cases before assuming that waiting proves a capacity shortage; poor triage or unexpectedly difficult work could also explain it.
Suppose that inspection finds prompt diagnosis followed by repeated waits for specialists. The executive who controls the competing project commitments must decide what time to release, which project obligation will change and when the new allocation starts. The service leader can then schedule work within that allocation and remain accountable for its quality. At the next review, leaders examine whether waiting fell, whether customers obtained usable resolutions and whether the change caused an unacceptable problem in project delivery. If waiting persists despite specialist time being made available, they should revisit the diagnosis rather than repeat the same demand for urgency.
This is why a dashboard can be green while a strategy is failing. A higher case-closure count may reflect more routine work completed, not faster resolution of the complex problems the company chose to address. More indicators alone will not fix that blind spot. Each measure needs a job in the review: show activity, test the intended result or expose a constraint or adverse effect that could change the next decision.
When the answer is not system redesign
Conflicting commitments are not the only cause of poor delivery. If a team has a clear task, workable authority and access to the agreed resources but repeatedly cannot perform an essential step, leaders should examine skills, staffing, quality and supervision. If risks are visible and an available escalation route goes unused, delivery discipline may be the problem. Changing enterprise priorities will not substitute for developing capability or addressing performance in those circumstances.
The strategic promise itself can also be unsound. If the service company cannot justify the capacity required for faster complex resolutions, it should reconsider the offer rather than demand that teams absorb the gap indefinitely. During an urgent incident, a designated leader may need to set an immediate sequence of action. That can resolve the immediate ambiguity without settling how the organization will handle the competing commitments afterward.
The distinction changes how leaders respond to a missed target. First establish whether the people responsible had a feasible promise, the authority to act and the resources their plan assumed. Where those conditions were absent, leadership must change the commitment or make its support real. Where they were present, leaders can judge delivery against them. Execution becomes more reliable when the same leadership team that chooses a priority also owns the decisions that make it possible—or explicitly decides not to make them.