You have been waiting nine days for your sponsor to approve which way to go. You have chased twice. The only reply was a thumbs-up on an unrelated thread. The plan says this decision was due last week. Nobody has said yes. Nobody has said no. And the build team is now sitting on their hands, waiting for a direction that is not coming.
You keep telling yourself the project is just waiting on the sponsor. It is not waiting. A decision is being made right now, by default, and it is the worst one on the table: keep drifting. When this goes sideways, the question will not be why the sponsor went quiet. It will be why you let the project stall.
The Shift
Silence feels neutral. It is not. Every day the sponsor does not answer, a default is quietly running: the status quo, the safe option, the do-nothing path. That default is a decision. The only difference is that nobody chose it on purpose, and you are the one who will answer for where it leads.
When a sponsor goes quiet on a hard call, it is rarely because they stopped caring. It is because the decision is uncomfortable, the tradeoffs are ugly, or they are waiting for someone to make it easy to say yes. Silence is what an unforced decision looks like from the outside.
So stop treating the sponsor's inbox as the thing you are waiting on. Your job is not to wait for the decision. Your job is to force it. Not by chasing harder, but by changing what silence costs.
The System
A chase email asks “any update on this?” and invites more silence. A decision-forcing note does the opposite. It takes away the option to say nothing. It has three parts.
A clear recommendation. Not a menu of options with a shrug attached. You say what you would do and why, in a sentence or two. You are the person closest to the work, so you have a view. Use it.
A deadline. A specific date and time you need a reply by. Not “when you get a chance.” Something like “by Thursday 2 pm.”
The default action. This is the line that does the work: what will happen if no one replies by the deadline. “If I do not hear back by Thursday 2 pm, I will proceed with option A and treat it as approved.”
That last line changes the physics of the whole thing. It turns silence from a way to avoid the decision into a way to make it. Not replying is no longer a delay. It is an active choice to let you proceed.
A sponsor who was quietly avoiding a hard call will usually engage the moment doing nothing has a visible consequence. And in the rare case they still say nothing, you have a defensible path forward and a written record that you forced the clarity the project needed.
One caution. The default you name has to be one you can actually own and stand behind. Do not write a default you would be uncomfortable executing. This is not a bluff to smoke out a reply. It is the real path you are prepared to take, which is exactly why it works.
The Asset
The asset for this issue is the Decision Request one-pager.
It is a fill-in template for the note above. One page, with fields for the decision, your recommendation, the options you weighed, the deadline, the default that runs if no one replies, and what stays blocked while this sits open. It is built to be faster to send than another round of chasing. Fill it in, send it, and let the deadline do the rest.
You’ll find the filter button in The Move section below.
The AI Assist
One practical workflow here: stalled email thread to decision-forcing note. Use it when a decision has been sitting open across a long thread and you want a clean first draft in front of the decision-maker fast.
Use this prompt:
You are helping me force a stalled decision. Below is an email thread where a decision has been sitting open with no answer.
Draft a short note I can send to the decision-maker. It must contain exactly three things:
(1) a clear recommendation stated as my view, with one line of why;
(2) a placeholder for a specific reply deadline I will fill in;
(3) a default action, meaning what I will proceed with if I do not hear back by that deadline.
Keep it under 120 words. Plain and calm, not passive-aggressive. Do not offer more than two options. Do not end on a question.
Thread: [paste the thread here]
AI can draft the note. You still own the recommendation and the default, because you are the one who has to stand behind both.
The Move
Pick one decision that has been sitting open for more than a week. Today, send a decision-forcing note on it: a recommendation, a deadline, and a default that runs if no one replies. You will stop being the person waiting on the sponsor and become the person moving the project.
Reply prompt: What is one decision sitting in silence on your project right now, and what is the default quietly running while it waits?
P.S. New here? The free Execution Signal Starter Pack is here.