The pile rarely looks like a crisis. It looks like a few extra items on the list. A code review waiting for sign-off. A budget line needing one more approval. A hire that could have been made two levels down but somehow needed the founder’s read first. Each item, on its own, seems small enough to justify keeping.

What is easy to miss is where these items came from. They were not created by the founder. They were routed there, by a structure that never quite assigned the decision to anyone else, or assigned it in name but not in practice. The org chart says the decision belongs to a manager. The daily reality says it lands back on the same desk it always has.

This is the part that stays invisible longest. It doesn’t look like a bottleneck from the top. It looks like a bit more work, a bit more context-switching, a bit more “let me just handle this one, it’s faster.” What it actually is: thinking time and deep work time, spent instead on decisions that were never meant to require the founder’s attention in the first place.

The cost does not stop at the desk. Every decision sitting in that pile has people on the other end of it, waiting. A team that can’t ship until the review comes back. A department that can’t hire until the number is confirmed. Those people don’t wait quietly. They stop, they start something else, they come back, they stop again. Context-switching has a cost of its own, and it is being paid by people who did nothing to cause the delay.

So the pile is doing two things at once. It is stopping the founder from moving the needle on the work only they can do. And it is stopping entire teams from moving on the work only they can do. Neither of these costs shows up on a dashboard. Both compound, week after week, long before anyone names what is happening.

The instinct, once this is noticed, is to look at the people. The manager who keeps escalating. The team that keeps waiting instead of deciding. But the pattern rarely traces back to a person. It traces back to where a decision actually sits versus where the structure says it sits, and how much information, trust, or authority was actually transferred along with the responsibility. Escalation is not a character flaw. It is what happens when a structure quietly makes escalation the safer choice.

None of this is solved by working faster, delegating more forcefully, or asking people to “just decide.” The pile is not a motivation problem. It is a structural one, and structural problems are visible only once someone stops asking who is slow.

It isn’t the obvious kind, the ones you’ll find named in a management book, with a chapter and a checklist attached. It’s the kind that compounds quietly, in places you’re not watching: in how fast your organisation actually moves, in how confident your team feels making a call without you, in how much room you have left to think clearly. And then one day the company simply feels heavier than it should, slower than it should, and you’re not entirely sure why.

What follows are ten costs. But I want to be precise about something before we start, because it changes how you’ll read the rest of this: these are not ten separate problems. They are ten expressions of a single structural pattern. Once you can see that, you’ll start noticing it everywhere: in your calendar, in your leadership team, in habits you didn’t think were costing you anything.

Subscribe now

It’s worth saying clearly, too: this isn’t an argument that founders should never be central. In the earliest stage of a company, the founder is the structure. Every decision genuinely should run through them, because there’s no one else yet with the context to make it well. That’s not a flaw to fix. It’s the right architecture for that stage.

The problem isn’t the founder-centred structure itself. It’s that most companies never redesign it. They keep the early-stage architecture running long after the company has outgrown it, and the same structure that made the company possible at ten people is what quietly slows it down at a hundred.

I’ve spent years inside organisations at exactly the point where growth stops feeling like momentum and starts feeling like friction. I’ve sat in most of the seats in that room. As a developer, a team lead, a CEO, a board member, an investor. Underneath, no matter the industry or the stage, it’s always the same architecture wearing a different surface.

So let’s look at it properly.

Cost 1: Speed

When too many decisions sit with the CEO, the organisation slows down. Not dramatically, not all at once, but gradually, the way water finds every low point in a floor. Everything ends up waiting on the same person’s attention. Small issues escalate because nobody quite has permission to close them out. Opportunities pass not because the company lacked the capability to act, but because it lacked the authority to act without asking first.

What makes this cost so hard to see is that the CEO often looks fast. They respond quickly, they’re always reachable, always in the loop. The slowness never shows up in the CEO’s own behaviour, it shows up in the growing gap between what the market needs and what the organisation can actually deliver while waiting for one person’s bandwidth.

So the delay stays invisible for a long time. By the time someone finally names it, the company has usually been losing ground quietly for months, sometimes years.

The right question was never how fast the CEO is. It’s how fast the organisation moves when the CEO isn’t in the room.

Cost 2: Scalability

A business can’t grow cleanly if its growth depends on one person being involved in too many details, and this ceiling tends to arrive earlier than most CEOs expect. The company might still be hitting its targets. It might still look, from the outside, like it’s working hard and winning. But underneath, it isn’t building capacity. It’s building dependence. And for a long stretch, those two things are almost impossible to tell apart.

