PM DEPOT

Back to Stakeholder Management
BUREAU
OF S·H
Bureau of Stakeholder Hazards  ·  A Field Dispatch Dispatch N° IV
Hazard Class · Sponsor Ghosting

Your Executive Sponsor Has Stopped Replying

Eight days. Two unread messages. One increasingly concerned product manager. A guide to diagnosing, rescuing, or respectfully burying the project your champion has gone quiet on.

· · · · ·

There was a time, not very long ago, when your executive sponsor was thrilled about the project. They opened the all-hands with a slide about it. They replied to your updates within an hour, using exclamation points. They introduced you at the leadership offsite as “the person behind the thing.”

Now your last two Slack messages are seen. A meeting was moved. The follow-up email has no reply. The all-hands slide has been replaced by a different all-hands slide, featuring a different project, run by a different person. You are, in the technical sense of the word, being ghosted.

This is the fourth hazard. Sponsor ghosting is rarely personal and almost never means what it feels like it means. But the instinct it triggers in new PMs — try harder, follow up more, make yourself visible — is exactly backwards. Before you act, you need to know which species of ghosting you're dealing with, because they require different responses.

Why Sponsors Go Quiet

The Capacity Ghost

Your sponsor is just overwhelmed. Their calendar has twelve meetings a day, their Slack has 400 unreads, and your project — which is important but not on fire — has quietly dropped below the daily triage line. This is the least malicious and most common version. Response: change what you send them, not how often.

The Priority Ghost

The strategic context has shifted. A board meeting, a competitor, a layoff, a new exec — something upstream has moved your project from “important” to “not the most important.” Your sponsor still likes you. They don't want to tell you the project lost its priority, because telling you feels like withdrawing support, and it's easier to go quiet. Response: make it safe for them to reset priorities without losing face.

The Political Ghost

Your project has become inconvenient in a way that's hard to explain to you. Another exec has pushed back, a commitment has shifted, the sponsor is in a fight they don't want to pull you into. This is rarer than new PMs think, but when it happens, silence is information. Response: find out what's actually changed through a lateral channel before you resurface.

The Mood Ghost

Your sponsor is having a bad quarter. It has nothing to do with you. They are not ghosting you personally; they are ghosting life. Response: reduce your footprint, wait two weeks, try again.

The Diagnostic

Four questions, in order. Answer them honestly before you decide what to do.

  1. Has their calendar pattern changed in general, or specifically around you? Ask a mutual contact. “General” is capacity. “Specific to you” is something worse.
  2. What was the last thing you sent them? Was it an update, or was it an ask? People ghost asks. They rarely ghost good news.
  3. Has your project moved in the org chart recently? Roadmap changes, reorgs, renamed initiatives — priority ghosting loves to hide behind these.
  4. Have you seen their calendar around other VPs' projects change at the same time? If multiple sponsors are going quiet, something upstream has shifted and you are one of the downstream victims.
Contrarian note The tempting move is to escalate: more pings, more updates, a formal request for a 1:1. Resist. A ghosting sponsor is usually a sponsor trying to signal “I don't have capacity for this right now.” The right response is to require less of them, not more. You want to become cheap to support, not expensive.

The Fix — Four Moves

1. Change the update format

If your weekly update is three paragraphs long, it's already too long. Cut it to three lines: what shipped, what's next, what I need from you. What I need from you should say “nothing” most weeks. Sponsors re-engage with updates that don't require them to do anything. They disengage from updates that ask for decisions in line 8.

2. Route through the chief of staff

If your sponsor has a chief of staff, executive assistant, or deputy — that person is your new best friend. Don't use them to push messages through. Use them to get a read. “Is this a bad week for me to surface a decision, or should I wait?” You will get more information from that one question than from three increasingly worried follow-ups to the sponsor themselves.

3. Acquire a second sponsor, quietly

If the project matters enough to exist, it matters enough to not depend on a single human's attention span. Identify one more senior person who benefits from your project succeeding and loop them in with small, useful updates. You are not replacing the sponsor. You are building a backup generator so that when the power flickers you don't lose everything.

4. Offer them an exit

Counterintuitive, but often the move that gets the relationship back. In your next message, give them an easy path to step back from a commitment they may be regretting. “Hey — I know things have shifted. If you'd rather de-prioritise this for the quarter, I'd rather know now than find out in Q3. Totally fine either way.” Nine times out of ten, the sponsor comes back — partly because you've removed the guilt of the unanswered message, partly because the offer itself is unusual enough to remind them why they backed you in the first place.

Phrases That Work

Short one for your inbox: we shipped X, next up is Y, nothing blocked on you. Happy to pause or reshape if priorities have moved — let me know what's most useful.
I'm sensing this is a lower-priority quarter for this project. No judgment — would rather know than keep pushing. What's the right thing for me to be doing instead?
Quick check with you: is there context I'm missing? Happy to pivot, pause, or keep going — want to make sure I'm not spending capacity on something that's already been reprioritised.

When to Let It Die

Sometimes the kindest thing you can do for a ghosted project is bury it with dignity. A project without a sponsor is not a project; it is overhead. If your diagnostic says the priority has shifted and the sponsor won't say so out loud, you can save both of you a quarter of quiet suffering by saying it for them. Write the postmortem. Move the team. Take the lesson. You will not be punished for killing a project that has already lost its champion; you will be thanked quietly by at least two people you didn't expect.

Working rule: a sponsor's silence is a signal, not a gap. Your job is to read the signal correctly. Most new PMs fill silence with effort. Experienced ones fill it with diagnosis.

← Back to Stakeholder Management