Ownership is not the same as accountability
Most strategies eventually produce an action plan. Initiatives are named. Sponsors are assigned. Workstreams are created. Owners appear beside rows in a spreadsheet.
And yet execution can still drift.
The problem is often not an absence of ownership. It is that ownership has been defined too loosely to govern the real work.
A named owner may still be unclear about which decisions they can make, which trade-offs require enterprise input, what resources are genuinely committed, where another function controls a critical dependency, when a problem should be escalated, and what evidence will demonstrate traction.
In that environment, the organisation can look highly accountable while remaining difficult to execute through.
This is why strategy execution needs more than owners. It needs an accountability architecture.
An accountability architecture is the practical system that connects a strategic choice to the decisions, commitments, interfaces and review disciplines required to move it. It makes explicit how the organisation will act when priorities compete, dependencies become visible and circumstances change.
The strategy is not executable until these questions are answerable.
Why execution gets lost after the strategy decision
Recent work on strategy mobilisation makes an important distinction between deciding a strategy and mobilising the organisation behind it. Senior teams may invest heavily in analysis and strategic choice, but much less in the work required to translate those choices into coordinated action.
That translation layer matters because strategy rarely enters an empty organisation. It lands on top of existing budgets, reporting lines, incentives, commitments and functional priorities.
A strategic priority may therefore be “owned” by one executive while relying on five other parts of the organisation to change behaviour, move resources or make different decisions. If those interfaces are not explicit, accountability becomes distributed in theory and diluted in practice.
Research on execution and decision-making repeatedly points to the importance of decision rights, information flow, coordination and clear accountability. More recent transformation research makes the same issue visible in practical terms: organisations can lose speed when decisions escalate unnecessarily or when accountability is spread across too many actors without clear guardrails.
The implication is straightforward.
If a strategy requires cross-functional action, accountability must be designed at the level of the enterprise—not simply assigned at the level of the initiative.
Five elements of an accountability architecture
1. Explicit decision rights
Every important strategic priority contains a small number of consequential decisions.
Who decides whether investment moves from one area to another? Who can change scope? Who decides when a customer promise outweighs a cost target? Who determines whether an initiative stops, accelerates or changes direction?
These decisions should not be left inside generic labels such as “responsible” or “accountable.” The organisation needs to know who has the decision, whose advice is required, who executes it and how disagreement is resolved.
The more cross-functional the priority, the more valuable this clarity becomes.
2. Commitments that are observable
Accountability becomes useful when it can be seen.
What has this leader or team actually committed to deliver? By when? With what resources? What must another function provide? What evidence will show that movement has occurred?
This is different from creating a long activity list. The aim is to identify the few commitments that materially change the probability of strategic success.
A good commitment is specific enough to be reviewed and consequential enough to matter.
3. Dependencies treated as part of the work
One of the most common execution errors is to manage initiatives individually when value is actually lost between them.
A commercial priority may depend on technology. Technology may depend on data. Data may depend on process ownership in operations. Operations may need a funding decision from finance. Each function can appear to be performing while the enterprise outcome remains stuck.
Accountability therefore needs to include the interfaces.
Which dependencies are critical? Who owns resolving them? Which trade-offs require executive-team attention? Where does one function’s local optimisation create enterprise friction?
If dependencies are invisible, execution risk is invisible too.
4. An agreed escalation path
Not every issue should reach the CEO or executive team. But the issues that genuinely require enterprise judgement should reach them quickly.
A useful accountability architecture makes escalation explicit before the crisis occurs.
What threshold triggers escalation? What information should accompany it? Which forum resolves it? Who has authority to make the trade-off? What happens after the decision?
This prevents two common failure modes: unnecessary escalation that slows the organisation, and delayed escalation that allows a material issue to become expensive before senior leaders see it.
5. A review rhythm built around decisions and evidence
Review meetings often become reporting rituals. Teams describe progress, explain activity and update status colours. Everyone leaves better informed but the work itself is largely unchanged.
A stronger execution rhythm asks different questions.
What has moved? What has not? What assumption has changed? Which commitment is at risk? What decision is now required? Where must resources move? What should stop?
The purpose of the review is not to observe execution from a distance. It is to improve execution through timely judgement.
That distinction matters.
Accountability without coordination can still fail
Clear accountability is necessary, but it is not sufficient.
Research on decision quality shows that high-performing organisations combine clarity with effective stakeholder coordination, enterprise-level value focus and commitment to execution. Simply defining roles does not guarantee that a cross-cutting decision will be implemented well.
This is especially important at executive-team level.
A strategic priority can have a clear owner and still fail because peers protect functional interests, dependencies are not surfaced, or the leadership team avoids the trade-off that the strategy requires.
The real test of accountability is therefore not whether every initiative has a name beside it.
It is whether the organisation can make and hold the enterprise choices required when those initiatives collide with normal operating pressure.
From accountability to traction
The most useful evidence of accountability is movement.
That does not mean every result will appear immediately. Strategic work often involves lead indicators, capability shifts and decisions whose financial impact takes time to emerge.
But there should be observable evidence that the organisation is behaving differently because the strategy exists.
Resources have moved. A decision has been made. A dependency has been resolved. A legacy activity has stopped. A customer process has changed. A leadership behaviour has shifted. A milestone has been achieved for a reason—not simply reported as complete.
This is why the BGA Strategy Execution Accelerator focuses on evidence of traction rather than volume of activity.
Activity can be abundant while the strategy remains stationary.
A practical executive-team test
For any critical strategic priority, the executive team should be able to answer six questions without ambiguity:
- What enterprise choice are we trying to execute?
- Who has authority over the decisions that will determine progress?
- What are the few commitments that must be delivered next?
- Which cross-functional dependencies could stop movement?
- What triggers escalation, and where will the trade-off be resolved?
- What evidence will tell us that the strategy is gaining traction?
The role of the executive team
Accountability architecture is not a PMO substitute and it should not create another administrative layer.
Its purpose is to make leadership work clearer.
The executive team owns the enterprise trade-offs that functions cannot resolve alone. It sets the few strategic priorities that deserve disproportionate attention. It clarifies decision rights where ambiguity is slowing progress. It moves resources when the strategy requires it. It removes barriers that sit between functions. And it creates the review rhythm through which evidence changes the next decision.
When this work is done well, accountability becomes enabling rather than punitive.
People know what they can decide. Teams understand what they owe one another. Escalation becomes faster. Reviews become more consequential. Leaders can distinguish genuine traction from reassuring activity.
Make the strategy executable
A strategy can be clear and still be difficult to execute.
The gap is often not another communication exercise, another dashboard or another layer of governance. It is the absence of a practical system connecting strategic choices to the decisions and commitments that move them.
That system is the accountability architecture.
Make the enterprise choice explicit. Clarify who decides. Define the commitments. Surface the dependencies. Establish the escalation path. Review evidence, not activity.
Then the strategy has somewhere to travel.
Questions for executive teams
- Which strategic priority currently has the greatest ambiguity around decision rights?
- Where is accountability assigned to one leader but delivery depends on several functions?
- Which dependency is most likely to slow execution over the next 90 days?
- What issue is being repeatedly discussed because no one is clearly empowered to decide?
- Does our review rhythm generate decisions—or mainly status updates?
- What observable evidence would convince us that the strategy is genuinely gaining traction?
BGA connection
This perspective supports the Bevan Gray Advisory Strategy Execution Accelerator: a focused 90-day intervention that turns strategic choices into owned execution, explicit decision rights, disciplined operating rhythm and measurable traction. The accountability architecture is not a standalone bureaucracy; it is part of the minimum viable execution system required to make strategy real.
Sources and further reading
- West, A., Montard, A., Lacroix, S. & Zimmerman, W. (2026), “How to Ensure Your Company Acts on Your New Strategy,” Harvard Business Review, July 2026.
- McKinsey & Company (2026), “Rigor: What it takes to turn ambition into impact.”
- De Smet, A. et al. (2022), “If we’re so busy, why isn’t anything getting done?”, McKinsey & Company.
- McKinsey & Company (2019), “Effective decision making in the age of urgency.”
- Neilson, G. L., Martin, K. L. & Powers, E. (2008; HBR summary updated 2012), “The Secrets to Successful Strategy Execution,” Harvard Business Review.
- McKinsey & Company (2025), “Execute to win: How healthy organizations turn vision into results.”
- Bevan Gray Advisory, Strategy Execution Accelerator Research, Methodology & GTM, 2026.