Dependence looks exactly like capacity, right up until the organisation has to function without the CEO at the centre of it. That’s the moment the real architecture reveals itself.

What makes this cost expensive isn’t just today’s ceiling. It’s that it compounds. A structure built on dependence doesn’t scale in a straight line; it gets harder at every stage. What worked at twenty people creates friction at fifty. What felt manageable at fifty becomes genuinely painful at a hundred and fifty.

So the scalability cost was never just about the ceiling you’re at now. It’s about every ceiling after this one.

Cost 3: Quality of Judgment

This is the one most CEOs are least prepared to hear: their own judgment might be part of the problem.

The assumption is that the CEO makes the best decisions because they’re at the top, they have the most context, the most experience, the sharpest pattern recognition. That assumption skips over one variable entirely: overload.

The more decisions a CEO carries, the more decision fatigue sets in. And under fatigue, people default to speed, habit, or control, not depth. This isn’t a willpower problem. It’s structural. A brain under cognitive load simply doesn’t perform the same as a brain with room to think.

The CEO who insists on being in every decision isn’t protecting the quality of those decisions. They’re quietly degrading it.

And the work that suffers first is always the work only they can do: strategy, trade-offs, the long view.

Cost 4: Team Development

When a CEO keeps pulling decisions back to themselves, the people around them don’t get the room to grow into bigger ones. Nobody teaches them to wait for approval. They learn it the same way a child learns which parent to ask first, not because anyone said so, but because that’s reliably where the answer comes from fastest.

Instead of a strong leadership bench, the organisation ends up with people trained to defer upward. Ownership weakens. Learning slows. And succession, years later, becomes far harder than it needed to be, because the capability that should have been developing all along simply wasn’t given the space to.

The part that tends to land hardest is that the CEO usually has no idea this is happening. They’re not trying to hold their team back. Most of the time they genuinely believe the opposite, that staying involved is how they add value, how they maintain the standard.

So the damage is never visible in any single moment. It only becomes visible in the aggregate. When you notice the same decisions keep landing on the same desk, and a team that’s clearly capable of more is still, quietly, waiting for a signal.

Cost 5: Culture

A company led by a CEO who does everything personally can slowly become a company shaped by caution and dependence, without anyone ever choosing that culture on purpose. Culture was never really about what gets said in the all-hands. It’s about what the structure rewards.

When the structure rewards escalation over initiative, people escalate. When it rewards waiting over deciding, people wait. Over time, the organisation fills up with capable people who aren’t quite allowed to be capable.

That’s expensive, not in a line-item way, but the way compound interest is expensive: every month that capable people operate below their real capacity is a month of output, growth, and resilience that simply never happened.

And the part worth sitting with is that this pattern doesn’t need the CEO to keep maintaining it. Once it’s established, the team maintains it themselves, because that’s exactly what the invisible structure has taught them to do.

So the cultural cost was never really a leadership problem alone. It’s an architectural one.

Subscribe now

Cost 6: The Emotional Cost to the Team

This one is emotional, and almost nobody says it out loud.

Employees often experience a non-delegating CEO as someone who doesn’t quite trust them. Nobody announces that. It’s felt. In the repeated check-ins, in decisions that come back revised, in the quiet sense that their judgment is always provisional, never final.

For your strongest performers, this corrodes something. They joined for responsibility. They stayed because they believed in the work. But if the structure keeps signalling that their calls will be reviewed, adjusted, or overridden, they start to feel underused. Micromanaged. Eventually invisible.

That feeling turns into disengagement. Disengagement turns into departure.

The company loses precisely the people it most needed to keep.

Cost 7: The Personal Cost to the CEO

The CEO may be carrying too much, working too late, living in a near-constant state of mental activation, and that’s not a productivity problem. It’s a sustainability one.

Burnout risk. Disrupted sleep. A shrinking capacity to think at the level the role actually demands. None of this is a sign of weakness. It’s a sign of a structural mismatch between what one person is carrying and what any one person can sustainably hold.

What makes this cost so hard to address is that the CEO rarely experiences it as a cost at all. They experience it as commitment. As accountability. As simply what the job requires. So the signal that something is structurally wrong gets reinterpreted as a reason to push harder, and pushing harder inside a structure that’s already overloaded doesn’t resolve anything. It accelerates it.

A CEO who spends every day solving immediate problems has very little left for the work only they can do: setting direction, making the real trade-offs, shaping culture, building what comes next. The irony is almost too precise. The CEO holding on to everything is often the one doing the least of what the company actually needs from them.

