A few years ago I was advising a client's board on an innovation hub, a space originally conceived for community building and open collaboration. The strategic intent was clear: the hub's value depended on its openness, on the kind of interaction that only happens when a space genuinely belongs to a community. Everyone at board level understood this. Most of my contact was through the project manager, which matters for what happened next.
The project manager responsible for day-to-day execution was capable, thoughtful, and acting in good faith. But she reported upward through a chain that never attended working-level meetings. Each report distilled, simplified, reframed. Over months, she began making interpretive choices about what to emphasise, what to leave out, how to frame progress in terms the board would find useful. None of those choices were wrong on their own. But they accumulated. The hub was drifting toward becoming a private client lounge, a premium, access-controlled space that would have been profitable in the short term but would have destroyed the entire strategic premise.
Nobody decided to change direction. The direction changed anyway.
I remember sitting in a review meeting where the board finally saw what had happened. The reaction was not anger. It was confusion. Nobody could point to a moment where someone had overstepped. There was no moment. The decision had migrated, piece by piece, from the people who held the strategic vision to the person closest to the daily work. And I had been somewhere in the middle of that chain, advising through the very reporting structure that allowed it to happen, without noticing either.
Delegation that does not announce itself
When leaders talk about delegation, they usually mean the deliberate kind. You assign a decision to someone, define its boundaries, hold them accountable. There is clarity about who is deciding and where their authority ends. That is the version of delegation people think they are practising.
The problem is the other kind. There is a form of delegation that never announces itself, and it happens through the ordinary mechanics of how information moves through an organisation. The person who distils and summarises for the decision-maker is, in effect, pre-deciding. They introduce their own assumptions (not maliciously, but inevitably), strip context that may have been essential, and make judgements about what matters. Summarising is itself a form of decision-making, although it is almost never recognised as such.
I should be honest: the innovation hub was not the only time I have been part of this. In advisory work, it is tempting to absorb part of a client's decision without realising it, quietly shaping what reaches them because you think you are being helpful. The instinct to add value is, ironically, one of the forces that makes this worse. You start carrying a piece of someone else's decision and it feels like good service. It is not. It is a transfer of ownership that nobody agreed to.
How it accumulates
Any single instance is manageable. A simplified report here, a pre-filtered dashboard there. Each one feels minor. In isolation, it probably is.
But let them pile up over weeks and months, and something shifts. A team member picks up the slack for a time-poor executive. A dashboard pre-selects which metrics appear first. A report omits context that seemed tangential but was not. A middle manager, wanting to show initiative, resolves an ambiguity rather than escalating it. None of these feel like a transfer of authority. Each is a reasonable response to the pressures of organisational life. Yet an important decision has been made, gradually, collectively, without a single identifiable moment of handover.
There is a Japanese concept, nemawashi, the practice of building consensus quietly before a formal decision is taken. In well-functioning organisations, nemawashi is a strength. But there is a shadow version of it where consensus is built not deliberately but accidentally, where alignment happens through drift rather than intent. The formal decision-maker signs off on something that has already been decided by the time it reaches them. They just do not know it.
What makes this hard to detect is that the organisation's own culture often reinforces it. In environments where boards are not expected to operate at the project level (which is a design choice, not a failure), the gap between strategic intent and operational execution widens naturally. In cultures where initiative is rewarded, people step into decision-making roles not because they are overreaching but because they believe they are doing what is expected. The empowerment is real, although the clarity of ownership often is not.
Technology adds another layer. When an executive relies on an AI-driven model to inform a decision, the reasoning behind the output is rarely transparent. You cannot see the logic even if you want to. If you do not know what shaped the output, you have already delegated, whether you recognise it or not. The pattern is the same as with human intermediaries. Something else has absorbed part of the decision before it reaches you.
What orphaned decisions do
When a decision loses its owner, two things tend to happen together. The ambition shrinks. No one feels authorised to pursue bold outcomes, because no one fully owns the direction. People become cautious not because the risk is too high but because the ownership is too diffuse. And then the risk appetite collapses to match the reduced ambition. The organisation does not just lose control of a specific decision. It loses the conviction that decision was supposed to serve.
I have seen this most clearly in innovation work. A company invests in an initiative, assigns resources, builds a narrative around it, and then the decision-making gradually disperses across committees, intermediaries, and processes. The initiative does not fail dramatically. It just becomes smaller, less ambitious, less differentiated. The original boldness was tied to the original owner's conviction, and when ownership drifted, the conviction went with it. Honestly, it is one of the most frustrating things to watch, because from the outside you can see it happening and the people inside cannot.
There is an external dimension too. Customers, partners, and investors can tell when a decision is not truly owned. It comes through in how the story is told, how questions are fielded, how commitments are made. If the people you are trying to reach do not believe the story because it does not sound owned, the project is already in trouble, regardless of how good the underlying idea is.
What might help
The first useful thing is also the simplest. Name the pattern when it is happening. Most organisations have never had a conversation about where decision ownership actually sits versus where it is assumed to sit. That gap, once named, becomes workable.
A practical principle follows: no decision should go without an owner, whether singular or collective. This does not mean every decision needs a single heroic decision-maker. It means someone, a person or a clearly defined group, should be able to say, “This is ours. We own the reasoning, the trade-offs, and the outcome.” If no one can say that, the decision is orphaned.
I should add a qualification, because the reality is not always clean. There are organisations where the delegated state is working well enough. The team has absorbed the decision-making, the outcomes are acceptable, and the senior leader's absence from the process has not caused visible harm. In those cases, the task is not to reclaim ownership. It may be to acknowledge the arrangement consciously, add safeguards, and make sure that what is happening by drift could withstand scrutiny if examined deliberately. The problem is not delegation itself. It is not knowing it is happening.
The question worth asking
The executive who says “I make the final call” is not wrong, exactly. They do sign off. They review the recommendation, weigh the options presented, and approve a course of action. But signing off on a decision that has already been shaped, filtered, and narrowed by hands you may not be aware of, that is a different act than deciding. It looks the same from the outside.
The question is not whether you are delegating. It is whether you know you are. And if you have never asked that question inside your own organisation, it might be worth starting there.
