What to do about unresponsive stakeholders
When your sponsor or another stakeholder goes quiet, send one short message that restates the single decision you need, the options, your recommendation, the date, and what happens to the timeline if it passes. If that gets no answer in two or three working days, try a different channel or the second contact you agreed at kickoff, and record the delay and its effect on the date in writing. Keep working on everything that doesn’t depend on them, and don’t let the silence quietly move your deadline.
By the Unblockd team · Updated · 5 min read
On this page
Why sponsors go quiet
Silence feels personal, but it usually has an ordinary cause, whether the sponsor is an executive in your own organization or a client paying for the work. Knowing which cause you’re facing changes what you send next.
- They’re busy, and your request needs more effort than they have this week.
- The request wasn’t clear, so they’re waiting until they can think about it properly.
- They don’t have the authority, and are waiting on someone above them.
- People on their side disagree, and replying would mean taking a side.
- They have bad news, such as a budget cut or a change of priority, and haven’t worked out how to say it.
- The project has slipped down their list, and nobody told you.
Seven steps to get the project moving again
- Check that it’s really silenceConfirm the message reached the right person, that they aren’t on leave, and that it asked a question rather than only sharing information. A surprising amount of sponsor silence is a message that never asked for anything.
- Make the next message easy to answerRestate the one decision you need, with two or three options, your recommendation, and the date. Leave out the history. They should be able to answer from a phone without opening anything else.
- Put the cost of waiting in their termsSay what moves if the date passes: the launch, the training week, the campaign. Facts about the timeline are easier to act on than a reminder that you’re waiting.
- Change the channel before you raise the volumeIf email hasn’t worked, try a short call, a message in the chat tool they use, or their assistant. A third email in the same thread usually gets the same result as the first two.
- Go to the second contact, openlyIf you agreed a backup approver, ask them, and copy the original contact so nothing happens behind anyone’s back. Frame it as keeping their date safe.
- Keep the rest of the work movingRe-plan around the gap so the team works on whatever doesn’t depend on the answer. For small, reversible choices, you can say what you’ll do and when: “We’ll go with option A on Thursday unless you tell us otherwise.” Never do this for anything costly to undo.
- Record the delay and its effectWrite down when you asked, each follow-up, and how the date has moved as a result. Share it in the next status update. A dated record keeps the conversation about the timeline factual when it comes up later.
A follow-up message that works
Short, specific, and complete, so it works even if it’s the only message they read this week.
Subject: One decision for the support rollout, needed by Thu
Which support vendor should we go with?
A. Provider A, live in 3 weeks (we recommend this)
B. Provider B, adds 2 weeks of setup
If we don’t hear by Thursday, the Nov 7 launch moves a day for each day after.
Reply with A or B, or call me if it’s easier to talk it through.
When and how to escalate
Escalate when the agreed response window has passed and a different channel hasn’t worked, or sooner if the cost of waiting is high. Go to the person who can decide in their place: the backup approver you agreed, the chair of the steering group, or whoever the sponsor reports to on this project. Copy the sponsor, and bring the same short request, the dates you asked, and the effect on the timeline. Keep the tone neutral. The aim is a decision, and the sponsor will still be backing your project next month.
If the silence lasts weeks and covers everything, treat it as a signal about the project itself. Ask the sponsor directly, ideally in a short call, whether priorities have changed, and offer a clear choice: pause formally, reduce scope, or set a new date together.
Preventing it on the next project
- Name a decision-maker and a backup for each type of decision at kickoff.
- Agree a response window and what happens on silence.
- Agree the follow-up rhythm up front, so reminders feel like process.
- Send a short weekly update, so a missing answer stands out early.
Doing this in Unblockd
Unblockd follows these steps for you. Each ask carries the options, the recommendation, the date, and the cost of waiting, and the sponsor can answer from the email without an account. Reminders go out on a schedule, a request for help can be handed to someone else by name, and an admin can let unanswered asks pass to the next decider automatically. See unblocking stalled projects.
Questions
- How many follow-ups before I escalate?
- Usually two: one a few days after asking and one before the deadline. After that, change the channel or go to the agreed backup contact.
- Should I stop work while I wait?
- Stop only the work that depends on the answer. Re-plan the rest so the team stays productive, and record how the wait affects the date.
- Can I go ahead with my recommended option?
- For small, reversible choices, yes, if you say in writing what you’ll do and when. For anything expensive to undo, wait for the decision or escalate.
- What if the sponsor has gone quiet on everything?
- Ask them directly whether the project’s priority has changed, and offer to pause, cut scope, or reset the date together.