When an executive sponsor won't make a decision, find out why before you push harder. A stall usually has one of a few causes: the options are unclear, the decision carries personal or political risk, the sponsor lacks the authority, peers disagree, or the sponsor wants more evidence. Each cause needs its own fix. That might be a short decision memo with a recommendation and a cost of delay, a default that takes effect on a set date, a smaller first step that can be undone, a steering committee item agreed in advance, or an escalation the sponsor knows about. Keep a written record the whole time.
The problem is common enough to have a name. PMI describes "wafflers who disappear when pivotal decisions must be made" and cites its 2018 Pulse of the Profession, in which one in four organizations said inadequate sponsor support was the main cause of failed projects. The steps below assume the sponsor is your own executive on an internal program, and that you want the program moving again without damaging the relationship.
Why is my executive sponsor not deciding?
An executive sponsor who keeps deferring a decision usually has a reason they haven't said out loud. Watch what they do in reviews, then match it to a likely cause below. The table gives you a starting guess to test, not a verdict. Treat it as a hypothesis until you have spoken to the sponsor directly.
| Likely cause | What you notice | Move that fits |
|---|---|---|
| The options aren't clear | They ask what exactly they are choosing between, or reopen the background | A decision memo with options, a recommendation, and a date |
| Political or personal risk | They agree in private but won't commit in writing or in front of peers | Split the decision into a smaller first step that can be undone, and share ownership through the steering committee |
| Missing authority | "I need to check with [name]" comes up again and again | Ask who actually holds the decision and bring that person in, with the sponsor |
| Conflict between peers | Another executive's team objects, and the sponsor avoids taking sides | A steering committee item agreed in advance with both peers |
| Wanting more data | Every meeting ends with a request for another analysis | Agree what evidence would be enough and by when, then set a default |
| Shifted priorities | Reviews get cancelled and replies slow down | Ask directly whether the program still matters, and offer a pause or a re-charter |
A decision path is what keeps a program from drifting. As one governance explainer puts it, a steering committee can only work when sponsors are present enough to decide, not just observe.
How do I find out which cause it is?
The quickest way to learn why a sponsor is stalling is a short private conversation about the decision itself, not the whole program. Ask open questions, listen for the cause, and don't argue for your option yet. Hold it before the next steering committee so nobody is caught out in front of peers.
You can say this as is:
"I want to make the [decision] easier for you. What would you need to see to feel comfortable choosing? Is there anyone else whose view matters before you commit? And what worries you most about getting it wrong?"
Then check:
- Did they name a missing piece of information? That points to unclear options or a need for data.
- Did they name a person? That points to missing authority or a conflict between peers.
- Did they describe what could go wrong for them personally? That points to political risk.
- Did they change the subject to other priorities? That points to shifted priorities.
Write a few lines afterwards recording what you heard. That note goes into your decision log.
What should I put in front of the sponsor?
Give the sponsor a short decision memo that asks them to choose, not to think. EveryoneSocial sums up the idea as "never ask them to think. Ask them to choose." Put the bottom line first and the backup detail after it, and bring options to every problem you raise, as ITBusiness.ca advises for upward communication.
Copy this template:
Decision needed: [the decision in one sentence]
Needed by: [date], so that [milestone] stays on [date]
Recommendation: [option] because [main reason]
Options
A. [option]: [what happens], [main risk], [can it be undone? yes/no]
B. [option]: [what happens], [main risk], [can it be undone? yes/no]
C. Wait: [what slips], [who stays blocked]
Cost of waiting past [date]: [milestones that move], [people or teams waiting], [money or capacity committed], [windows that close]
Default: If we have no decision by [date], we will proceed with [option], which can be reversed until [date].
Who has been consulted: [names or roles]
Evidence: [link or attachment name]
Send the memo before the meeting, then use the meeting to confirm the choice rather than to explain the options.
How do I state the cost of delay without sounding like a threat?
State the cost of delay as plain facts from the plan: what moves, who waits, and what is already committed. Leave out blame and adjectives. A sponsor can argue with a tone of voice but not with a dependency chart, so link each cost to a dated milestone or a named deliverable.
Useful wording:
"If we decide by [date], [milestone] holds. Each week after that, [deliverable] moves by about the same amount, and [team] stays on [holding work] instead of [planned work]."
Check that each cost holds up against the current plan before you send it. If it doesn't, cut it.
Can I set a default decision if the sponsor doesn't reply?
A default decision is acceptable when the choice can be undone, sits within the program's agreed scope, and the sponsor has accepted the rule beforehand. Bring up the rule early, ideally when you first send the memo, so it reads as a working agreement and not as an ultimatum.
Wording to agree the rule:
"For decisions like this one, can we agree that if I don't hear back by [date], I'll go ahead with the recommended option and tell you the same day? You can still reverse it until [date]."
Don't use a default for anything that is hard to undo, affects another executive's budget, or commits the organization to an outside supplier or partner. Those need an explicit yes.
What if the decision is too big to make at once?
When a decision feels too big or too risky, split it so the sponsor can commit to the next step without committing to the whole outcome. This helps most when political risk is the cause, because a small step that can be reversed is easier to defend in front of peers.
- List what the full decision commits the organization to.
- Find the smallest step that unblocks the team, for example a pilot with [group], a design spike, or a limited purchase.
- Name the evidence that step will produce and the date you'll bring it back.
- Ask for a yes on the step only, and record when the larger decision is due.
How do I use the steering committee without ambushing the sponsor?
Raise the decision at the steering committee only after you have shown the sponsor the agenda item and asked them to present or co-present it. Talking to the members in advance turns the meeting into a confirmation rather than a confrontation, and it shares the ownership when peers disagree.
- Tell the sponsor: "I'd like to put [decision] on the steering committee agenda for [date]. Would you like to present it, or shall I?"
- Share the memo with each affected peer beforehand and ask what they need answered.
- Write the agenda item as a choice: "Decide between [A] and [B]; recommendation [A]."
- Record the outcome, owner, and date in the minutes before the meeting closes.
The sponsor role includes high-level decision making and resolving conflicts across departments, so a committee setting supports their job instead of going around it.
When is it acceptable to escalate above the sponsor?
Escalating above the sponsor is acceptable once you have made a clear request with a date, offered the steering committee route, and the cost of delay is now affecting agreed milestones. Tell the sponsor before you escalate, invite them to join, and describe it as getting help with the decision, not as reporting on them.
An escalation ladder:
- Direct request with a memo and a date.
- A reminder that names the date and the default.
- A steering committee item, set up with the sponsor.
- A conversation with the sponsor's manager or the program board, with the sponsor invited.
Wording for step 4:
"We haven't been able to settle [decision] since [date], and [milestone] is now at risk. I'd like to take it to [person or board] on [date] so we can get it unblocked together. Would you like to join, or would you rather raise it yourself?"
When should I formally pause the program?
Ask to pause or re-charter the program when the team can't usefully keep working without the decision, or when the sponsor tells you the program has lost priority. A formal pause protects the team's time and puts the reason on record.
Subject: Request to pause [program] pending [decision]
We have been waiting on [decision] since [date]. Without it, [workstreams] cannot progress beyond [point].
I propose we pause [workstreams] from [date], keep [minimal work] running, and restart within [period] of a decision.
If the program's priority has changed, I'd like to agree a re-charter or a new sponsor at [meeting] on [date].
How do I keep a written record of what was decided?
Keep a decision log that shows every pending decision with an owner, a date it was raised, a date it is due, and the outcome. Share it in each status report under "Decisions waiting," so the delay is visible to the steering committee without anyone confronting the sponsor.
Fields to track: [decision], [owner], [raised on], [needed by], [options], [recommendation], [default], [status], [decided on], [outcome], [evidence link]. Unblockd supports projects with deliverables, activities, tasks, evidence, blockers, risks, decisions.
Before your next sponsor meeting, write the memo for the oldest open decision, have the private conversation, and add the item to the log with a date.