Project managers make decisions all day. We decide how to structure the work, who needs to be in a meeting, what needs escalating and whether a risk response is worth the effort. But the bigger the decision, the less likely it is to be ours to make.
At some point, the choice belongs to the sponsor, project board or another senior leader. That’s where a different project management skill becomes important: helping the person with the authority make a good decision, at the right time, with enough information to understand the consequences.
That is not the same as learning another decision-making technique. If you want the mechanics of working through a choice, start with my guide to project decision-making. Here, I want to focus on the project manager’s role in executive decision support: turning delivery detail into something senior leaders can actually act on.
Know which decisions are actually yours
One sign of an experienced project manager is that they don’t escalate everything. Senior leaders do not need to approve every change in meeting dates, every small spend decision or every adjustment to the plan. If you have delegated authority to deal with something, deal with it.
Equally, do not quietly make a decision that sits outside your authority simply because getting time with the sponsor is difficult. I have seen both extremes: project managers who ask permission for everything, and project managers who carry on making increasingly significant calls because “someone had to decide”. Neither is particularly helpful, and both can get you into trouble.
Get clear on decision rights early. Your governance arrangements should tell you what can be decided within the project team, what belongs with the sponsor (or steering) and what needs wider executive approval, through investment committees, the PMO, change boards and so on. Tolerances, delegated financial authority, terms of reference, and escalation thresholds all help.
The practical test I use is: does this decision materially change the business case, benefits, risk exposure, strategic intent, budget, timeline or operating model? If yes, it probably needs to go upwards. If not, you may be able to make the call and keep the project moving.
Translate project information into business consequences
Project teams live in detail. We know which test script failed, which supplier is late, how many tasks have moved and why the integration environment is unavailable. Senior leaders rarely need all of that information.
They need to know what the detail means.
For example:
- Project information: “Testing is two weeks late.”
- Decision-support information: “If testing moves beyond 30 September, we lose the only implementation window before peak trading. We can add testing capacity now, reduce scope, or move the launch to January.”
The second version gives the decision-maker a consequence and a choice. It connects delivery performance to something the business cares about.
This is why business acumen matters for project managers (it’s specifically called out as a PMI Power Skill). It’s still a development area for many project professionals. PMI’s 2025 Pulse of the Profession found that only 18% of project professionals demonstrated high business acumen, and those with stronger business acumen were more likely to meet business goals, schedules and budgets.
You need enough understanding of the business case, benefits, operating model and strategic priorities to explain why a project issue matters outside the project team. A red milestone is not inherently interesting, although I know many execs will want to go straight to that, so they can fix it. It’s the effect of that red milestone on revenue, compliance, customer experience, capacity or another strategic objective that they should be caring about.
Bring a recommendation, not just a problem
There are times when the right thing to say is, “I don’t know yet.” But there are many more occasions where the project manager can do (at least some of) the analysis before asking the sponsor to choose.
Instead of taking a problem to the project board and asking, “What do you want to do?”, prepare the decision so the group can spend its time making the choice rather than discovering the issue from scratch.
A useful decision brief includes:
- the decision that is required
- your recommendation
- the realistic alternatives
- the main trade-offs
- the evidence behind the recommendation
- what happens if no decision is made
- the date by which you need the decision.
That does not mean pretending there is only one sensible answer. Your recommendation may be based on delivery considerations while the sponsor has access to commercial, political or strategic information that changes the picture. Your job is to make your reasoning visible so they can challenge it.
Being able to make a recommendation is not only a project management skill. The World Economic Forum’s Future of Jobs Report 2025 found that analytical thinking remains the most sought-after core skill, identified by 69% of employers, while leadership and social influence was cited by 61%.
It is also worth separating solving the underlying issue from choosing what to do next. I have written separately about the difference between problem solving and decision making. They are related, but they’re not the same activity.
Build enough business acumen to understand the trade-offs
You don’t have to become a finance director to support executive decisions. However, it helps enormously if you understand the language behind the trade-offs you are presenting.
Depending on your environment, that could mean understanding:
- Opportunity cost: what else cannot happen if resources stay on this project
- Cost of delay: what waiting another month actually costs the organization
- Benefits and value: what outcome the project is meant to create, not simply what it is delivering
- Total cost: including ongoing support, licences, maintenance, training and operational effort
- Strategic fit: whether the initiative still supports the priorities the organization has today, not only the priorities it had when the business case was approved.
Most project managers build this knowledge through experience: sitting in governance meetings, working with Finance, talking to sponsors and seeing what happens after a project goes live. Mentoring and cross-functional work help too.
Formal study is another route if you want a broader grounding in finance, strategy and leadership. For example, a Master of Business Administration online can provide a structured way to learn how the different parts of an organization fit together.
You don’t need an MBA to become a strategic project manager, but you do need to understand enough about the business to recognize what makes a trade-off important.
Be explicit about uncertainty
Executive decisions are often difficult because the information is incomplete. If the answer were obvious and the data perfect, the decision probably would not need much senior attention.
One of the most useful things you can do is separate what you know from what you think is likely to happen. Label the information clearly.
- Facts: things already evidenced or agreed.
- Estimates: numbers based on known inputs and an estimating approach.
- Assumptions: things you are treating as true for planning purposes.
- Forecasts: your current view of what is likely to happen.
- Unknowns: information you do not yet have and may not be able to get before the decision is required.
Avoid false precision
I would much rather tell a sponsor that the cost is likely to be between £180,000 and £230,000 than present £204,738 as if we have somehow achieved perfect certainty. False precision does not make a recommendation more credible!
Although I also remember being told as a young project manager that not submitting a round number made it look like we’d worked out the budget forecast somehow, instead of just guessing, which is what we were basically doing.
How you present the information matters too. The same facts can feel very different depending on whether you emphasize the potential gain, the potential loss, the short-term impact or the long-term consequence. My article on the impact of framing in decision making goes into that in more detail.
And if you are wondering why capable people still make poor choices when they have plenty of information, there are some common traps. I cover three of them in 3 things that stop you making the right decision.
Match the decision process to the decision
Not every decision needs a workshop, thankfully. Not every decision should be made by one senior person either.
Think about what kind of input will give you the right data for the decision. A technical architecture decision may need specialist advice. A change to a frontline process probably needs input from the people who will use it. A time-critical incident may need one person to decide quickly so everyone else can get back to work.
If a collaborative approach is appropriate, I have a practical guide to helping teams make group decisions. There are also situations where autocratic decision-making is the no brainer choice: someone has the authority, the decision is time-sensitive and wider consultation will not materially improve the outcome.
You can also reduce the stakes by avoiding one giant, irreversible decision. On uncertain projects it may be possible to approve a pilot, fund the next tranche or test an assumption before committing further. That is close to the incremental model of decision-making: moving forward in smaller steps as more information becomes available.
Manage the decision pipeline, not just individual decisions
A project can have perfectly good governance and still grind to a halt because decisions are sitting with busy people – this is decision latency, the slowness of decision-making.
One outstanding decision may not be a problem. Five decisions, each dependent on the one before it, quickly become a delivery issue. I think of this as decision debt: unresolved choices accumulate until the team is spending more time working around them than moving the project forward.
Manage significant decisions as actively as you manage risks and actions. For example:
- Keep a visible list of decisions waiting for action
- Give each decision an owner and required-by date
- Show the impact of missing that date
- Pre-circulate and socialize major decisions with key stakeholders before the formal meeting
- Make the decision ask obvious in papers and presentations
- Escalate an impending decision delay before it becomes a schedule delay.
And please do not hide the decision on slide 17 of a 30-slide project board pack. If you need the group to choose something, say so at the beginning, because who is going to read to slide 30?
A clear heading such as “Decision required: approve Option B by Friday” is far more useful than hoping everyone spots the ask in the discussion. Pop it in the exec summary right at the front.
Close the loop after the decision
The meeting finishes, everyone closes their laptops and the conversation moves on. That is exactly the point where a decision can disappear.
Confirm what was agreed, especially if the discussion moved away from the options originally presented. I worked with a sponsor who was incredibly good at this. He would summarize the actions and decisions in the last 5 minutes of the meeting, even though I had been taking the minutes. He must have had his own notes because the meetings could get a bit rambly.
Then turn the decision into delivery: update the schedule, budget, risks, scope or communications as required.
For decisions that matter, record the rationale as well as the answer. Six months later, “We chose supplier B” is much less useful than “We chose supplier B because they were the only bidder able to meet the regulatory deadline, despite the higher cost.” A project decision log gives you a simple structure for keeping that history.
Five habits that make your advice easier to act on
If you want senior stakeholders to see you as someone who helps them make decisions rather than someone who simply reports project status, these are the habits I would focus on.
- Lead with the decision required. Do not make people listen to ten minutes of background before they understand why you are in the room.
- State your recommendation. You are allowed to have a professional view, even when someone else owns the final choice.
- Quantify what matters, but do not invent precision. Use ranges, assumptions and confidence levels where that is a more honest presentation of where you are now.
- Say the uncomfortable trade-off. If saving three weeks means accepting more operational risk, say so plainly.
- Say when you need the answer. A decision without a required-by date has a habit of becoming tomorrow’s problem!
For more ideas on strengthening your own everyday judgement, see my 5 tips for making better decisions every day.
Make yourself useful at the decision point
Becoming more strategic as a project manager is not about pretending to be a senior executive. It is about understanding the business well enough to recognize what matters, applying project judgement to the evidence and making the consequences of each choice clear.
That means doing the analysis before the governance meeting, knowing where your authority ends, presenting uncertainty honestly and making it easy for the right person to choose.
Do that consistently and you stop being the person who turns up with a status report and a list of problems. You become the person whose advice helps senior leaders decide what happens next.
