Your Organisation Is Perfectly Designed to Get These Results
- Darren Emery
- Feb 2
- 6 min read
Part 1 of the Performance Architecture Series
There’s a moment I see again and again when talking to senior leaders.
It usually arrives after the dashboards have been reviewed, the delivery updates discussed, and the risks politely acknowledged.
Someone leans back and says something like:
“We’ve got good people.
We’ve invested heavily.
We’ve tried Agile, Product, OKRs, AI…
So why does it still feel this hard – despite all the investment?”
The reflex answer is execution.
Teams need to move faster.
Delivery needs tightening.
People need to try harder.
It’s an understandable conclusion.
And it’s almost always the wrong one.
Because most performance problems are not delivery failures.
They’re design outcomes.
Organisations don’t drift into poor performance.
They are engineered into it - often unintentionally.
The uncomfortable truth about performance
There’s a sentence most organisations avoid finishing:
“Given how we’ve designed this place, these results make perfect sense.”
Not emotionally.
Not politically.
But systemically.
Organisations rarely under-perform because people don’t care, lack capability, or aren’t putting in the effort.
More often, they are performing exactly as their structures allow.
That includes:
How strategy is translated (or diluted)
How money is allocated
Who gets to decide what, and when
How work flows across boundaries
What gets measured, rewarded, and ignored
None of that lives in Jira.
None of it shows up in a sprint review.
None of it can be fixed with a better roadmap.
And all of it shapes outcomes far more than effort ever could.
The visible symptoms of a strained system
Leaders don’t first notice structural constraints in org charts.
They notice them in their calendars, their priorities, and their fatigue.
The Meeting Tax
When 50-60% of senior time is spent “aligning,” “socialising the deck,” or managing the “meeting before the meeting,” the organisation is signalling something important.
Decisions are expensive.
Clarity is scarce.
Authority is unclear.
Alignment, at scale, is often a substitute for decision design.
If every meaningful move requires multiple conversations before the real conversation, the system is telling you that decision rights are poorly defined.
That’s not a time management issue.
It’s an architectural one.
Priority Dilution
If everything is a priority, nothing is.
Yet many organisations operate with:
Ten or more strategic priorities
Multiple “must-win” themes
Competing transformation agendas
This is rarely accidental.
It is often a leadership choice to avoid the pain of trade-offs.
But strategy without trade-offs is not strategy.
It is aspiration.
And aspiration does not create throughput.
Throughput comes from focus.
Focus comes from constraint.
Constraint comes from design.
The Hero Culture
Every organisation has its heroes:
The person who saves the release
The leader who escalates to unblock
The team that “goes the extra mile”
Celebrated occasionally, this is healthy.
Required routinely, it’s a warning sign.
A system that relies on people staying late, escalating constantly, or firefighting to deliver is a system operating in failure mode.
Heroics are not a performance strategy.
They are a single point of failure disguised as commitment.
Why “try harder” never works
Most improvement efforts quietly assume this logic:
Better people + better tools + better intent = better performance.
Sometimes it does. Briefly.
Then reality reasserts itself.
Because effort is elastic - but systems are not.
People can compensate for poor design for a while:
Working longer hours
Navigating around bottlenecks
Absorbing ambiguity
Using relationships to get things done
But eventually, the system wins.
Queues build.
Decisions stall.
Feedback arrives too late to matter.
And performance plateaus - no matter how committed the teams are.
This is why organisations with exceptional talent still struggle.
Talent does not override design.
It only delays its consequences.
You can buy the fastest hardware on the market, but if the bandwidth is capped at the exchange, the system will still crawl.
Leadership intent ≠ organisational behaviour
Leaders are often sincere about what they want:
“We want teams to take ownership.”
“We want faster decisions.”
“We want to be outcome-led.”
“We want people to challenge us.”
Yet the organisation behaves very differently.
Why?
Because intent is expressed through design, not statements.
If:
Funding is fixed annually
Decisions escalate by default
Risk is punished asymmetrically
Metrics reward activity over impact
Then the organisation will optimise for:
Predictability over learning
Safety over speed
Compliance over judgement
No matter how many town halls say otherwise.
Culture does not drive behaviour.
Structure does.
Culture is what people do in response to the system they operate within.
The Performance Architecture Stack
To make this visible, I use a simple model: the Performance Architecture Stack.
At the top sit the things we talk about most:
Ways of working
Methods and practices
Culture and behaviours
These matter.
But they are downstream.
They rest on layers that shape performance far more:
1. Strategy & Intent
What choices are actually made - and just as importantly, what is not.
2. Governance & Capital Allocation
How capital is allocated, sequenced, and constrained.
Annual funding cycles quietly hard-code annual learning cycles.
3. Decision Rights
Who decides what, where, and when.
If every decision escalates, speed is structurally impossible.
4. Operating Model
How work is structured and flows across boundaries.
This is where queues, handoffs, and friction either appear or disappear.
5. Ways of Working
Methods, frameworks, and rituals.This is where most transformations start.
6. Culture & Behaviours
What people actually do when the pressure is on.
Culture is not installed - it emerges from the layers above.
Most transformations start at layer five.
Some attempt layer six.
Very few redesign the layers underneath - then wonder why nothing sticks.
Changing Jira workflows without changing funding models is like repainting a car with a broken engine.
It looks different.
It drives the same.
If you don’t change the architecture, you don’t change performance.
You just create turbulence.
The shadow operating model
There’s another reality most leaders quietly recognise.
Every organisation has two operating models.
The formal one:
The one on the slide.The one in the handbook.
The one described in transformation decks.
And the shadow one:
The one people actually use to get things done.
The shadow model appears when:
Approval paths are too slow
Funding is too rigid
Decision authority is unclear
Governance forums multiply
So work finds a way around the system.
Decisions happen offline.
Exceptions become the norm.
Relationships outperform process.
When leaders say,“Nothing moves unless I personally get involved", they are describing the shadow operating model.
That’s not a people problem.
It’s a design signal.
The economic cost of design
Structural constraints are not just cultural issues.
They are economic ones.
When a £1m initiative sits in a review committee for three weeks:
Capital is idle
Value is delayed
Opportunity cost accumulates
Risk exposure extends
Throughput is a financial metric, whether we label it that way or not.
Every day of decision latency is a day value is not realised.
In stable environments, organisations can absorb this friction.
In volatile ones, the buffer disappears.
AI, regulatory change, cost pressure, and shifting customer expectations are not creating new problems.
They are exposing old ones.
Many organisations are not working harder because the world changed.
They are working harder because their design no longer fits their environment.
A different starting point
This isn’t an accusation.
It’s an invitation.
Instead of asking:
Why aren’t teams delivering?
Why isn’t Agile working?
Why can’t we scale this?
Start with a different question:
What have we designed this organisation to optimise for?
Predictability?
Control?
Risk minimisation?
Budget adherence?
Those are valid choices.
But they produce predictable outcomes.
Once you can see the system, performance stops being mysterious.
And redesign becomes possible.
The highest-performing organisations don’t demand more effort.
They design for better outcomes.
And that is the difference between managing performance and architecting it.
The mirror test
If you want a simple starting point, try these questions at your next leadership discussion:
How many people must say “yes” for a £50k experiment to start?
When did we last stop a project because strategy changed - not because money ran out?
Is our funding model designed for learning or for compliance?
These are not delivery questions.
They are design questions.
“Every system is perfectly designed to get the results it gets.” - W. Edwards Deming
The line is often quoted as a critique.
It is more useful as a source of optimism.
If results are designed, they can be redesigned.
And that is where real performance work begins.
This article is part of the Performance Architecture Series, exploring how organisations design for sustained performance.
Comments