Your Organisation Is Optimised - Just Not for What You Think
- Darren Emery
- 7 days ago
- 6 min read

Part 4 of the Performance Architecture Series
In the previous article, we ended with a question:
If strategy is only an input,what actually dictates the limits of your performance?
The structural reality is this:
Your organisation is already optimised.
Just not for the outcomes you say you want.
Performance is not an execution failure; it is a design success.
Your system is perfectly calibrated to produce exactly what it is currently delivering.
Article 1 argued that performance is a design outcome.
This article goes deeper: every design embeds an optimisation logic.
And optimisation always involves trade-offs.
It’s Not Underperformance. It’s Alignment.
Most executive conversations about performance start from the assumption that something is broken.
Innovation isn’t landing.
Strategy isn’t translating.
Teams seem busy but impact feels modest.
The instinctive diagnosis is capability.
We need:
Better prioritisation
Stronger leadership
More discipline
More accountability
Faster execution
But what if the organisation is not underperforming?
What if it is performing exactly as it was designed to?
Every System Optimises for Something
Whether explicitly stated or not, every organisation has an optimisation logic.
A dominant objective function - a systemic “default” that overrules any strategy deck.
Your strategy is what you say; your Objective Function is your System DNA - the structural default that dictates what your organisation actually does when no one is looking.
For example:
If funding is fixed annually and tightly governed, the system optimises for budget adherence, not value.
If promotions reward stability and predictability, the system optimises for risk minimisation, not innovation.
If governance escalates meaningful decisions upward, the system optimises for control concentration, not speed.
If performance conversations focus on milestone delivery, the system optimises for activity completion, not business outcomes.
These behaviours are not irrational.
The organisation behaves rationally - relative to the constraints and incentives it has been given.

The Performance Equation No One Writes Down
On paper, organisations optimise for value.
In practice, they optimise for a different equation:
Control
Compliance
Predictability
Risk containment
Resource utilisation
Budget certainty
These forces are rarely articulated as strategy.
But they are embedded in:
Funding models
Approval thresholds
Governance cadence
Incentive systems
Reporting structures
This is the implicit contract of the enterprise - and it is rarely debated explicitly at board level.
And because they are embedded structurally, they overpower declared intent.
If you tell teams to “be innovative” but fund them like fixed-cost assets, the system wins.
If you say “move fast” but require five layers of approval for deviation, the system wins.
If you say “act like owners” but escalate all material decisions, the system wins.
Structure always outranks rhetoric.
The Hidden Trade-Off: Control vs Throughput
At the heart of underperformance is a tension between control and throughput.