Cost 8: The Cost Beyond the Company

This one reaches past the organisation entirely.

Family and friends absorb the strain of long hours and constant availability, usually without saying much about it. They see the exhaustion. They feel the distraction. They notice the version of the CEO who’s physically present but still, somewhere, at work.

It isn’t only about fewer hours at home, it’s the slow erosion of attention, recovery, and connection. The things that are hardest to rebuild once they’ve quietly gone.

This one almost never gets named in a business context, because it feels personal rather than professional. But it belongs on this list, because it shapes everything else. A CEO who can’t recover, who can’t be genuinely present outside of work, is a CEO whose strategic capacity is depleting in the background. And the people who depend on them, at work and at home, usually feel that depletion before the CEO does.

Cost 9: Investor Confidence

This one is structural, and it becomes visible to people outside the organisation before it’s visible inside it.

Investors often tolerate, even value, a founder-centric style early on. In the first stages, the founder being at the centre of everything is often the company’s greatest asset: their judgment, their relationships, their speed.

But that changes. Over time, investors start looking for something else entirely: a company that can function without one person at the centre of it. If too much still depends on the CEO, what they see is concentration risk, succession risk, execution risk.

The business can be genuinely strong today and still look structurally weak tomorrow. And structural weakness, once it’s visible, gets priced in, into valuations, into board conversations, into how confidently investors back the next round of growth.

What feels, from the inside, like a leadership style is being read, from the outside, as a risk profile. Two entirely different conversations, happening at the same time, about exactly the same pattern.

Cost 10: Resilience

This one only becomes visible when something changes.

A company where the CEO makes everything can run for a long time, especially if the CEO is talented, energetic, and fully committed. But resilience was never about how well things run when everything’s going well. It’s about what holds up when conditions shift, growth accelerates, or the CEO simply isn’t there.

A non-delegating organisation is almost always more brittle than it looks, because its strength is concentrated rather than distributed. The capability exists. It’s just held in one place. And anything held in one place is one point of failure.

The real test isn’t what happens on a good week. It’s what happens when the CEO is sick, or travelling, or simply unreachable for a few days. Does the organisation keep moving? Or does it wait?

Most CEOs already know the answer, if they’re honest with themselves. They feel it in the messages waiting when they get back. They feel it in the decisions that were held rather than made. They feel it, most of all, in the quiet relief on the team’s face when they walk back through the door.

That relief was never a compliment. It was a signal.

Why This Doesn’t Change Through Understanding Alone

Here’s what I want to name directly, because most writing on this topic stops one layer too early.

Delegation sounds simple. It rarely is. Most CEOs don’t fail to delegate because they misunderstand the concept, they’ve read the same books everyone else has. They fail because letting go asks for trust, patience, and a real tolerance for watching things happen imperfectly. It asks them to let people learn in public: to watch someone make a call they would have made differently, and not step in.

But the deepest barrier isn’t any of that. It’s this: delegation asks the CEO to give up the emotional reward of being the person with the answers. That’s not a process to install. It’s not a communication tactic you can roll out at an all-hands. It’s a habit wound into identity, into self-worth, into the story of how the company got here in the first place, usually because the CEO’s answers were the right ones, for a long time.

No operational framework touches that layer. Which is exactly why most delegation efforts don’t hold. The framework gets implemented. The habit underneath stays exactly where it was. And within a few months, the decisions have quietly found their way back to the top again.

So non-delegation was never really a time-management problem. It’s a leadership problem, a cultural problem, a structural problem, and a personal one, all at once. And it shapes how the company grows, how people develop, how decisions get made, and how sustainable the CEO’s own life becomes.

The cost is invisible at first. Then it compounds quietly, until the organisation feels heavier, slower, and more dependent than it ever needed to be.

The real question was never whether the CEO is working hard enough. It’s whether the company is becoming capable enough without them.

Subscribe now

Ten costs. One structural pattern.

Speed. Scalability. The quality of your own judgment. How your team develops, or doesn’t. What your culture quietly rewards. What your best people feel but rarely say out loud. What it costs you personally, and what it costs the people who live with you. What your investors see before you do. And how your organisation holds up the one time it actually needs to.

None of these announce themselves. That’s what makes them expensive: they build in the background while the CEO looks committed, fast, accountable, entirely on top of things. The damage isn’t visible until, quite suddenly, it is.

The goal was never a better CEO. It’s an organisation that no longer needs one to function at all. That’s the architecture worth building, and it’s rarely built by trying harder inside the same structure.

