Decision Rights: Why No One Knows Who Owns What

Ask three people in the same organisation who owns a decision and you will often get three different answers.

One will say it belongs to their manager. Another will say it needs sign-off from a committee that has not met in months. A third will say they thought someone else was handling it. None of them are wrong, exactly. They are each describing a different version of a decision that was never clearly assigned in the first place.

This is what a decision rights problem looks like from the inside. It rarely announces itself as a structural failure. It shows up as a delayed project, a duplicated piece of work, or a meeting that ends with everyone nodding and nothing actually decided. By the time leaders notice the pattern, they usually blame it on culture, capability or a lack of accountability. The research suggests otherwise. McKinsey's global survey on decision making found that only 20 percent of executives believe their organisation excels at decision making, and most admit that a large share of the time spent on decisions is wasted. Intelligence and effort are rarely the missing ingredient. Ownership is.

Decision rights define who has the authority to make a specific decision, who needs to be consulted before it is made, and who is accountable for the outcome. When those rights are unclear, decisions do not stop happening. They just happen slower, get made by the wrong person, or get quietly avoided until someone senior is forced to step in. This is precisely the territory that organisational design work is meant to address, because a structure only functions if the decisions running through it have somewhere clear to land.

What Decision Rights Actually Mean

Decision rights are the explicit answer to one question: who is allowed to decide this, and who else has a legitimate say. They are not the same as a job title, a reporting line, or a general sense of seniority. A person can sit high on an org chart and still have no real authority over a decision that matters to their team.

Most people assume decision rights are implied by structure. If you manage a department, surely you decide what happens in it. In practice, that assumption breaks down constantly. A regional manager may believe they can approve a new supplier, only to find out finance requires sign-off above a certain spend. A product lead may think they own the roadmap, until marketing pulls rank on a launch date for reasons nobody explained to them.

This gap between assumed authority and actual authority is where most confusion lives. Decision rights work only when they are made explicit, communicated, and understood the same way by everyone involved in a decision, not just the person who assumes they hold it.

A useful way to think about it: every meaningful decision has an owner, contributors, and people who simply need to know the outcome. When those three roles are not defined, everyone behaves as if they might be the owner, which is functionally the same as no one owning it at all.

Why Decision Rights Become Unclear in the First Place

Decision rights rarely fail because of one bad decision. They fail because the organisation grew faster than its structure, and nobody went back to redraw the lines. Early on, a small team does not need a formal framework because everyone can see what everyone else is doing. As the organisation adds people, functions and layers, that informal clarity disappears, but the assumption that "we all just know" often survives long after it stops being true.

There are a handful of recurring reasons ownership goes missing.

Growth outpaces structure. What worked for twenty people breaks down at two hundred. Nobody redesigns decision-making on purpose. It simply gets stretched until it snaps somewhere.

Matrixed reporting lines blur accountability. When someone reports to a function and a project, both sides may assume the other one owns a given call. Dual reporting is common and useful, but it multiplies the chances that a decision has no single home.

Decisions are confused with tasks. Responsibility for doing the work is often mistaken for the right to decide how the work should be done. A team can be fully responsible for delivering a project and still have no authority over the decisions that shape it.

Leaders hold onto decisions they no longer need to make. Sometimes ownership is unclear not because it was never assigned, but because a senior leader keeps intervening anyway, which teaches the organisation to escalate rather than decide.

Nobody owns the framework itself. Even organisations that once mapped out decision rights rarely revisit them. Reorganisations happen, people leave, new functions are created, and the original map quietly stops matching reality.

None of these causes are dramatic. That is exactly why they are so hard to catch early. Decision rights erode gradually, and the organisation usually only notices once the cost becomes visible.

The Real Cost of Not Knowing Who Owns a Decision

When decision rights are unclear, the cost shows up as slower execution, more escalation, and decisions that get revisited long after they should have been settled. It rarely appears as a single dramatic failure. It accumulates as friction that people learn to work around, which makes it easy to underestimate.

The first visible symptom is usually speed. Decisions that should take a day stretch into weeks because nobody wants to commit without confirming they are allowed to. People start seeking informal approval from several directions at once, just to protect themselves if something goes wrong later. That instinct is rational at an individual level and expensive at an organisational one.

The second cost is duplicated effort. Two teams may work on the same problem in parallel because each assumes the decision belongs to them, or because neither realises the other is already involved. This is rarely discovered until both pieces of work collide. Bain & Company’s research involving more than 350 organisations found that only around 15 percent practised effective decision-making. It also identified ambiguity over accountability as a recurring source of decision-making bottlenecks. When ownership is unclear, organisations tend to involve more people, create more approval points and slow the very decision they are trying to improve.

The third cost is quieter and more damaging over time: decision fatigue at the top. When ownership at lower levels is unclear, decisions travel upward by default. Senior leaders end up making calls that should never have reached them, which leaves less time for the decisions that genuinely require their judgement. It also sends an unintended signal to the rest of the organisation: real authority sits only at the top, so nothing moves without it.