Every C-level executive recognises this table in practice, but few acknowledge it for what it truly is: a capital allocation choice.
From a finance perspective, the logic is sound: Control reduces variance, which increases predictability and protects capital. However, the systemic trade-off is rarely acknowledged: the more a system is optimised for control, the more it caps its own Strategic Throughput.
You are effectively trading your ability to respond to the market for the comfort of predictability.
The mechanics of this trade-off are visible in the friction of the daily workflow:
More reviews lead to more waiting.
More approvals create longer queues.
Higher certainty requirements result in slower learning.
The structural result is Governance Latency - the delay between a market signal and your organisation’s permission to respond. While this friction is survivable in stable markets, it is lethal in volatile ones. Many organisations are currently discovering, in real time, that their architecture is simply too slow for their reality.
The Optimisation Mismatch
Ask most executive teams what they want.
They will say:
Faster innovation
Shorter time to market
Greater adaptability
Customer-centricity
Better return on capital
Now ask:
What is your funding model optimised for?
What is your governance cadence optimised for?
What is your decision architecture optimised for?
Very often, the answers reveal a mismatch.
The stated ambition is adaptability.
The structural optimisation is stability.
That gap is where frustration lives.
Consider a typical enterprise scenario:
A strategic priority shifts mid-year.
The executive team agrees it is critical.
But funding is locked.
KPIs are fixed.
Delivery plans are committed.
The pivot requires exception approval across three committees.
By the time the organisation responds, the opportunity has moved.
This is not resistance. It is architectural inertia.
A Simple Diagnostic
At your next leadership session, try this exercise:
Complete the sentence:
“Our organisation is optimised to maximise…”
Be honest.
Is it:
Budget predictability?
Executive visibility?
Resource utilisation?
Risk avoidance?
Portfolio balance?
Committee oversight?
Now compare that answer to your strategy.
If the two don’t match, performance tension is inevitable.
You cannot sustainably achieve outcomes your system is not optimised for.
Why Local Optimisation Makes It Worse
One of the reasons this problem persists is because of fragmented logic.
This isn’t a collaboration problem or a silo problem - it is a systemic design flaw.
Finance optimises for financial control.
Portfolio optimises for balance.
Technology optimises for utilisation.
Delivery optimises for predictability.
Each function behaves sensibly in isolation.
But, it’s likely your flow of value runs through each of them.
And collectively, these rational decisions strangle global flow.
Local excellence is producing global sub-optimisation.
Value gets caught in the handoffs. Decisions stall, innovation slows.
This is Fragmented Optimisation - rational decisions that undermine global performance.
No one is wrong. The system is misaligned.
The organisation becomes efficient at the wrong objective.
The Cost of the Wrong Objective Function
When the objective function is misaligned with strategy, you see predictable symptoms:
Projects complete on time but don’t shift business metrics.
Innovation initiatives become compliance exercises.
Strategic pivots take quarters to materialise.
Teams protect scope rather than pursue outcomes.
Leadership discussions focus on status, not impact.
It feels like an execution issue. It’s not.
It’s an optimisation issue.
The system is faithfully producing what it is designed to produce.
The hidden cost is architectural friction:
Capital tied up in slow decisions: The erosion of strategic option value as investment remains frozen in serial approval layers designed for control rather than throughput.
Delayed realisation of returns: The gap between strategic choice and market impact.
Reduced option value: The loss of agility as the system prioritises stability over adaptation.
Increased cost of change: The sheer energy required to push a strategic pivot through an architecture that treats change as a "failure" of the plan rather than a feature of the system.
None of these appear explicitly in traditional reporting.
Redesigning the Objective Function
So what changes performance?
Not new slogans.
Not new frameworks.
Not another transformation programme.
Performance shifts when the objective function shifts.
You cannot “culture” your way out of a design flaw.
Performance shifts only when you re-engineer the Objective Function.
This is a sequence of architectural choices, not a shift in mindset.
And that sequence follows a predictable order:
Capital Allocation - from fixed, annual budgets to dynamic, option-based funding.
Decision Rights - from escalation-heavy hierarchies to proximity-based authority.
Measurement & Incentives - from activity completion to strategic traceability and impact.
Governance Clock Speed - from annual cycles to quarterly and continuous for learning.
Sunset Mechanisms - stopping initiatives when they no longer serve strategic intent.
In other words: performance improves when the system is re-optimised, not when rhetoric changes.
The Leadership Question That Actually Matters

Most performance conversations begin with the wrong question:
“How do we execute better?”
Earlier, we introduced a more useful starting point:
“What is our system optimised to do?”
Now comes the question that separates operators from architects:
Is that optimisation still appropriate for the environment you operate in?
Stable, regulated industries can tolerate control-heavy systems.
Volatile, technology-driven markets cannot.
The environment has a clock speed.
Your governance has a clock speed.
Your funding model has a clock speed.
When those speeds diverge, performance degrades.
Not because people fail.
Because design lags reality.
The Reframe
If you don’t change what the system is optimising for, nothing else sticks.
You can:
Upgrade practices
Introduce new tools
Restructure teams
Replace leaders
But the system will continue to produce the same outcomes.
Not because it is broken.
Because it is optimised.
The organisations that outperform are not those with the boldest ambitions.
They are those whose Objective Function matches their strategic intent.
Alignment between declared ambition and structural optimisation is where real performance architecture begins.
A Practical Diagnostic for Executives
At your next leadership offsite, ask the team to complete this sentence:
“Our organisation is optimised to maximise…”
Then compare the answers to your stated strategic ambition.
Where they differ, you have a structural gap.
That gap is not cultural.
It is architectural.
Your role as an executive is not to push harder.
It is to re-optimise the system.
Architecture determines performance.
Culture amplifies it.
Effort cannot compensate for it.
In the next article, we’ll examine how to deliberately re-optimise an enterprise system - without destabilising it.
This article is part of the Performance Architecture Series, exploring how organisations design for sustained performance.




Comments