If any of this landed less like an idea and more like something you recognised, not abstractly, but in your own company, that’s worth a closer look. Book a call with me and let’s look at the architecture underneath it.

Myrto Zehnder helps CEOs and founders of scaling companies fix the decision architecture behind their recurring problems.

Some of the most costly failures I’ve seen were the result of good decisions, made in the wrong order.

The restructure that was necessary, but happened before the leadership team had the clarity to execute it. The strategy that was correct, but was communicated before the organisation had the stability to absorb it. The senior hire that was the right person, brought in at a moment when the role they were hired into didn’t yet exist in any functional sense. The accountability conversation that was overdue, but happened after trust had already collapsed, and so landed as confirmation of what people feared rather than as a course correction.

Subscribe now

Sequence Failure is the pattern that emerges when the right intervention meets the wrong moment.

It is the hardest pattern to see in advance. The decision looks correct in isolation. The analysis is sound. The reasoning holds. What isn’t visible is the structural readiness of the organisation to receive it, and what happens when something arrives before the conditions for it exist.

A building that needs a new floor doesn’t benefit from the floor being installed before the foundations are reinforced. The floor is right. The sequence is wrong. The result is damage that has to be undone before the original work can begin.

Organisations are not buildings. But they have an equivalent logic. Certain structural conditions have to exist before certain interventions can hold.

When those conditions aren’t present, the right move uses the window and closes it. The organisation becomes harder to change, not easier, because the intervention produced a reaction that now has to be managed.

Sequence Failure is rarely diagnosed as such. The intervention is assessed on its own merits. The timing is not. So the conclusion is usually that the decision was wrong, or the execution was poor, or the people weren’t ready.

The sequence was wrong. That’s a different problem, with a different answer.

Myrto Zehnder partners with CEOs and founders of scaling organisations on the structural architecture underneath recurring organisational problems. This is the seventh in a series on seven patterns from the field.

The Eagle’s Perspective — myrtozehnder.com

The CEO has solved a problem. Properly solved it, not patched it. They brought in the right person, restructured the function, clarified the process, had the difficult conversation. For a period, things improve.

And then, some months later, something appears. It’s not identical to the original problem. But it has the same shape. The same feel. The same location in the organisation.

We’ve been here before.

Structural Recurrence is not the same problem returning. It is the same structure generating a new instance of the same problem. The condition that produced the original issue was never addressed, because it was never identified. The solution was applied to the symptom. The architecture underneath it remained.

This is why the problem comes back in a different form. The structure keeps producing pressure. The pressure finds the nearest available outlet. When that outlet is closed, it finds another.

A team that kept losing senior people. Different people, different reasons given, different exit interviews. The same structural condition underneath, producing the same pressure on everyone who stepped into that layer of the organisation.

A decision that kept arriving on the CEO’s desk despite repeated attempts to push it down. Different topics, different functions, different people bringing it. The same gap in decision authority generating the same gravity upward.

An initiative that stalled at the same stage three times across three years. Different teams, different sponsors, different names given to the project. The same structural sequence failure occurring at the same inflection point every time.

The problem is not recurring. The structure is.

Myrto Zehnder partners with CEOs and founders of scaling organisations on the structural architecture underneath recurring organisational problems. This is the sixth in a series on seven patterns from the field.

The Eagle’s Perspective — myrtozehnder.com

None of them capture the cost I’m describing.

Structural Tax is the accumulated cost of operating inside a system that isn’t working. It doesn’t appear in the P&L. It doesn’t show up in the board pack. It accumulates in the hours spent in meetings that produce no decision. In the decisions that get made, unmade, and remade because the authority to hold them never existed in the first place. In the senior people whose capacity is consumed by coordination work the structure should be doing for them. In the hires that don’t stick because the role they were hired into was never properly defined. In the initiatives that stall at the same point every time, for the same structural reason, which nobody has named.

It is a tax on everything else the organisation is trying to do.

The reason it stays invisible is that it has no line item. The meeting that takes three hours instead of forty minutes because nobody has decision authority is filed under leadership time. The senior hire who leaves after eighteen months because the role was structurally impossible is filed under attrition. The initiative that didn’t deliver is filed under execution failure. The costs are real. The structural source of them is not recorded anywhere.

This is not accidental. Organisations are better at measuring outputs than at measuring the friction that reduces them. And structural friction is particularly hard to measure because it is distributed across people, functions, and time in ways that make the pattern invisible unless you’re looking for it specifically.

