The Sponsor Dependency | Fragile Strategy in Large Organisations

How Decisions Get Made and How Long They Last

Large organisations do not wake up one morning and decide to pursue a strategy. Someone decides. And that someone is almost always brought in, elevated, or empowered specifically to solve a problem that shareholders have identified as urgent.

The sequence is familiar. A gap surfaces. Competitive pressure, regulatory obligation, a market opportunity with a visible window. Shareholders or the board translate that gap into a mandate. A leader arrives, or an existing leader is handed the brief, with the implicit contract that they will resolve it. The strategy that follows is theirs. They shaped it, they believe in it, and they carry the organisational weight needed to resource it, protect it, and push it through the natural resistance that any significant change encounters.

The governance process then does something that looks like institutional commitment. Investment cases get approved. Steering committees get formed. Programme boards convene. The language shifts from proposal to programme. To anyone observing, the organisation has made a decision.

What has actually happened is that one person, with enough positional authority and shareholder backing, has made a decision. The institution has provided the scaffolding. The conviction belongs to the individual.

This distinction matters because it determines how long the strategy lasts.

The typical arc runs three to five years. In the first year the strategy is being built, resourced, and defended. Teams form around it. Partners get selected. The early technical and organisational foundations get laid. In years two and three the work is deepest. Teams are fully invested. Delivery is happening. The strategy is beginning to demonstrate value in pockets of the business. Critical business processes start to form around it. Operational workflows get built on the technology the strategy produced. The platform, the architecture, the tooling, it starts to become load-bearing. This is the peak. The work is real, the belief is genuine, the sponsor is still present, and the strategy has begun to anchor itself into how the organisation actually runs.

Then shareholder priorities shift. A different problem has surfaced. A new gap, a new pressure, a new opportunity with a more immediate window. The strategy that was urgent three years ago is now background. And the sponsor, whose mandate was always tied to the problem shareholders originally asked them to solve, follows that shift. They move to a different role, a different organisation, or simply reach the natural end of their relevance to the new agenda. The departure is a consequence, not a cause. The cause is that the shareholder attention that created the original mandate has moved on.

What happens next is not dramatic. There is rarely a decision to stop. There is simply a gradual withdrawal of the conditions that made the strategy possible. The sponsor is no longer in the room. The replacement either brings a different view of the problem or lacks the appetite to inherit someone else’s direction. The steering committee still meets but the energy has changed. The investment case that was approved is quietly not renewed at the same level.

By year four or five, the strategy is running on momentum rather than conviction. And momentum, without the sponsor who generated it, is a diminishing asset.

What Gets Invested and What Gets Lost

When a strategy lands with genuine conviction behind it, the organisation responds in kind. Not just structurally but humanly.

Teams form with a sense of purpose. The work has a direction that feels worth moving toward. Engineers make technical decisions with the confidence that the platform they are building will matter. Delivery leads push through the friction of large programme execution because the destination justifies it. Architects design for the future state, not just the immediate need. The emotional contract between the people doing the work and the work itself is real. There is accomplishment in it. There is satisfaction in building something that is going somewhere.

This investment runs deeper than engagement survey language captures. Physically, people give the work more than the job description asks for. Mentally, they develop capabilities specifically oriented around the strategy. They learn the domain, the technology, the organisational context. They become genuinely expert in something that only exists because the strategy exists. Emotionally, they attach. The work becomes part of how they understand their own professional worth.

That investment is what makes the moment of sponsor departure so consequential. And it rarely announces itself clearly.

The first visible signal is not a restructure or a strategy review. It is movement at the top. The senior leadership who carried the mandate start transitioning to other roles. Some move within the organisation, following the new shareholder priority to wherever it has landed. Some leave altogether. The leadership below them, the people who translated strategic intent into programme reality, follow the same pattern. Some move on. Some are replaced.

And this is where the human cost begins to compound. The people who step into those vacated leadership roles are not, in most cases, carrying the same conviction. They are making a career move. The role is a step up. But the emotional and intellectual investment in the strategy, the years of context, the belief in where the work was going, that does not transfer with the title. What arrives in its place is management. Competent in many cases. But management of something rather than belief in something. The distinction is felt immediately by the people beneath them, even when it is never named.

Then the broader movement begins. Engineers, delivery leads, testers, architects. The people who built their professional identity around the work start to leave. Not all at once. But steadily. Because the feeling that made the work worth doing, the sense of accomplishment, of building something real, of being part of something with a direction, has been replaced by something that has no clean name but is recognisable to anyone who has felt it. A low-level anxiety about what comes next. A sense that the ground has shifted without anyone saying so officially.

