Essays
-
2026
How Ownership Quietly Disappears
Organisations rarely slow because they grow. They slow because ownership over decisions quietly erodes as they do.
-
2026
Load-Bearing Assumptions
Growth doesn't create problems. It reveals the assumptions an organisation has been depending on without knowing it.
-
2026
The Product Has Changed Jobs
The visible asset is becoming less economically important than the system growing around it.
-
2026
Containment
Great organisations don't eliminate complexity. They decide who carries it.
-
2026
When the Signal Becomes Background Noise
Organisations don't fail because they miss signals. They fail because signals stop feeling like signals.
← Essays
How Ownership Quietly Disappears
There is a conversation that happens in most growing organisations.
It usually begins with a question like: why are decisions taking so long?
The answer that follows is almost always the same. We need better communication. More visibility. Clearer processes. Faster meetings.
These answers are not wrong, exactly. But I've come to think they're rarely the real answer.
The organisations I've worked with that struggle to make decisions quickly don't usually have a communication problem.
They have an ownership problem.
Not ownership in the legal sense. Ownership in the operational sense: who genuinely holds the right to make a decision, the responsibility for its outcome, and the authority to act without seeking permission first.
When that is clear, decisions move quickly. When it isn't, they don't.
I pay close attention to how ordinary decisions actually get made inside organisations. Not the big strategic choices. The everyday ones.
Who feels able to make them without asking. Who waits. Who asks permission even when they technically don't need to. Who gets pulled in even when they have no clear role in the outcome.
These patterns tell me more about how an organisation actually works than any process map or organisational chart.
They show me where authority really sits. Where uncertainty exists. What behaviour the organisation is quietly rewarding.
Here is what I've noticed.
In the early stages of most organisations, ownership is obvious. There are few enough people that responsibility is naturally clear. Decisions get made because it's obvious who should make them.
As organisations grow, that clarity erodes. Not suddenly, and not because anyone decides to let it. It erodes gradually, through the accumulation of small changes that each seem reasonable at the time.
A new layer of management is added. A process is introduced to ensure consistency. Sign-off requirements expand after something goes wrong. Coordination mechanisms multiply to manage the complexity of more people doing more things.
Each of these changes makes sense in isolation. Collectively, they produce something nobody intended: an organisation where it's no longer clear who owns what, and where the path of least resistance is to involve more people rather than fewer.
This is what I mean when I say ownership quietly disappears.
It doesn't leave all at once. It dissolves gradually, replaced by a kind of distributed responsibility that belongs to everyone in general and no one in particular.
The meeting gets called to align stakeholders. The decision gets deferred pending further review. The email chain grows longer. The outcome gets delayed.
And the organisation looks at the slowness and concludes: we have a communication problem.
The fix is rarely more communication.
It's usually a much more uncomfortable conversation about who actually owns this decision, what that ownership means in practice, and what needs to change structurally to make that clear.
That conversation is harder to have than improving communication. It involves clarifying accountability in ways that some people find exposing. It requires leaders to give up involvement in decisions they've grown used to being involved in.
But it's the conversation that moves things.
The question I find most useful isn't: how do we improve communication?
It's: who actually owns this decision?
Not who approves it. Not who influences it. Not who needs to be informed.
Who owns the outcome?
That question, asked clearly and answered honestly, usually reveals more about why an organisation is slowing down than any number of communication audits or process reviews.
Ownership quietly disappears. The work of leadership is to notice when it has, and to restore it deliberately before the organisation forgets what it felt like to move.
← Essays
Load-Bearing Assumptions
There is a story we tell ourselves about growth.
Communication breaks down. Culture changes. People stop collaborating the way they once did. Decisions slow. Bureaucracy appears. The organisation that once moved quickly begins to feel like it's moving through water.
We've all heard it.
Most of us have probably said it.
Growth, the story goes, creates these problems.
I'm not sure that's true.
I've watched organisations grow. I've been inside them at different stages: as a clinician, as a founder, as someone brought in to understand why something that once worked had stopped working.
It looked more like exposure.
When my own business grew from one person to more than sixty employees across three locations, I started noticing something I hadn't expected.
Many of the things I'd assumed were strengths weren't strengths at all.
They were conditions.
I could overhear most conversations. Not because I'd designed a communication system. Because the office was small enough that I didn't need one.
Everyone knew where decisions were made. Not because we had clear governance. Because there were so few of us that asking was faster than documenting.
If something felt off, someone would mention it. Not because we had feedback structures. Because people sat close enough to each other that information moved without effort.
None of these had been built.
They had simply existed.
And for a long time, I'd confused existing with working.
Looking back, I realised those conditions had something in common.
They were assumptions that had quietly become load-bearing.
Nobody had designed them. Nobody had named them. Nobody had considered what would happen when the organisation grew beyond the conditions that made them possible.
When the business expanded, they didn't fail dramatically. They simply disappeared. And the organisation discovered, slowly and uncomfortably, how much weight they had been carrying all along.
Every organisation has them.
The founder who naturally fills the gaps between roles because they're always there to notice them.
The shared knowledge that lives in no document but somehow everyone understands.
The trust that moves information through relationships rather than formal structures.
These aren't weaknesses waiting to be discovered. Most of the time, they're genuine strengths. The assumption, and this is where it quietly becomes dangerous, is that they'll continue to work as the organisation changes around them.
Growth doesn't destroy these things directly.
It removes the conditions that made them possible.
The office expands. People stop sitting near each other. The founder's attention, once available to everyone, becomes finite. The new hire doesn't know who to ask, because the answer to that question exists only in the memory of people who've been there long enough to remember.
By the time the organisation notices something is wrong, the symptoms have usually been visible for a while. Decisions are slower. Communication is harder. Collaboration requires more effort than it once did. The organisation begins running more meetings to compensate for the information that used to move without them.
And here is where the misdiagnosis almost always happens.
The organisation looks at what's appeared: the slowness, the friction, the breakdown in communication, and concludes that growth created these problems.
It didn't.
Growth revealed which assumptions were no longer being supported by the conditions that had quietly sustained them.
The assumption was old.
The symptom was new.
Most organisations spend their energy treating the symptom.
I've learned to ask a different set of questions.
Not: what problems has growth created?
But: what did this organisation depend on that growth has now removed?
What moved without effort when the organisation was smaller?
What was known without being written down?
What decisions were made without process, because proximity made process unnecessary?
The answers rarely appear in organisational charts or strategy documents.
They appear in the gaps: in what people reach for instinctively before realising it's no longer there.
Growth rarely creates the organisation you're becoming.
It reveals the organisation you've already built.
← Essays
The Product Has Changed Jobs
Over the past few years, I've found myself noticing the same pattern in places that appeared to have very little in common.
The NFL.
Formula 1.
Apple.
Disney.
At first, I assumed the similarities were superficial.
Eventually, I realised they were structural.
In 2009, the NFL launched Flag Football.
At first glance, it looked like a participation initiative. A way to grow the sport. Get more children playing.
Here's another way to read it.
Every child who plays Flag Football becomes something. A fan. A viewer. A parent who watches on Sunday. Someone for whom the NFL is not a league they follow but an identity they carry.
The NFL wasn't simply creating more players.
It was building the base of people for whom football would always matter.
The game was the visible thing. What the NFL was actually building was much harder to see.
When Liberty Media acquired Formula 1 in 2017, the sport looked roughly the same on the surface. The cars still raced. The championship still unfolded across twenty-something weekends. The fastest team still won.
What changed was everything around it.
Content. Storytelling. Digital distribution. Race weekend experiences designed for people who had never watched a race before. Sponsorship inventory that hadn't previously existed. A documentary series that introduced millions of people to drivers, teams and rivalries they had no reason to care about until suddenly they did.
Liberty didn't make Formula 1 faster.
They asked a different question entirely: what could exist around the race that doesn't exist yet?
The race remained. But its role quietly changed. It stopped being the destination and started being the reason everything else was possible. Every piece of content, every new fan, every sponsorship conversation, every sold-out grandstand in a city that had never hosted a race: all of it depended on the race existing. But none of it was the race.
That's the clearest example I've found of what I kept seeing everywhere.
Apple sells phones.
That sentence was true in 2007. It becomes less precise every year.
What Apple has built around the phone: payments, health monitoring, identity, streaming, subscriptions, services, now generates more revenue than most companies generate in total. Without the phone, none of it works.
But the phone is no longer the point.
It's the entry point.
What's interesting is that Apple never announced this transition. There was no moment where they said: we are becoming something different. The product stayed visible. The business quietly changed shape around it.
Disney made films.
For decades, that was the business. The studio. The stories. The characters.
Then something happened that took time to fully understand. The characters didn't stay in the films. They moved. Into parks. Into hotels. Into merchandise, cruises, streaming platforms, licensing agreements that span industries and decades.
A Disney film now does something its creators in the 1930s couldn't have imagined. It introduces a character who will generate value for fifty years across businesses that didn't exist when the film was made.
The film is still important. But its job has changed.
It used to be the product.
Now it's the introduction.
Four industries. Four organisations. Apparently nothing in common.
Except this.
In each case, the visible thing: the game, the race, the phone, the film, remained. It didn't diminish. If anything, it became more important, because more things depended on it.
But its role changed.
It moved from destination to gateway. From the thing people came for to the thing that made everything else possible.
The product didn't disappear.
It changed jobs.
That's the shift I kept seeing. The visible asset remained essential. But its purpose had changed. It no longer existed only to create value directly. It increasingly existed to make other forms of value possible.
This pattern tends to follow the same movement.
First, the visible asset is the business. It attracts attention, generates revenue, creates reputation. Everything serves it.
Then, gradually, things accumulate around it. Experiences. Communities. Services. Relationships that outlast any single transaction.
Then something shifts. The asset that once stood alone becomes the centre of something much larger. It still matters, perhaps more than ever, but its primary job is no longer to be the product. Its primary job is to anchor everything that has grown around it.
By the time most people notice this has happened, the organisations that understood it earliest have already built something very difficult to replicate.
The organisations that endure don't always create better products.
Increasingly, they create better systems around them.
By the time everyone else notices, the product hasn't disappeared.
It has simply changed jobs.
← Essays
Containment
It was the week of the Hungarian Grand Prix.
I was already exhausted. I'd been commuting between the F1 calendar and California for months, trying to run a multi-location business from the other side of the world while staying present enough in both places to be useful in either. By the time I arrived in Budapest, I was running on very little.
I checked into the team hotel.
Or tried to.
They had double-booked my room. The other guest had already checked in. After a series of calls to their customer service line: calls that went nowhere, they arranged another hotel across the city, assured me it had availability, and put me in a taxi.
It didn't have availability.
The second hotel had inherited a problem they hadn't created and wanted no part of it. They wouldn't make calls. They wouldn't take responsibility. As far as they were concerned, this was someone else's problem, not theirs.
Which left me standing in a hotel lobby at close to midnight with nowhere to go.
I spent the next two hours calling hotels, calling the team hotel again, and working through a mental list of colleagues I hoped I wouldn't have to wake at 2am.
I called the Kempinski without any particular expectation.
I had no reservation. No loyalty status in Budapest. No claim on them whatsoever.
The person who answered said: "Come over. We'll figure something out."
It was around 2am when I arrived.
They did exactly what they said they would. Calmly. Without making the situation feel like my problem to carry. They found me a temporary suite for the night, fed me, and moved me into a regular room the next day once space opened up.
I've stayed loyal to that brand ever since.
Not because the evening went well.
Because of what the Kempinski chose to do with a problem that was never theirs.
Three organisations. The same problem passed between them. Two transferred it. One absorbed it.
That night, I didn't have language for what I'd experienced.
I just knew something had worked completely differently.
It was only later: watching other systems operate under pressure, in very different environments, that I started to understand what I'd actually experienced.
At the 2023 Qatar Grand Prix, McLaren completed a pit stop in 1.80 seconds.
From the outside, it looks almost simple. The car arrives. Four tyres change. The car leaves.
What makes it possible has almost nothing to do with those 1.80 seconds.
It's the strategy discussions held days before. The choreography rehearsed hundreds of times. The wheel-gun practice. The telemetry. The scenario planning for failures that never happened. The communication protocols refined until they required almost no communication at all.
By the time the car arrives, the complexity has already been absorbed.
The driver receives stillness.
I spent years working as a clinician before I became a founder.
When a complex patient walks in: an elite athlete, six months before a major competition, carrying anxiety from coaches and agents and sponsors and the quiet terror of not knowing whether their body will hold, the room contains an enormous amount of competing pressure.
My job was never to eliminate that pressure.
It was to decide where it lived.
The athlete shouldn't leave carrying my diagnostic process. The hypotheses I was testing. The uncertainty I was working through. The differential I was building between referred pain and a structural issue and something further up the chain.
That was my cognitive load to carry.
The athlete had enough of their own.
What the athlete left with was a plan.
"Here's what we're doing today."
The complexity didn't disappear. It was contained.
This is the thing I've come to notice most clearly in organisations under pressure.
Not whether they have problems.
Every organisation has problems.
But what they do with the complexity those problems create.
Some organisations absorb it. They decide who carries it.
Others transfer it. Outward. To customers. To frontline staff. To whoever is least equipped to absorb it.
The difference isn't visible under normal conditions.
Both types of organisation can look impressive when things go according to plan.
The real differentiator appears under friction.
When timelines slip. When plans fail. When pressure arrives unexpectedly.
That's when you discover whether the system absorbs complexity or transfers it.
The best organisations I've worked with have made a deliberate decision about who carries the complexity required to serve the people depending on them.
Not by eliminating it.
Not by pretending it doesn't exist.
By deciding, clearly and in advance, that it won't reach the people it would damage most.
The Kempinski didn't solve the problem before I arrived.
They made sure I never had to carry it.
Great organisations don't eliminate complexity.
They carry it so others don't have to.
← Essays
When the Signal Becomes Background Noise
Every organisation has experienced this moment.
Someone new joins the team.
A few weeks later, they ask a question that catches everyone slightly off guard.
"Why do we do it this way?"
The room goes quiet.
Not because the answer is complicated.
Because nobody has asked the question for a very long time.
The new person hasn't discovered something hidden.
They've simply noticed something everyone else stopped seeing.
A dashboard that nobody quite trusts, but everyone knows how to read anyway.
An approval step that adds no value, but has existed for so long nobody thinks to question it.
A customer complaint that arrives often enough to become a category rather than a warning.
A delayed decision that gradually stops feeling delayed because everyone has quietly adjusted their expectations around it.
None of these changes happen all at once.
Each one makes the signal a little quieter.
The unusual becomes familiar.
The familiar becomes expected.
And expected things stop generating questions.
The organisation didn't ignore the problem.
It adapted to it.
Consider what adaptation actually looks like from the inside.
The analyst who updates the dashboard every Monday and mentally adds ten percent to every number before sharing it. Not because she's been told to. Because she's learned to. The adjustment has become so automatic she no longer thinks of it as an adjustment.
The project manager who builds an extra two weeks into every timeline. Not because the work requires it. Because decisions always arrive late, and he stopped waiting for that to change.
The customer service team with a template for the complaint that lands every week. Efficient. Professional. Completely indistinguishable from a team that has decided the complaint is simply part of the service.
The leadership team that schedules a monthly review to discuss a problem they've been discussing for eighteen months.
None of these people are failing.
They're doing exactly what capable people do.
They adapt.
That's what makes it so difficult to see.
The organisation hasn't become less competent.
It has become competent at functioning despite something it should have fixed.
This is what makes organisational drift so difficult to diagnose.
It doesn't arrive as a failure.
It arrives as a series of reasonable decisions.
Each one logical in isolation.
Each one making the organisation slightly better at tolerating something it should be changing.
The signal doesn't disappear.
It simply stops feeling like one.
Think about what happens to a signal the first time it appears.
It registers.
People notice.
Questions get asked.
Sometimes action follows.
Sometimes it doesn't.
But either way, the signal has been seen.
The second time, it registers a little less.
The third time, someone mentions it almost as an aside.
By the tenth time, it has a name.
By the fiftieth, it has a process.
The organisation hasn't solved the problem.
It has built infrastructure around it.
Organisations adapt to signals faster than they solve them.
And every adaptation makes the signal quieter.
Not because the problem has changed.
Because the organisation has.
There is a word for what happens next.
Drift.
Not a decision.
Not a failure.
Not a moment anyone can point to.
Just the slow accumulation of adaptations that move the organisation away from the standards it once held: without anyone noticing the distance travelled.
Drift is difficult to see from the inside precisely because it happens through normal behaviour.
People doing their jobs.
Teams solving today's problems.
Leaders managing what's in front of them.
Nobody intending to lower the standard.
Nobody realising the standard has moved.
This is why the new employee's question is so valuable.
Not because they have better answers.
Because they haven't adapted yet.
They're still seeing the organisation as it is rather than as everyone else has learned to experience it.
That gap: between what the newcomer sees and what everyone else has stopped seeing, is one of the most accurate measures of organisational drift available.
Most organisations don't measure it.
Most don't even notice it closing.
Within a few months, the new employee stops asking.
Not because the questions have been answered.
Because they've adapted too.
The question worth asking isn't whether your organisation has signals.
Every organisation has signals.
The question is how long they remain signals.
At what point does the unusual become familiar?
At what point does the familiar stop generating questions?
At what point does the workaround become the process?
These aren't dramatic moments.
They rarely announce themselves.
They accumulate quietly, in the background, until the day someone new walks in and asks a question that stops the room.
The day a warning becomes routine is the day it stops being a warning.
Notes
-
2026
Notes on Organisations
Observations that have continued to prove useful across different industries and environments.
-
2026
Questions I Ask
I don't begin with solutions. I begin by trying to understand why the system is producing the outcome I'm seeing.
← Notes
Notes on Organisations
Over time, I've found myself asking the same question again and again:
What conditions produced this outcome?
The industries have changed. The people have changed. The patterns rarely do.
These are some of the observations that continue to shape how I think.
The visible problem is rarely where the real leverage sits.
Most organisations describe symptoms. Slow decisions. Missed deadlines. Poor communication. High turnover. Those problems matter. They just rarely explain themselves. The more useful question is usually: what conditions produced this?
Decisions reveal how an organisation really works.
I pay close attention to ordinary decisions. Who feels able to make them. Who waits. Who asks permission. Who becomes involved. Decision making reveals far more than process maps or organisational charts. It shows where authority really sits. How information moves. Where uncertainty exists. What behaviour the organisation quietly rewards. Many organisations don't have a communication problem. They have a decision architecture that no longer matches the organisation they've become.
People usually behave rationally.
When capable people repeatedly behave in ways that seem irrational, I assume there is something about the environment I haven't understood yet. People respond to incentives. To uncertainty. To experience. To what carries risk. Behaviour usually makes sense once the conditions become visible.
Every system is perfectly designed to produce its current behaviour.
If a pattern keeps repeating, I don't assume it's coincidence. Or bad luck. Or simply the wrong people. I assume something is reinforcing it. The question isn't who caused the problem. It's what allows the problem to continue.
Organisations teach people how to behave.
Not primarily through values. Through experience. People learn where decisions are really made. They learn what earns recognition. What gets challenged. What quietly disappears. Every organisation teaches. Whether it intends to or not.
Growth reveals what no longer fits.
Growth rarely creates new problems. More often, it exposes assumptions that quietly stopped working. The conversations that once happened naturally now require meetings. Decisions that once took minutes now take weeks. Work that once flowed easily begins to hesitate. Growth reveals which parts of the organisation never evolved with it.
Mistakes are information.
The mistake itself is rarely the most valuable part. The response is. The strongest organisations don't simply recover. They learn. They redesign. They reduce the likelihood of making the same mistake twice. They also learn from mistakes that aren't their own.
Good decisions avoid creating tomorrow's problems.
Every decision solves something. The question is what it creates in return. The strongest organisations resist solving immediate problems in ways that quietly limit future choices. They leave room to adapt. To learn. To decide again.
Performance is built long before it becomes visible.
Most outcomes are downstream. Preparation. Trust. Communication. Decision quality. Role clarity. By the time performance becomes visible, much of the work that created it has already happened. Performance accumulates long before it appears.
Leadership shapes environments.
Leaders influence behaviour less through instruction than through the conditions they create. People adapt remarkably quickly. The environment always teaches. The only question is what it's teaching.
I don't think organisations need more complexity.
I think they need a clearer understanding of the conditions producing the behaviours they're experiencing.
Once those conditions become visible, the path forward is often much simpler than it first appeared.
← Notes
Questions I Ask
I don't begin with solutions.
I begin by trying to understand why the system is producing the outcome I'm seeing.
Most organisations can describe the problem. I'm usually more interested in understanding the conditions that made it possible.
These are the questions I find myself returning to.
What problem are we actually trying to solve?
The stated problem and the real problem are not always the same. Before changing anything, I want to know whether everyone is trying to solve the same problem.
What changed?
Problems rarely appear without something changing first. Growth. Leadership. Structure. Market conditions. Expectations. The change itself is often more informative than the symptom.
Where does work hesitate?
Not where it stops. Where it hesitates. Where do decisions slow? Where do conversations repeat? Where does confidence disappear? Hesitation usually tells me uncertainty exists. The next question is why.
Who owns this decision?
Not who approves it. Not who influences it. Who genuinely owns the outcome? Ownership tells me more about an organisation than an organisation chart ever will.
Why does this behaviour make sense?
If capable people repeatedly behave in ways that seem irrational, I assume I'm missing part of the picture. Behaviour usually becomes understandable once the conditions become visible.
What is the organisation teaching people?
Every organisation teaches. The question is what. What behaviour is rewarded? What behaviour carries risk? What behaviour quietly disappears? Culture is often the result of these lessons rather than the cause of them.
Where does information stop being information?
Where does observation become interpretation? Where does interpretation become assumption? By the time information reaches the point where decisions are made, what has changed?
Which assumptions no longer fit reality?
Success changes assumptions. Growth changes assumptions. Markets change assumptions. The most dangerous assumptions are often the ones that still feel true.
If we replaced the people, would the problem remain?
If the answer is yes, replacing people won't solve it. It will simply delay understanding it.
What isn't being discussed?
Every organisation has conversations that happen repeatedly. It also has conversations that never happen. Sometimes silence tells me more than discussion.
If I followed one piece of work from beginning to end, what would I learn?
Not from the process map. From the work itself. Where does it hesitate? Where does it change hands? Where does it wait? Where does it become more complicated than it needs to be? Following the work usually reveals the organisation people experience rather than the one they describe.
Good diagnosis rarely begins with answers.
It begins with better questions.
The quality of those questions determines everything that follows.