What I find, consistently, is that the organisations paying the highest structural tax are also the ones least aware of it. The cost has been normalised. This is just how things work here. This is what growth looks like. This is the price of complexity.

It isn’t. It’s the price of a structure that hasn’t kept pace with the organisation it’s supposed to be running.

Myrto Zehnder partners with CEOs and founders of scaling organisations on the structural architecture underneath recurring organisational problems. This is the fifth in a series on seven patterns from the field.

Most organisations skip the expense. They move fast, leave things implicit, and trust that people will figure it out. Usually they do. For a while.

What fills the gap is not chaos. It is something quieter and more durable: assumption. Each person in the system develops their own working model of what has been decided, what is permitted, what the priorities are, and what will happen if they step outside those lines. These models are rarely identical. They are rarely tested. And they are almost never visible to anyone else.

This is Structural Silence. Not the silence of conflict avoided, or of things unsaid in a meeting. The silence of clarity that was never produced in the first place, and the assumptions that quietly organised themselves in its place.

It shows up in specific ways. Two functions operating from different understandings of who owns a decision, neither aware the gap exists. A team executing against a priority that was superseded three months ago but never formally updated. A new senior hire building a strategy on an assumption about the company’s direction that the founders privately revised, but never communicated. A process that everyone follows, that no one designed, that no one can explain the origin of.

The organisation does not experience this as silence. It experiences it as misalignment, confusion, politics, and friction. The symptoms are interpersonal. The cause is structural.

What makes Structural Silence particularly hard to address is that it is invisible by design. The gaps are not marked. Nobody flags what hasn’t been said. The assumptions feel, to the people holding them, like facts.

When that doesn’t happen, the organisation fills in the gaps itself. And what it fills them with is rarely what leadership intended.

Myrto Zehnder partners with CEOs and founders of scaling organisations on the structural architecture underneath recurring organisational problems. This is the fourth in a series on seven patterns from the field.

It belongs to the person who is accountable for an outcome but cannot control the conditions that produce it.

They own the result. They don’t own the decisions that determine it.

This is Authority Split. And it appears in almost every organisation that has grown faster than its structure has been designed to handle.

It looks like this: a head of product who is responsible for delivery timelines but has no authority over resourcing decisions. A country manager who is accountable for revenue but cannot approve the hires she needs. A COO who owns operational performance but cannot move budget across functions without running it upward first. A team lead who is expected to develop people but has no say in their compensation.

The gap is rarely announced. It accumulates. And what follows is predictable. The person in the split role compensates. They escalate decisions they should be able to make themselves. They wait for alignment that never quite arrives. They work around the gap informally, building influence to get done what they have no structural permission to do. Or they stop trying, and the accountability becomes nominal.

The organisation interprets all of this as a performance problem. The person isn’t decisive enough. Doesn’t have enough presence. Isn’t senior enough for the role.

The role was designed to fail. The person was placed inside it.

The person is visible. The architecture isn’t.

Myrto Zehnder partners with CEOs and founders of scaling organisations on the structural architecture underneath recurring organisational problems. This is the third in a series on seven patterns from the field.

When something goes wrong in a scaling organisation, the explanation usually arrives quickly.

It’s the head of sales. The VP who can’t manage upward. The team that doesn’t communicate. The founder who micromanages. The senior hire who never quite integrated.

The explanation feels right because it’s specific. There’s a person attached to it. The person is visible. The problem, once named as theirs, feels solvable: coach them, replace them, restructure around them.

So that’s what happens.

And then, some months later, the same type of problem appears. Different person. Same shape.

This is the pattern I see most consistently in scaling organisations, and it is the most expensive one to maintain. Not because people are never the issue. Sometimes they are. But far more often, the person being identified as the problem is responding rationally to a system that is producing irrational pressure.

The head of sales is hoarding information because two other functions have authority over her pipeline and she has learned that transparency costs her. The VP who can’t manage upward is navigating a reporting line that was never structurally resolved. The team that doesn’t communicate is working across an accountability gap that no one has formally addressed. The founder who micromanages is doing so because the organisation has no reliable mechanism for decisions to hold without them.

The person is visible. The architecture isn’t.

When a structural problem is attributed to an individual, the organisation gets a temporary sense of resolution and a permanent continuation of the condition. The condition keeps generating the same pressure. The next person in that role, or that function, or that layer of the hierarchy, responds to it the same way. And the explanation arrives again, just as quickly, just as specific, just as confidently attached to a name.

The People Illusion isn’t a failure of intelligence. It’s a feature of how organisations naturally process complexity. People are legible. Structure is not. So the explanation that feels most true is almost never the structural one.

