The Importance of Project Manager Decisiveness: How to Decide Faster Without Deciding Badly
On a project, an undecided question is not neutral. People wait, work gets built on guesses, and the date moves. Decisiveness means making timely, well-reasoned decisions, owning them and correcting course when new facts arrive. This guide explains why it matters, what the research suggests about speed and quality, and gives you a method, a worked example and a decision log you can use on your next project.
What decisiveness is, and is not
It is choosing a course of action in time to be useful, based on the best information available, and then committing to it. It includes saying “not yet, and here is when I will decide.”
It is not impulsiveness, ignoring other views, or refusing to change your mind. A decisive manager decides quickly and also updates quickly. Stubbornness is a different trait, and a harmful one.
The opposite problem is just as real: delaying a decision until certainty arrives, which on a project it rarely does.
Why it matters: what the research says
We could not find rigorous research on project manager decisiveness specifically. The best evidence we found is general research on organizational decision-making. McKinsey’s survey of 1,259 executives in 91 countries, published in April 2019 as Decision making in the age of urgency, reports:
- Only 20% of respondents said their organizations excel at decision-making.
- 57% said their organizations consistently make high-quality decisions, and 48% said they make decisions quickly. Just 37% said both.
- 61% said most of their decision-making time is used ineffectively.
- Faster decisions tended to be higher quality. Quick decision makers were twice as likely as slow ones to make high-quality decisions.
- Fewer reporting layers went with better results: 70% of respondents at organizations with one to three layers said they make high-quality decisions, against 45% at organizations with seven or more.
These are self-reported views from a survey, and they show association, not cause. They do suggest that speed and quality are not simple opposites. The same article advises prioritizing speed for low-risk or reversible decisions and quality for big bets.
What this means on a project (our reasoning, not a finding):
- Delays compound. A one-week wait on one decision can hold up several tasks that depend on it.
- Teams lose time and morale when direction is unclear.
- Stakeholders trust managers who make clear calls and explain them.
- Undecided issues often turn into scope creep and surprises. See also why projects fail.
Decisions a project manager makes
The table is our summary of common project decisions. How much a project manager decides alone depends on the project’s governance, so agree decision rights early.
| Decision | Easy to reverse? | Usually decided by | Suggested timebox |
|---|---|---|---|
| Task order and daily priorities | Yes | Project manager and team | Same day |
| Minor scope trade-offs | Mostly | Project manager, within agreed limits | 1–2 days |
| Adding or moving people | Partly | Project manager with line managers | 2–5 days |
| Approving a change request | Depends | Sponsor or change board | Within the agreed cycle |
| Choosing a supplier or tool | Hard | Sponsor with the project manager | Set a date, then hold to it |
| Go or no-go at a milestone | Hard | Sponsor or steering group | At the gate meeting |
| Escalating a problem | Yes | Project manager | As soon as it threatens a baseline |
A responsibility matrix removes a lot of hesitation. See the responsibility assignment matrix and project team roles and responsibilities. For how approved changes are handled, see the monitoring and controlling process group.
Two kinds of decision
A useful rule is to ask first: if this is wrong, can we undo it cheaply? A framework attributed to Jeff Bezos, summarized in Farnam Street’s article on reversible and irreversible decisions, calls them “one-way doors” and “two-way doors”:
- One-way doors are irreversible or nearly so. Slow down, consult and test assumptions.
- Two-way doors can be reversed if they go badly. Decide quickly, with a capable person or small group, and adjust.
The article warns that large organizations often apply the slow process to two-way decisions, creating delay and risk aversion. It also reports that Bezos treats about 70% certainty as the point to act. That figure is a rule of thumb, not a science, but the idea is sound: waiting for near-certainty usually costs more than correcting later.
Worked example: the cost of waiting
Everything here is made up to show the reasoning. A team must choose between two ways to integrate online payments. A manager wants five more working days to gather information.
| Item | Working | Amount |
|---|---|---|
| Cost of each day of delay (idle time, later launch) | Assumed | $2,000 |
| Cost of waiting five days | 5 × $2,000 | $10,000 |
| Rework cost if the choice proves wrong | Assumed | $6,000 |
| Chance the choice proves wrong | Assumed | 30% |
| Expected cost of deciding now | 30% × $6,000 | $1,800 |
Waiting costs $10,000. Deciding now carries an expected cost of $1,800. The choice is also reversible. So the decisive move is to decide now, set a checkpoint after the first prototype, and be ready to switch.
Change the numbers and the answer changes. If a wrong choice cost $100,000 and could not be undone, a week of extra analysis would be cheap by comparison. The method is to compare the cost of delay with the cost of being wrong, not to always go fast.
Worked example: a decision matrix
For harder decisions, write the criteria and weights before you look at the options. Suppose a project is three weeks behind. The options are A: cut nice-to-have features, B: add two contractors, C: move the launch date by three weeks. Each is scored from 1 (poor) to 5 (strong). The weighted score is the sum of weight × score, divided by 100.
| Criterion (weight) | A: cut scope | B: add contractors | C: move date |
|---|---|---|---|
| Keeps the launch commitment (35) | 4 | 4 | 1 |
| Cost (25) | 5 | 2 | 4 |
| Quality risk (25) | 3 | 2 | 5 |
| Team strain (15) | 4 | 3 | 4 |
| Weighted score | 4.00 | 2.85 | 3.20 |
Option A scores highest. Scores are judgments, so test the result: if A still wins when you shift the weights, the decision is robust. Whatever the matrix says, a scope cut is a change, so take it through change control and agree it with the sponsor.
Decision log template
Recording decisions saves arguments later and shows you what you learned. Keep it short.
Decision log: [project name]
ID: D-[number] · Date: [date] · Decision owner: [name] · Decide by: [date]
1. The question: [One sentence.]
2. Type: Reversible / Hard to reverse · Cost of delay per day: [amount or effect]
3. Options considered: [List, with pros and cons.]
4. Criteria and weights: [What matters, set before scoring.]
5. Decision and reason: [What we chose and why.]
6. Who was consulted / who must be told: [Names.]
7. Review trigger: [What new fact or date would make us revisit this?]
8. Outcome (later): [What happened, and what we learned.]
Eight habits of decisive project managers
- Set a decision date. “We decide on Thursday” focuses minds and prevents drift.
- Sort by reversibility. Move fast on two-way doors, slow on one-way doors.
- Agree the criteria first. It stops the debate becoming a vote on favorites.
- Decide at the right level. Push decisions to the lowest level with the knowledge and authority. McKinsey’s survey found this practice was strongly associated with decision-making success.
- Get the right people, not all the people. Consult those with knowledge; inform the rest.
- Invite disagreement before the decision. Ask what would make this fail. Once decided, ask for commitment even from those who disagreed.
- Write it down. Use the decision log and share it.
- Review outcomes. Check a few decisions each month to see what you got right and wrong.
Common pitfalls
- Analysis paralysis. More data for a reversible decision is usually wasted time.
- False decisiveness. Deciding fast on a one-way door without checking the facts.
- Flip-flopping. Changing course without a new fact. Use a review trigger.
- Hidden decisions. Choices made in side conversations that the team never hears about.
- Decisions without owners. If nobody owns it, nobody makes it.
- Ignoring the people affected. A fast decision that triggers resistance is a slow one.
- Never reviewing. Without a look back, you repeat mistakes.
See also 12 common project management challenges and 15 project management tips.
Building the skill
Decision-making grows with practice, feedback and a few good tools. Start by keeping a decision log for one month. Then read about the other “people” skills in soft skills for project managers, and see how the role looks in practice in project manager jobs.
For structured learning, providers such as Coursera and Udemy list project management courses. We may earn a commission if you sign up, at no cost to you. We are not affiliated with any university. If you are preparing for an exam, start with the PMP exam prep course guide.
Frequently asked questions
Why is decisiveness important for a project manager?
Undecided questions hold up dependent work, move dates and unsettle the team. Timely decisions keep work flowing and show clear leadership.
Does deciding faster mean deciding worse?
Not necessarily. In McKinsey’s survey, quick decision makers were twice as likely as slow ones to report high-quality decisions. The survey is self-reported, but it suggests speed and quality can go together, especially for reversible decisions.
How do I decide when I do not have all the information?
Ask whether the decision is reversible, compare the cost of waiting with the cost of being wrong, and set a review trigger. Many project decisions will never have full information.
What is the difference between decisive and impulsive?
A decisive manager uses relevant input and criteria, then commits. An impulsive one skips the thinking. The decisive manager also changes course when facts change.
How do I get better at making decisions?
Keep a decision log, review outcomes, agree criteria before scoring options, and set decision dates.
Who should make project decisions?
The person with the knowledge and authority, at the lowest suitable level. Agree decision rights at the start, for example in a responsibility matrix.
Browse certificate, course and degree programs side by side.