From Strategy to Value: Why Performance Breaks Between the Slides
- Darren Emery
- Feb 9
- 6 min read
Updated: Apr 6
Part 2 of the Performance Architecture Series
Most leadership teams I work with do not lack ambition.
They lack throughput.
They have strategies.
They have roadmaps.
They have transformation initiatives.
They have delivery teams working hard.
On paper, everything connects.
So when performance disappoints, the question becomes:
“Where is the breakdown?”
Because when value moves slowly, competitors don’t.
The reflex answers are familiar:
Strategy wasn’t clear enough
Delivery wasn’t strong enough
Change wasn’t adopted fast enough
But many organisations don’t fail at strategy or delivery.
They fail at connection.
Between intent and execution.
Between decisions and outcomes.
Between funding and value.
Performance rarely breaks at the endpoints.
It breaks in the spaces between them.
The illusion of end-to-end alignment
Ask almost any executive team:
“Are your strategy and delivery aligned?”
The answer is usually “yes.”
After all:
Strategic priorities are defined
Funding is allocated
Initiatives are approved
KPIs are tracked
Delivery is underway
Alignment appears visible.
But alignment on slides is not alignment in motion.
Motion is what customers feel.
Real alignment is not about artifacts connecting.
It’s about whether value flows.
Many organisations have alignment theatre:
Strategy decks that don’t shape daily decisions
Roadmaps that don’t influence funding adjustments
OKRs that don’t change prioritisation
Governance forums that review rather than enable
Everything looks connected.
Value still moves slowly.
That’s the symptom.
I once worked with an organisation where a strategic priority was labelled “critical” at board level.
It still took 14 months to reach a customer.
Not because anyone resisted it.
In fact, everyone supported it.
But it passed through five funding gates, three prioritisation forums, and two re-organisations.
Alignment was never the problem.
The path was.
The real problem: translation loss
Every organisation has domains:
Strategy
Finance
Portfolio
Product
Technology
Operations
Each domain has its own language, incentives, and logic.
None of this is inherently wrong.
Specialisation is necessary at scale.
But every boundary introduces translation.
Strategy becomes themes.
Themes become projects.
Projects become features.
Features become backlogs.
Backlogs become tasks.
At each step, meaning shifts.
Not maliciously.
Not incompetently.
Just structurally.
By the time work reaches teams, it is often several translations removed from the original intent.
When outcomes disappoint, the organisation tries to correct at the delivery layer.
But the distortion happened upstream.
This is not misalignment.
It's structural friction.
The cost of the space between
Just as technical debt slows down software delivery,
structural debt slows down value delivery.
Legacy governance.
Rigid funding cycles.
Escalation-based decisions.
They quietly accumulate interest.
And like financial debt, the longer it’s ignored, the more expensive change becomes.
Eventually, organisations stop adapting not because they lack ideas - but because the system has made change expensive.
The organisation pays for it in:
Delay
Friction
Lost opportunity
Slower learning
Structural debt doesn’t show up on balance sheets.
But it compounds like any other liability.
Why handoffs kill value
Handoffs feel efficient.
But they are usually where value slows down.
Every handoff introduces:
Waiting
Reinterpretation
Local optimisation
Loss of context
Consider a typical journey:
Strategy defines a priority.
Finance approves funding.
Portfolio sequences work.
Product shapes scope.
Technology estimates effort.
Delivery executes.
At each stage, work pauses.
Queues form.
Assumptions creep in.
No single step looks disastrous.
But cumulative delay compounds.
The organisation measures activity.
Customers experience latency.
The cost is rarely visible on dashboards.
But it is felt in competitiveness.
The three flow killers (common in UK enterprises)
1) The Annual Budget Cycle
Fixed January plans quietly kill July opportunities.
When funding is locked annually, learning becomes compliance.Adaptation becomes political.
2) The Steering Committee
Decisions wait for the people furthest from the work.
Context degrades.
Momentum stalls.
Accountability blurs.
3) The Dependency Web
Team A is ready.
Team B has a 4-week queue.
Flow doesn’t slow at the team.
It slows at the interfaces.
Introducing flow
If Article 1 argued that performance is designed,
then Article 2 argues that performance is dynamic.
It’s not static.
It lives in motion.
The most useful lens here is flow.
Flow is not a team-level concept.
It is an organisational one.
Flow asks:
How smoothly does value travel from idea to impact?
Where does it wait?
Where does it need permission?
Where does it loop?
Where does it get reinterpreted?
Most organisations optimise parts.
Few optimise flow.
And local optimisation often makes global flow worse.
A control-heavy finance process can slow learning.
A risk forum can increase delay.
High utilisation can increase queues.
Each makes sense locally.
Together, they reduce performance.
What high performers do differently
The best organisations don’t eliminate governance, funding, or controls.
They redesign them for flow.
Funding becomes incremental.
Decision rights sit closer to knowledge.
Governance asks “how do we enable?” not “how do we control?”
Same functions.
Different design.
Radically different performance.
This is rarely about working harder.
It is about designing smarter.
The High-Performance Pipeline
High-performing organisations think less in silos and more in pipelines.
Strategy → Investment → Decisions → Execution → Feedback → Adaptation
Not as stages.
As a connected system.
Where each part strengthens or weakens the whole.
In weak pipelines:
Strategy doesn’t shape funding
Funding doesn’t enable learning
Decisions escalate too far
Feedback arrives too late
Adaptation is political
In strong pipelines:
Strategy informs investment dynamically
Funding follows evidence
Decisions sit near knowledge
Feedback loops are short
Adaptation is normal
The difference is not effort.
It is connectivity.
A familiar executive experience
A common frustration:
“We agreed this six months ago. Why is it still not live?”
Trace the journey and you often find:
Funding gates
Governance reviews
Portfolio reshuffles
Dependency delays
Priority conflicts
No dramatic failure.
Just systemic friction.
Multiply that across initiatives and it looks like a delivery issue.
But it’s a system flow issue.
Managing intentions vs managing performance
Many organisations manage intentions well.
They define goals.
They launch initiatives.
They track milestones.
But intentions are not value.
Value is realised when something changes for a customer or business metric.
If you cannot trace how value flows from decision to outcome, you are managing intentions - not performance.
That distinction matters.
Intentions feel productive.
Flow creates impact.
The market only rewards the second.
The Throughput Health check
Pick one major project or initiative that launched 6 months ago.
Ask:
Where did it wait? How many weeks of dead time did it spend on the balance sheet, consuming overhead without generating a single penny of value?
Where did it need permission? How many times did progress halt to wait for a committee or a signature from someone three layers removed from the context?
Where did it loop? How many times did the work loop backwards for re-approval or clarification?
Where did it get reinterpreted? Is today’s version still solving the original strategic problem, or has it been reinterpreted into something safe and irrelevant?
Most executives are surprised by the answers.
Not because the organisation is broken -but because no one has ever mapped the waiting.
We measure utilisation.
We rarely measure delay.
Yet delay is where competitiveness is lost.
Your constraint is flow - not effort.
Where does value actually slow down?
Not who.
Where.
Which boundary?
Which queue?
Which decision point?
Which funding constraint?
Blame invites defensiveness.
Flow invites diagnosis.
A different leadership lens
Leaders don’t need every delivery detail.
They need visibility of flow.
Because flow is where:
Strategy meets reality
Capital meets outcomes
Decisions meet consequences
Flow is not a team problem.
It is a leadership design responsibility.
The organisations that outperform are not those with perfect plans.
They are the ones where value travels with the least friction.
“If you can’t trace how value flows, (and most organisations can’t - at least not honestly) you’re managing intentions, not performance.”
Performance is not just what you choose.
It is how smoothly those choices travel through the system.
That is where high-performance pipelines begin.
And that is where performance architecture becomes real.
In the next article, we’ll go one level deeper:
If flow is the lifeblood of performance, what actually constrains it inside organisations?
Because flow doesn’t break randomly.
It breaks at predictable points - and that's down to organisational design.
This article is part of the Performance Architecture Series, exploring how organisations design for sustained performance.
Comments