Until you learn to look there first.

Myrto Zehnder partners with CEOs and founders of scaling organisations on the structural architecture underneath recurring organisational problems. This is the second in a series on seven patterns from the field.

The Eagle’s Perspective — myrtozehnder.com

It changes shape. The industry changes. The team changes. The size of the company changes. But the shape of the problem stays roughly the same, and the CEO keeps working on it, and it keeps not resolving.

Most people explain this as bad luck. Or as something inevitable about growth. Or as a reflection of how complex organisations are.

I explain it differently.

The problem that keeps coming back is usually not the problem being worked on.

Not because the CEO is wrong about what they’re seeing. They’re right about what they’re seeing. The underperforming team, the decision that won’t stay decided, the initiative that keeps losing momentum, the person who keeps creating friction. All real. All worth addressing.

But those are the presenting questions. And underneath every presenting question is a different one. Quieter. Harder to name. Often pointing at something the organisation has been quietly organised around avoiding.

A product question that was actually about exit readiness.

A people question that was actually about decision process.

A performance question that was actually about where authority sat.

A communication problem that was actually about what couldn’t be said.

The presenting question is the door. The hidden question is what’s behind it.

Answering the door doesn’t change the room.

This is not a psychological insight. It’s a structural one. The hidden question isn’t buried in someone’s motives or unspoken in a team meeting. It’s visible in how the organisation is designed. In who has to ask permission for what. In which decisions travel up and which ones don’t. In where the accountability actually lands when something goes wrong.

The pattern I call The Hidden Question shows up when the question being actively worked on and the question the system is actually generating are two different questions. And the distance between them is where the structural problem lives.

Once you learn to look for the hidden question, you stop solving the wrong thing.

You also stop being surprised when it keeps coming back.

Myrto Zehnder partners with CEOs and founders of scaling organisations on the structural architecture underneath recurring organisational problems. This is the first in a series on seven patterns from the field.

The Eagle’s Perspective — myrtozehnder.com

She didn’t mean it as a decision. She meant it as a mood. A nudge. The kind of thing a CEO says between two other things, already half-thinking about the next call.

Three weeks later, the head of product had restructured the intake process, cut the customer success team out of the triage loop, and told them the change came “from Kim.”

It hadn’t. Not really. What Kim had said was one sentence, unscoped, unwritten, said once. What the head of product had heard was a mandate. And what customer success experienced was a decision made about their work, by someone who’d never spoken to them, that nobody could quite trace back to a moment where it was actually decided.

Kim found out about all of it in a Friday retro, three people deep into a conversation about whose call it had even been.

Nobody had lied. Nobody had overstepped, exactly. The head of product had filled a gap the only way anyone can: with their best guess at what the CEO probably meant, extended a little further than the sentence itself ever went.

This is the part that’s easy to miss. Structural silence doesn’t look like conflict. It doesn’t look like anyone hiding something or refusing to communicate. It looks like an ordinary Tuesday, a passing comment, and three weeks of a team quietly organizing around a decision that was never actually made — because nobody had been forced to write it down, scope it, or say out loud who it belonged to.

The tell isn’t in what was said. It’s in what happened next, and how many people had a different version of it by the time it surfaced.

A few places this shows up, if you’re looking for it in your own organization:

Two people, in two different meetings this week, each confidently describing the same decision — differently. Not disagreeing. Just each holding a version they’d quietly assembled themselves, because no shared version was ever put in front of them both.

A change that “came from” you, that you don’t remember deciding. Not because your memory is bad. Because it was never a decision in the first place. It was a comment, and someone downstream had to turn it into one.

A question that keeps getting asked in slightly different words, by slightly different people, months apart. Not because the answer is hard. Because it was never actually answered — just implied, once, to someone who’s since moved teams or moved on.

None of these are dramatic. That’s what makes them structural rather than personal. Nobody is the problem. The problem is what a system does with the space nobody has filled — it fills it anyway, with whatever each person’s best guess happens to be, and it does this quietly, continuously, whether or not anyone intended it to.

Kim’s team wasn’t wrong to act. They were doing what any team does when the top of the organization leaves something unscoped: they scoped it themselves, and hoped it matched.

Sometimes it does. That Friday, it hadn’t.

The head of product who keeps escalating decisions she should be making herself. The country manager who waits for sign-off before moving on anything real. The COO who runs every budget shift upward instead of just deciding.

The read is always personal. Not decisive enough. Not senior enough for the seat. Needs to grow into the role.

