The project is going well. Milestones are being met, the team is motivated, the results are solid. Then the news comes: your sponsor is leaving the company. Or is transferred. Or is promoted into a division that no longer has anything to do with your project. Suddenly, everything is on the brink.
Projects are only as stable as their support. If you rely on a single sponsor, you are building on sand.
Good work alone is not enough. A project needs political backing, budget security, and access to decisions. All of that often depends on one person. If that person leaves, even the best project can be put up for review overnight.
A project manager I advised in exactly this situation had built up a digitalization project over two years: secured the budget, assembled the team, achieved initial successes. Then his sponsor was poached by a competitor. The successor had different priorities, questioned the budget, and within three months the project was shut down. Two years of work—gone. Not because the project was bad, but because it depended on a single person.
A sponsor change is not an administrative formality. The new sponsor has their own priorities; your project was the predecessor’s idea. At best, they are neutral; at worst, they see it as competition for resources. They do not understand the history, do not know which hurdles were overcome, or what value the project delivers. They owe you nothing, have no emotional attachment, will not defend you when things get difficult. And opponents sense an opportunity: every project has skeptics and competitors who stayed quiet under the old sponsor and now see their chance.
| Risk factor | Impact |
|---|---|
| The new sponsor’s own agenda | Your project loses priority |
| Lack of contextual knowledge | The project’s value is underestimated |
| No emotional attachment | Less willingness to defend it |
| Opponents become active | Political headwinds increase |
Sponsor changes rarely come completely out of the blue. Career signals appear early: your sponsor talks about new opportunities, is pulled into company-wide initiatives, seems distracted, less engaged. Organizational signals are just as telling: restructurings, division mergers, new leaders brought in from outside. And political signals should alarm you: your sponsor is losing influence, their projects are being scrutinized more critically, they are excluded from key meetings.
Build informal sources of information. Maintain relationships with people who hear about changes early. Do not wait until you are officially informed. The best time to prepare for a sponsor change is before it happens. The second-best time is now.
The best protection against a sponsor change is a project that does not depend on a single person. That requires systematic work long before the change occurs.
One sponsor is good; three advocates are better. Identify additional leaders who benefit from the project’s success. Involve them, keep them informed, make them allies. For critical projects, a steering committee is the formal way to eliminate the “single point of failure”: the sponsor may chair it, but if they leave, the other members will carry the project.
At the same time, strengthen the business case. A project with a weak business case is vulnerable. Quantify the benefits, document successes, gather evidence. If someone asks, “Why are we doing this?”, the answer should be indisputable. Create visibility: a project nobody knows about is easy to cut. The more people know its value, the harder it is to end. Also check whether the project can be transitioned into a standard process. The less it is seen as a “special project,” the more stable it becomes.
A project that exists only because of the sponsor is not a sustainable project. Make it independent before you have to.
A division head I supported faced exactly this challenge: her sponsor was promoted, and the successor did not know the project. Instead of waiting, she requested a meeting within 48 hours. Instead of pitching, she listened first: What are your priorities? What problems do you want to solve? Then she positioned the project as a solution to one of his problems. And she offered him something surprising: an exit. “I understand if you want to reassess priorities. Let’s review together whether the project makes sense on your agenda.” That showed professionalism, and in the end he decided to continue.
As Peter Drucker aptly observed: the most important decision in organizations is not what gets done, but who has the power to decide it. A new sponsor is not only a risk; it is also an opportunity. Now is the moment to shed toxic legacy issues from the old sponsor, renegotiate unrealistic deadlines, or unlock frozen budgets. What was impossible under the old sponsor can suddenly become possible under the new one. Use this window—it closes quickly.
Sometimes the pitch does not work. The new sponsor has other plans, and your project does not fit. Then it is time to accept the new reality. Fighting a sponsor who does not want you is rarely successful. Consider alternatives: can the project continue under a different sponsor, in another division? Could a reduced scope be the спас? Sometimes a scaled-down project can grow again later.
If the project ends, ensure a professional close. Document everything, hand over knowledge, acknowledge the team’s work, and ensure smooth transitions for team members. What you should avoid: letting the project limp along in zombie mode, blaming the new sponsor, or leaving the team in the dark. Ending a project professionally is just as important as leading it professionally. Those who cling to sunk costs waste resources needed elsewhere.
Not every project survives a sponsor change. That is not a disgrace; it is reality. The question is what you learn from it for next time: was the project too dependent on a sponsor? Was the business case too weak? Was visibility too low?
First: how many advocates does your most important project have at the leadership level, besides your sponsor? If the answer is “none,” you have a structural problem.
Second: is your business case strong enough to convince someone who has no personal relationship with the project? Test it by presenting it to someone unfamiliar.
Third: could you deliver a compelling pitch for your project in one hour that works even without your current sponsor? If not, your project is more vulnerable than you think.
Project management is often treated as a technical discipline: milestones, budgets, resource plans. That is important, but it is not everything. The political dimension of projects is systematically underestimated. Anyone who believes good work speaks for itself will eventually be taught otherwise.
Your project needs more than a plan. It needs allies, visibility, and a sponsor—ideally more than one. Do not build on sand. Build on multiple foundations. Then your project will weather the storm when a sponsor leaves.
The right moment to stop – If the project does not survive the sponsor change, a clean close is better than a slow fade-out.
Leading upward – Winning over the new sponsor is a special case of “managing your boss.”
All Insights can be found in the overview.
Proven tools and models for self-application are available under Solutions.
If you want to take these thoughts further for your company, a no-obligation initial conversation is worthwhile.