Finally, unclear decision rights damage trust. When a decision is reversed after it was already communicated, or made by someone who was not expected to make it, people stop believing that decisions will hold. Once that belief erodes, teams start double-checking everything, which slows the organisation down even further.

The Warning Signs Your Organisation Has a Decision Rights Problem

You can usually diagnose a decision rights problem before it is named, because it leaves a consistent trail of symptoms across meetings, projects and reporting lines. The pattern is rarely subtle once you know what to look for.

Meetings end without a clear decision, and the same topic reappears the following week with no new information. People escalate issues that they could reasonably resolve themselves, because they are unsure whether they have the authority to do so, or because escalating feels safer than being wrong. Two departments each believe they are responsible for the same outcome, and neither finds out until something goes wrong. A decision gets made, then quietly reopened by someone who was never consulted the first time.

Perhaps the clearest sign is what happens when a senior leader goes on leave. If decisions stall in their absence, that is rarely a sign of their importance. It is usually a sign that decision rights were never actually distributed below them in the first place.

None of these signs prove that decision rights are the root cause on their own. Taken together, though, they point to the same underlying problem: the organisation has plenty of capable people and no shared agreement about who gets to decide what.

How to Define Decision Rights Without Creating More Bureaucracy

Fixing decision rights does not require a company-wide overhaul or a permanent new layer of governance. It requires identifying the decisions that actually matter, naming an owner for each one, and being explicit about who else needs a voice before the decision is made.

Start with the decisions, not the org chart. Most organisations try to fix ownership by redrawing reporting lines, when the actual problem sits at the level of specific, recurring decisions: who approves a budget over a certain threshold, who signs off on a hire, who decides which features ship this quarter. List the decisions that cause the most friction or delay, rather than attempting to map every decision the business makes. A handful of well-defined decisions will do more good than an exhaustive framework nobody reads.

Assign one owner per decision, not a group. A decision with three owners is a decision with none. The owner does not have to make the call alone, but they are the person accountable for ensuring a decision actually gets made and communicated. Everyone else contributing information or opinion is not the owner, however senior they are.

Separate who decides from who is consulted. Being asked for input is not the same as holding a veto. Many decision rights problems trace back to people who were meant to be consulted behaving as though they had the final say, or owners who felt they needed unanimous agreement before acting.

Write it down somewhere people can actually find it. This does not need to be complicated. A simple, shared reference that states who owns which category of decision is usually enough. What matters is that it exists outside of memory and assumption, and that people know where to look when they are unsure.

Push decisions to the people closest to the work. Ownership assigned by seniority alone tends to create bottlenecks, because the people with the most context are not always the people with the most authority. Decision rights work best when they sit as close as possible to the information needed to make a good call, with clear boundaries around when something should be escalated.

Common Mistakes Organisations Make When Assigning Decision Rights

Most attempts to fix decision rights fail for a small number of predictable reasons, usually because the framework is built once and then left to decay, or because it is designed without addressing the incentives working against it.

One common mistake is treating a decision rights exercise as a one-time project. A workshop produces a tidy document, everyone agrees it looks sensible, and it is filed away. Roles change, teams reorganise, and the document stops reflecting reality within a year, sometimes sooner. Decision rights need to be revisited on a rhythm, not set once and forgotten.

Another mistake is designing decision rights around hierarchy rather than expertise. Titles are an easy shortcut, but they do not always track who has the context to make the best call. Handing every meaningful decision to the most senior person in the room often slows things down rather than improving quality.

A third mistake is confusing clarity with control. Some leaders resist clearly assigning decision rights because it feels like giving something up. In practice, unclear ownership tends to concentrate more decisions at the top over time, not fewer, because everything defaults upward when nobody else is confident enough to act.

Finally, organisations often forget to address the incentives sitting underneath the framework. If people are still rewarded for avoiding risk rather than making sound calls, no amount of clarity on paper will change how they behave when a real decision is in front of them.

Making Decision Rights Stick

A decision rights framework only works if it survives contact with a normal working week, which means it has to be reinforced through everyday behaviour, not just documented once and left alone.

Leaders play the biggest role here. When a manager overrides a decision that was not theirs to make, or steps in the moment something looks slightly risky, the message that lands is louder than any policy document: nothing is really decided until someone senior agrees. Reinforcing decision rights means leaders deliberately letting decisions sit with the people who own them, even when they would have chosen differently themselves.

It also helps to check in periodically rather than waiting for a crisis to reveal the gap. A short, honest conversation with a few teams about where decisions are getting stuck usually surfaces the same handful of unclear areas. Fixing those specific points is far more effective than redesigning the whole system from scratch.

Decision rights are not a document. They are a habit the organisation either keeps or lets slip. The document only ever describes the intention. What people actually do when a real decision arrives is what determines whether ownership was ever clear at all.

The organisations that get this right rarely talk about decision rights very often. They have simply made ownership specific enough that nobody needs to ask. That, more than any framework on a slide, is what "who owns what" is supposed to answer.