I think that read is wrong, more often than it’s right.

What’s actually happening in most of these cases isn’t a person failing to claim authority. It’s a person who was never structurally given it — carrying full accountability for an outcome, without the actual decision rights that would let them produce it on their own.

The head of product owns the delivery timeline. She doesn’t own the resourcing decisions that determine whether it’s achievable. The country manager owns the revenue number. He can’t approve the hires that would move it. The COO owns operational performance, and has to ask permission to move money across functions to affect it.

None of this was designed. It accumulated. A role expanded during a hiring push, and nobody revisited who could actually decide what. A function grew past the org chart that was drawn for a company half its size. The chart still says these people own their outcomes. The actual distribution of decision rights, quietly, moved somewhere else.

This is where the ownership diagnosis becomes seductive. It’s simpler to believe the person than the structure. It doesn’t require anyone to touch the org chart, revisit who reports to whom, or admit that a role was built to fail before anyone was placed inside it. “They need to own it more” costs nothing to say and nothing to fix. It just doesn’t fix anything either.

Watch what the senior hire actually does instead. They escalate decisions that look, on paper, like theirs to make. They build informal influence networks to get things done they have no formal permission to do. They wait for an alignment call that never quite happens, because nobody above them realises they’re waiting for one.

Eventually, one of two things happens. They leave, and the organisation reads it as attrition — a hire who “didn’t work out.” Or they stop trying to close the gap, and accountability becomes a title rather than a fact.

Either way, the organisation replaces them. Hires someone new into the same seat. Watches, a year later, as the pattern returns.

It isn’t the person. It was never the person. It’s the seat.

Continue reading

Mine arrived fast.

I had spent years studying two things that don’t usually go together. Computer science at ETH: systems, architecture, logical structure, the discipline of finding where things break. And elite sports coaching, trained by people who worked at the highest level: Simon Ammann’s mental coach, Jean-Pierre Egger, the national handball coach. People who understood, with precision, how structure shapes performance under pressure. How authority needs to sit somewhere clear. How a team either has the architecture to perform or it doesn’t. And no amount of motivation closes that gap.

Then I walked into organisations.

And found that almost nobody had considered any of this.

Not because they weren’t intelligent. Not because they didn’t care about their teams. But because nobody had told them this was a discipline. That it had been studied. That there were people who had spent careers understanding exactly how structure produces behaviour. And how behaviour that looks like a people problem is almost always a structural one.

The gap was wide enough to be almost absurd.

What I kept seeing as a team lead was the same pattern repeating. A person identified as the problem. A team addressed. A restructuring done. And then, quietly, the same issue reassembling itself somewhere else in the organisation. Because the architecture had never been touched.

As CEO and board member, I had the freedom to work differently. To reshape the structure so that issues were addressed at the level where they actually lived, and not managed at the surface and left to return.

The computer science training gave me something useful here: I find logical flaws instinctively. Not as a criticism, as a signal. When something keeps breaking in the same place, that’s not a coincidence. That’s the system telling you something about its own design.

The sports coaching training gave me the other half. I understand what people need to perform inside a structure, and what happens when the structure asks too much of the wrong role, or puts accountability somewhere authority never landed. I’ve watched good people leave bad structures. The leaving was always a signal. The structure had been wrong for longer than anyone had admitted.

That combination is unusual. Most people who work on organisations have one side or the other. The systems thinker who sees the architecture but not the people inside it. Or the people person who understands teams but can’t read the structural layer underneath.

I ended up with both. Which means I can see what’s broken, and understand exactly what it costs the people living inside it.

That’s what The Eagle’s Perspective is built on. I work with CEOs and founders of scaling organisations to redesign the structural architecture that limits their freedom to lead. Not coaching. Not culture work. Not a new org chart. The architecture, where decisions actually live, how authority is distributed, what the system is producing and why.

The question I keep coming back to is the one most organisations never quite ask.

Not who is causing the problem.

What is the system producing, and what would need to change for it to produce something different.

Continue reading

Myrto Zehnder partners with CEOs and founders of scaling organisations on the structural architecture underneath their most persistent problems.

The Eagle’s Perspective — myrtozehnder.com

Not at the beginning. Usually somewhere in the middle, once the presenting problem has been laid out. The team that isn’t performing, the initiative that keeps sliding, the decision that keeps returning to the top, the person who keeps causing friction.

The question is quiet. It often arrives as a sigh more than a sentence.

Why does this keep happening?

