Autocratic Decision Making

Stakeholder technique · See it on the map

Runnable here

One person — usually the project manager or another accountable role — makes the decision alone, without a group vote or consensus process.

When to use it

Under real time pressure, where accountability for the outcome is clearly and solely held by one person, or where the decision is technical or narrow enough that consulting the wider group would be theatre rather than useful input. It is a legitimate, often correct, choice in those conditions — not a fallback to apologize for.

When to avoid it

Avoid it when the decision needs the group's buy-in to actually get implemented, or when the people affected have information the decision-maker doesn't have and hasn't asked for. Above all, never use it while pretending consultation happened — running a 'discussion' whose outcome was already decided costs more trust than deciding openly and saying so would have.

Steps

1. Confirm the decision genuinely sits with one accountable person — check this before acting, not after someone objects.
2. Gather whatever input is fast to get and actually useful, without treating it as a vote.
3. Make the decision.
4. State plainly that this was a unilateral call and why — the time pressure, the accountability, the technical narrowness — rather than dressing it up as group consensus.
5. Communicate the decision and the reasoning to everyone affected.

What it produces

• A decision made quickly, with a single named owner.
• A stated reason the decision was made this way, on the record.

Common pitfalls

• Running a sham consultation — asking for input on a decision that's already made — which erodes trust further than an honest 'I decided this' would have.
• Reaching for it as a default when the real reason is avoiding a harder conversation, not genuine time pressure or clear accountability.
• Using it on a decision that needed the affected team's buy-in to actually be implementable, and then being surprised when implementation stalls.

Worked example

A production outage is degrading customer checkout. The engineering lead has fifteen minutes to choose between two rollback options, both with tradeoffs, and is the only person with the on-call context to weigh them properly. She decides alone, executes the rollback, and posts a two-line note afterward: 'I made this call unilaterally given the time window; here's why, and here's what I didn't have time to check.' The team accepts the decision because it was presented as what it was.

Source

• PMBOK-6 §5.2.2.4

Where it comes from: this technique is named by the PMBOK Guide, 6th edition.