Peter Drucker once observed that decision-making sits close to the heart of what management actually is. That’s true at the individual level — a manager’s judgement genuinely matters — but a less-discussed and equally important question sits above it: within a given organisation, who actually has the right to make a specific decision in the first place? A remarkable amount of organisational slowness and frustration traces back to this question going unanswered, or answered differently by different people at the same time.
Decision-Making Versus Decision Rights
It’s worth distinguishing two related but genuinely different things. Decision-making is the cognitive process of actually reaching a judgement — weighing options, assessing risk, choosing a direction. Decision rights is a separate, organisational question: given a specific decision, who is actually authorised to make it, who needs to be consulted first, and who simply needs to be informed once it’s made?
Most organisational friction around decisions isn’t actually about the quality of anyone’s judgement. It’s about ambiguity in this second, structural question — multiple people reasonably believing they had a say, or reasonably believing someone else did, in a way that only becomes visible once the decision has already caused friction.
Why This Ambiguity Is So Common
As organisations grow, decisions that used to be made informally by one person — often the founder, in a young or small organisation — need to be distributed across a growing number of people. This distribution rarely happens through a single, deliberate design decision. It tends to happen gradually and informally, as new people join and new situations arise, without anyone stepping back to define, explicitly, who actually owns what. The resulting structure often works reasonably well until the organisation reaches a size or complexity where the informal, undocumented understanding starts producing real, visible friction.
A Practical Way to Think About Decision Rights
For a given significant decision, it helps to separate out a few genuinely distinct roles, rather than treating “who’s involved” as a single undifferentiated group.
Who has the final say. Ultimately, one person or clearly defined group needs to be able to make the call, particularly when consensus isn’t reached — without this clarity, decisions can drift indefinitely, with everyone assuming someone else will eventually resolve it.
Who provides genuine input before the decision is made. Certain people have relevant expertise or a legitimate stake that warrants being consulted, even though they don’t have final authority — being clear about who this is, and ensuring they’re actually asked, prevents both wasted time consulting people whose input isn’t essential and the real cost of excluding someone whose perspective genuinely mattered.
Who needs to be informed once the decision is made, but doesn’t need to be consulted beforehand. Not every decision requires broad consultation, but many do require broad awareness once made — conflating these two categories, requiring consultation where only notification was needed, slows decisions down without adding proportionate value.
Who’s actually accountable for the outcome. This should generally align with who had final decision authority — accountability separated from actual authority tends to produce either resentment, if someone is held responsible for a decision they didn’t really control, or carelessness, if someone has authority without any real accountability attached to it.
Why Getting This Explicit Matters
When decision rights are genuinely clear, decisions move faster, because people aren’t spending time and energy figuring out who actually needs to weigh in. Accountability becomes cleaner, because the person with final authority and the person answerable for the outcome are the same person. And frustration decreases substantially, because people stop discovering, after the fact, that a decision affecting them was made without any input they’d reasonably expected to have — or, just as commonly, stop being asked for input on decisions where their view was never actually going to change the outcome, which wastes their time without adding real value.
A Practical Scenario
A growing company has an increasingly common problem: decisions about vendor contracts sometimes get made by a department head acting alone, sometimes require sign-off from a more senior executive, and sometimes get revisited after the fact when someone who felt they should have been consulted discovers a decision was made without them. No one deliberately designed this inconsistency — it simply accumulated as the company grew past the size where informal understanding was sufficient.
Leadership addresses it directly: for contracts above a defined value, final decision authority sits explicitly with a specific role, a short list of people are identified as required input before the decision, and a broader group is defined as needing notification once it’s made. The specific decision authority doesn’t change dramatically from what was roughly happening before — but making it explicit eliminates the recurring friction of people discovering, after the fact, that their expected role in a decision didn’t match reality.
Common Mistakes
Assuming everyone shares the same understanding of who decides what. This assumption rarely survives organisational growth, and the resulting mismatches often go unnoticed until they cause real friction.
Conflating “needs to be informed” with “needs to be consulted.” Requiring consultation where only notification was actually needed slows decisions without adding proportionate value.
Separating accountability from actual decision authority. Holding someone responsible for an outcome they didn’t genuinely control produces predictable resentment and undermines the accountability structure’s credibility.
Leaving decision rights undocumented as an organisation grows. Informal, undocumented understanding that worked at a smaller scale tends to produce increasing friction as more people and more decisions are added without explicit clarity.
Action Steps
- Identify one recurring type of decision in your organisation that regularly causes friction or confusion, and map out explicitly who currently has final authority, input rights, and notification rights.
- Check whether accountability for a specific outcome genuinely aligns with who held decision authority, and address any mismatch you find.
- Review whether people are being consulted on decisions where their input isn’t actually going to change the outcome, and consider shifting them to simple notification instead.
- Where genuine ambiguity exists about decision rights, address it explicitly with the people involved, rather than letting it persist informally.
- As your organisation or team grows, periodically revisit whether existing decision rights still make sense, rather than assuming an earlier informal arrangement still fits.
Key Takeaways
- Decision rights — who’s authorised to decide, who provides input, and who’s simply informed — are a distinct organisational question from the quality of any individual’s judgement.
- Ambiguity in decision rights, more than poor individual judgement, is a common source of organisational friction and delay.
- Accountability for an outcome should generally align with who actually held decision authority.
- Conflating consultation with simple notification slows decisions down without adding proportionate value.
- Explicit clarity about decision rights, revisited as an organisation grows, prevents much of the friction that comes from informal, undocumented understanding.
Conclusion
A great deal of organisational slowness and frustration has less to do with anyone’s judgement and more to do with an unanswered structural question: who actually has the right to decide this? Making decision rights explicit — who has final say, who’s genuinely consulted, who’s simply informed, and who’s accountable — resolves a surprising amount of friction that otherwise gets misattributed to poor communication or personality conflict, when the real issue was structural ambiguity all along.
Frequently Asked Questions
Isn’t clarifying decision rights just another form of bureaucracy?
Not when done well — the goal is actually to speed decisions up and reduce friction, by removing the ambiguity that causes people to spend time and energy figuring out who needs to be involved.
How detailed should a decision rights framework be?
Detailed enough to resolve genuine, recurring friction, without becoming so elaborate that maintaining it costs more than the clarity it provides — starting with the specific decisions that currently cause the most confusion is a reasonable approach.
What’s the difference between being consulted and being informed about a decision?
Consultation means genuine input is sought before the decision is made; notification means being told once it’s already been decided — conflating the two often slows decisions down without adding real value.
Should decision rights be reviewed periodically, or set once and left alone?
They’re worth revisiting periodically, particularly as an organisation grows or circumstances change, since an arrangement that worked at an earlier stage may no longer fit current scale or complexity.
What happens when accountability and decision authority don’t align?
It tends to produce either resentment, when someone is held responsible for a decision they didn’t really control, or carelessness, when someone has authority without meaningful accountability attached.
Can unclear decision rights affect morale, not just efficiency?
Yes — people who discover, after the fact, that a decision affecting them was made without input they’d reasonably expected to have often experience real, lasting frustration, independent of whether the decision itself was a good one.