I’ve spent years working with CEOs and founders of scaling organisations on the structural layer underneath that question. Not the people. Not the culture. Not the strategy. The architecture. How authority is distributed, how decisions route, where accountability lands, how information moves through the system when nobody is watching.

What I’ve found is that the same conditions keep producing the same outcomes. Not because the same people are making the same mistakes. Because the same structures are generating the same pressures. And people, being rational, keep responding to them in the same way.

Seven patterns appear more consistently than anything else. They don’t arrive in isolation. They overlap, reinforce each other, and accumulate. But each one has a distinct shape, and once you’ve seen it, you can’t unsee it.

The first thing most CEOs notice is a person. Someone isn’t performing. A team is slow. Someone keeps pushing back. The diagnosis arrives quickly: it’s a people problem. It usually isn’t. The person identified as the problem is almost always behaving rationally, responding to what the architecture puts them in a position to do, absorb, or avoid. The system produced the behaviour. The person made it visible.

What’s harder to notice is when nothing signals the problem at all. Authority drifts upward without anyone deciding that’s where it belongs. Dependency forms without being declared. Freedom erodes not in one moment but in a hundred small ones, each of which felt like the right call. By the time the weight becomes visible, the calendar full of things that shouldn’t require the CEO, the team that stopped bringing initiatives, it’s been building for years. The silence wasn’t empty. It was accumulating.

Underneath the silence, there is almost always a split. Someone is accountable for an outcome they don’t control. Someone else controls outcomes they’re not accountable for. The org chart suggests alignment. The actual distribution of authority tells a different story. The decision that keeps coming back isn’t a failure of the person it was delegated to. It’s a signal that authority and accountability were never in the same place.

When these conditions persist long enough, something else happens. The same issue starts appearing in different people, different teams, different moments, slightly different shape, same place in the organisation. Each intervention felt complete. The conversation happened, the restructuring was done, the culture work was valuable. But the architecture was never touched. So the system found the next person, put them in the same position, and produced the same result. The problem didn’t return because of who was in the role. It returned because the conditions that produced it were still intact.

All of this runs at a cost that never appears in any report. Not the visible cost. The friction, the delay, the conflict. Those are the smallest part. What accumulates underneath is the strategic initiative that keeps getting displaced, the senior person carrying more than the architecture should ask of them, the talented person who quietly disengaged months before anyone noticed. The structural tax keeps running. Invisibly. Continuously. Long before anyone calculates what it’s actually worth.

And when organisations finally decide to act, the intervention often fails, not because it was wrong, but because the sequence was wrong. The reorganisation changed the diagram. The authority stayed where it was. The new structure existed on paper while the old system continued in practice. Correct answer, wrong timing. Which used the window and closed it. The next time someone proposes the same direction, the answer is already there: ‘we tried that.’

Underneath all of this, in every case, there is a question behind the question. The presenting problem is real, it deserves attention, it brought us to the conversation. But answering it directly leaves the structural question untouched. A product decision that was about exit readiness. A people problem that was about decision process. A compliance failure that was about meaning. The presenting question points at a symptom. The hidden one points at the system.

Seven patterns. One underlying dynamic.

The People Illusion: the problem looks like a person. It’s the architecture that made their behaviour rational.

Structural Silence: nothing signals the drift. Authority erodes through reasonable moments, quietly, until it’s already structural.

Authority Split: accountability landed with one person. Authority stayed with another. Nobody designed it. It accumulated.

Structural Recurrence: the intervention worked. The architecture wasn’t touched. The system reproduced the same outcome with the next person.

Structural Tax: the visible cost is always the smallest part. What accumulates underneath never appears in any report.

Sequence Failure: the answer wasn’t wrong. The timing was. It used the window and closed it.

The Hidden Question: the presenting question is real. Underneath it, a different one is waiting. Pointing at a different level, requiring a different kind of attention.

These patterns don’t require a broken organisation to appear. They appear in functioning ones: organisations that are growing, hiring well, hitting their numbers. The problem isn’t visible in the daily operations. It’s visible in what keeps not happening: the strategic work that keeps getting displaced, the CEO who keeps finding themselves in rooms they shouldn’t need to be in, the question that keeps coming back in slightly different form.

The shift that matters isn’t urgency to act. It’s the ability to see.

Once the architecture becomes visible, the question changes.

Not why does this keep happening, but what is the system producing, and why.

That’s where the work actually lives.

Continue reading

Myrto Zehnder partners with CEOs and founders of scaling organisations on the structural architecture underneath their most persistent problems.
The Eagle’s Perspective — myrtozehnder.com

7 Patterns - Further reading