Some stay. As explored in an earlier edition, the gravity of what has been built, the comfort of the familiar, the inertia of a career embedded in a particular context, keeps people in place even when the conviction is gone. But staying and being invested are not the same thing.

What remains is a team managing something rather than building something. New leadership without the history. Remaining staff without the emotional resonance that once made the daily friction worthwhile. And a technology platform that critical business processes are running on, that cannot easily be removed, but that nobody with budget authority is genuinely committed to developing further.

The two examples that sit in my experience are different in their detail but identical in their pattern. In one, a domain-driven strategy to replace multiple vendor platforms with a purpose-built cloud-native architecture ran RFPs, selected partners, built the technical foundations, and got close to delivery before the sponsor change came. Senior management, with different priorities and a different view of what the function was worth investing in, replaced the build strategy with a buy strategy. The work, the partners, the technical direction, the team that had built expertise around it, all of it unwound. In the other, a strategic platform built for the future was delivered. The architecture was sound. The platform worked. Then the sponsors moved on. Their replacements did not inherit the conviction. Investment slowed, then stopped. Within a few years the platform that was designed as a foundation for future growth became the subject of discussions about whether to migrate away from it entirely.

In both cases the technology did not fail. The sponsorship did. And the people who had invested in it felt that distinction acutely, even when the organisation never acknowledged it directly.

What is left behind in both cases is the same. A platform that the business depends on enough that removing it is expensive and risky, but that nobody is investing in enough to develop. Resource constraints start to emerge. The criteria for building on the strategy shift. Decisions that would once have been made on genuine technology value get made on organisational politics and short-term budget logic instead. The strategy is in survival mode. And survival mode, sustained long enough, is just a slower way of accruing technical debt.

The Ecosystem This Produces

This is not a story about poor planning. It is not a failure of governance or a shortage of good intentions. What the pattern described in this edition represents is the corporate technology ecosystem working exactly as it is oriented.

The strategies that get funded are the ones that address what shareholders have identified as urgent. The leaders who get the mandate are the ones brought in to resolve that urgency. The conviction that drives the work is theirs, not the institution’s. And when shareholder attention moves, as it always does, the mandate moves with it. The sponsor follows. The strategy is left behind.

What shareholders see as value at any given moment is a proxy for genuine business value. Not a replacement for it. A proxy. The two are related but they are not the same thing. Genuine business value accrues over time, through sustained investment in the right foundations, through strategies that are given long enough to embed not just to survive but to thrive. Shareholder perception operates on a shorter cycle. It responds to narrative, to visible momentum, to the problem that is most legible in the current quarter. When those two things align, as they do in the early years of a well-sponsored strategy, the results can be significant. When they diverge, which is inevitable, the strategy does not get a clean ending. It gets stranded.

The technology estate that large organisations carry today is in large part the accumulated residue of that divergence, repeated across decades. Platforms that were strategies. Investments that were convictions. Work that people gave years of their professional lives to, that now sits in the estate neither fully alive nor formally dead, consuming resource, resisting change, and quietly making every future decision more complicated than it needed to be.

The cleanup that would resolve this never quite arrives. Not because organisations do not recognise the problem. Because the same logic that produced the bloat governs the decision about whether to address it. Streamlining a technology estate does not satisfy shareholders looking for growth. Decommissioning platforms that are technically debt but operationally load-bearing requires capital that has to come from somewhere. The financial case for doing it properly competes with the financial case for the next strategy, the next mandate, the next problem that shareholders have identified as urgent.

The clearest counterexample in recent corporate history is Apple. The deliberate decision to cannibalise its own successful products before the market forced it to. The iPod into the iPhone. The product that was generating revenue, actively killed in favour of what came next. It is held up as visionary and it was. But it is worth being precise about what made it possible. It required a sponsor with unusual longevity, unusual institutional authority, and the personal conviction to override the rational short-term argument for protecting what already worked. It was not a process. It was a person. Which means even the exception does not escape the dependency this edition describes. It just had a sponsor who lasted long enough and believed deeply enough to break the cycle deliberately.

Most organisations do not have that. What they have is the cycle. Strategy born from shareholder urgency, carried by a person, partially embedded, stranded when the urgency moves on, surviving as debt, adding to the bloat, waiting for a cleanup that the same logic will continue to defer.