Thinking · Leadership & Execution
Why Execution Matters More Than Strategy Decks
I spent years advising founders, C-suites and boards on strategy. The biggest lesson was not that organisations lacked ideas. Most had plenty. The hard part was turning those ideas into decisions that actually changed the business.

The gap
Most businesses do not suffer from a shortage of ideas.
They suffer from a shortage of execution.
During my advisory years, I worked with founders, C-suites and boards across investment management, private equity, real estate, fintech, renewable energy, manufacturing and technology.
The businesses were different, but the pattern was remarkably consistent.
Senior teams usually knew what they wanted to achieve.
Grow into a new market. Improve margins. Raise capital. Launch a product. Reduce cost. Build a stronger sales function. Reposition the business. Fix an operating model.
The difficulty was rarely producing another set of recommendations.
The difficulty was making the organisation behave differently on Monday morning.
Strategy creates direction. Execution creates evidence.
A strategy deck can hide a lot
Clarity on a slide does not mean clarity in the business.
Strategy presentations are useful because they force ideas into a coherent form.
They can show the market, priorities, economics, risks and desired outcomes.
But a deck can make an organisation look more aligned than it really is.
Everyone can agree with the destination while holding a different view of what happens next.
One executive thinks the priority is hiring.
Another thinks it is technology.
Another is waiting for funding.
Another assumes the commercial team owns the change.
That is not alignment. It is agreement without operational consequence.
Where strategies fail
The failure is usually in the space between intention and ownership.
If everything is strategic, nothing has enough resource or senior attention to move properly.
A task owned by “the team” often means nobody feels personally responsible for the outcome.
Businesses try to launch, hire, automate and expand at the same time when one of those steps should clearly come first.
The strategy is discussed quarterly while the business makes hundreds of decisions in between with no connection back to the plan.
Teams keep moving because stopping to admit that an assumption was wrong feels harder than continuing.
Meetings, reports, hiring and projects can create a great deal of motion without changing the commercial result.
Strategy must become decisions
A strategy is only useful when it changes what you do.
I tend to test a strategy by asking what decisions it creates.
What are we stopping?
What are we starting?
What gets more capital?
What gets less?
Who now owns the outcome?
What has to happen first?
What evidence will tell us whether the decision is working?
If the answers are vague, the strategy is probably still too conceptual.
My test: if the strategy is genuinely different, next month’s resource allocation should look different too.
Sequencing
Execution is often less about doing more and more about doing things in the right order.
This is one of the most underrated parts of strategy.
A business may need a stronger sales team, better systems, a new product and more capital.
That does not mean all four should happen at once.
Perhaps the product needs to be proved before hiring.
Perhaps the data needs to improve before the sales team can perform properly.
Perhaps the business needs to reduce cost before raising capital.
Perhaps management capacity is already the constraint and another initiative would simply make execution worse.
Good sequencing is strategic because it determines where limited resources produce the greatest next step.
Ownership
Accountability needs a name, not a department.
One of the easiest ways for execution to disappear is shared responsibility without individual accountability.
Cross-functional work often needs several people.
But the outcome still needs someone who wakes up thinking about whether it is moving.
That person does not need to do every task.
They need to own the result, surface blockers and force decisions when the work stalls.
This matters especially when a strategy crosses sales, operations, technology, finance or risk.
Without a clear owner, everyone can be busy and the outcome can still sit still.
The operating rhythm
Strategy needs to appear in the weekly business, not just the annual offsite.
If something is strategically important, it should be visible in the normal operating rhythm.
There should be a clear measure, an owner, a next milestone and a mechanism for dealing with blockers.
The purpose is not to create more reporting.
It is to shorten the distance between a problem appearing and a decision being made.
I have always preferred a small number of meaningful measures over large dashboards that nobody uses to change behaviour.
The right measure tells you whether the thing you care about is actually improving.
Consulting taught me this too
Advice is easy to overvalue when you are not responsible for implementation.
This is something I became much more conscious of during my years advising management teams.
A consultant can produce a logical recommendation.
But the client still has to live with the implementation.
They have to move the people, budget, systems and incentives.
They have to manage disruption.
They have to explain the change internally.
They have to absorb the consequences if the recommendation is wrong.
That made me increasingly reluctant to separate strategy from implementation.
If a recommendation cannot survive contact with the actual organisation, it was never a complete strategy.
The uncomfortable middle
Execution usually becomes difficult after the excitement has gone.
The beginning of a strategic initiative is energising.
The leadership team agrees the ambition. The presentation is strong. People understand why it matters.
Then the work becomes repetitive.
Data needs cleaning. Roles need changing. Old processes need switching off. People need following up. Difficult conversations need having.
This is where many initiatives lose momentum.
There is no longer novelty, only persistence.
In my experience, execution is often won in this middle phase.
The organisation that keeps making the small decisions after the initial enthusiasm fades is usually the one that gets the result.
Founders have a different execution risk
Entrepreneurial businesses can move quickly enough to create their own confusion.
Large organisations can be slowed by bureaucracy.
Founder-led companies can have the opposite problem.
They can change direction so quickly that the team never gets enough time to execute the previous priority.
A new idea appears. A client opportunity creates another. A competitor changes something. The founder sees three adjacent possibilities.
Speed becomes noise.
This is why I think founder discipline is partly about protecting the organisation from unnecessary changes in priority.
Not every good idea deserves immediate execution.
I explored that from the capital side in Building Finanze From £10,000: The Decisions That Mattered.
How I think about execution now
Seven questions turn a strategy into something operable.
- What is the actual outcome? Not the initiative – the commercial or operating result.
- Who owns it? One person should be accountable even if many contribute.
- What happens first? Sequence the work around the real constraint.
- What are we stopping? New priorities need capacity from somewhere.
- What does success look like? Use measures that can change a decision.
- What could block it? Surface dependencies before they become excuses.
- When do we review the assumption? Persistence is useful; persisting with a broken premise is not.
Those questions are simple.
That is partly why I like them.
Execution becomes more difficult when the organisation needs a complicated framework just to understand who is doing what next.
Leadership
Senior leaders create execution through what they repeatedly pay attention to.
Teams notice what leaders follow up.
If a project is described as critical but never appears in the leadership conversation, people correctly infer that it is not actually critical.
If missed commitments carry no discussion, commitments become optional.
If priorities change every week, teams stop investing deeply in any of them.
Execution therefore becomes a leadership behaviour.
It is the consistency between what the organisation says matters and what senior people repeatedly ask about, resource and hold accountable.
Final thought
The best strategy is the one the organisation can actually execute.
I still believe strategy matters enormously.
Direction matters. Market choice matters. Positioning matters. Capital allocation matters.
But the value of strategy is only realised through execution.
A brilliant strategy that sits above the organisation is less valuable than a good strategy that changes decisions, priorities and behaviour every week.
That is the lesson I took from years of advisory work and have carried into entrepreneurship.
Strategy tells you what should happen. Execution is the discipline of making the business prove it.
General information only. This article reflects my personal experience in strategic advisory, leadership and entrepreneurship. It is not financial, investment, legal or business advice.
Make the next decision visible
For each material milestone, record the person accountable, the evidence needed, the dependencies and the date a decision must be made. A milestone called “finance arranged” is too broad if nobody knows whether it means indicative terms, credit approval or cleared funds.
Review exceptions rather than collecting reassuring updates. What has changed since the last review? Which dependency is late? What decision will unlock the next step? What should stop until the missing evidence arrives?
A useful operating rhythm makes emerging problems visible while they can still be addressed. It also distinguishes a project that needs help from one that needs a different plan. More meetings do not create that clarity unless somebody leaves with a specific action and the authority to deliver it.
Keep exploring