Business & Organizations · People & management
Why teams need clear decision rights
Tell advice apart from the authority to decide, work out which decisions belong near the work, and keep a clear decision-maker open to the facts.

What you will learn
- Tell giving input apart from holding decision authority.
- Explain why responsibility without matching authority can create a problem.
- Assign the four roles for a specific task and spot which one has been left empty.
- Explain one advantage and one cost of centralizing decisions.
- Identify a condition that supports handing a decision to the people closer to the work.
- Place a single decision by how hard it is to undo and how far its effects reach.
Lesson 1 of 4 · 5 min
Who decides, who acts and who answers for it
Say five volunteers spend an hour choosing a venue for a fundraiser. They agree on one. Each leaves assuming someone else will book it, and a week later the date is gone.
Psychologists call this diffusion of responsibility. In a 1968 experiment, students heard a stranger having a seizure over an intercom. Of those who thought they were the only listener, 85% went for help. Of those who thought four others could hear, 31% did.
The volunteers had plenty of ideas, and they agreed. What the team never said was who could decide and who would act.
Four roles were tangled together in that meeting. Giving input means offering information or a recommendation. Decision authority means being allowed to choose, within a stated limit such as a budget. Execution means carrying out what was chosen. Accountability means answering for the result.
One person can hold several of these roles. The trouble starts when a team treats them as one thing, because then a good discussion feels like a decision, and a decision feels like a booking.
Here's one way the venue roles could be split. Volunteers advise on access and travel. A coordinator chooses within an approved budget, and answers to the board for how the day goes. An administrator makes the booking.
Other splits would work just as well. What helps is that the roles and their limits are visible, so everyone knows whose input is needed and who can commit the organization's money.
Now give someone the job without the power. Say the coordinator is told to secure a venue but can't approve any option. Every choice has to wait for someone else.
That can work if the coordinator knows who approves and how fast. It fails when the approver is undefined or out of reach, and the organization still blames the coordinator for the delay. That's responsibility without authority.
Try to recallWhy can making someone responsible for a venue booking fail if nobody specifies how approval works?
They may be expected to deliver the result without the authority to choose or spend, and may not know who can authorize what's needed.
The four roles make a checklist you can run before work starts. Who gives input? Who's authorized to choose? Who carries out the choice? Who answers for the result?
Nobody in the venue story disagreed. The checklist looks for something else, a role held by nobody. A role held by everybody comes to the same thing, as the intercom experiment showed.
Each empty role fails in its own recognizable way. With no one authorized to choose, discussion goes on and never commits. With no one to carry it out, a decision gets made and nothing happens, which is exactly how the booking went missing. With no one answerable, nobody notices afterward that it didn't happen. So when a task stalls, work backward from the symptom. It usually points to the role that was never assigned.
The checklist takes a minute, and it has limits. Naming who'll do the work doesn't give them the time or access to do it. Naming a decision-maker doesn't settle a real disagreement about what to choose.
It's still the cheapest fix a team has. You'll know it worked if the next action has one person's name on it.
Lessons in this topic
Who decides, who acts and who answers for it
Tell giving advice apart from having the authority to choose, and find the empty role when a task stalls.
When to decide on the spot and when to send it up
Weigh what it costs to send a decision up the chain, and place any decision by how hard it is to undo and how far its effects reach.
A clear decision-maker still has to listen
See why the authority to choose doesn't supply the facts, why a bad outcome doesn't prove a bad decision, and how to agree in advance when a choice gets reopened.
Decide once, then let a rule decide
Sort decisions into routine ones and new ones, and see how a rule hands the routine ones to the people nearest the work.
Three quick stories from this topic
The cord anyone can pull
Toyota permits every worker on its production lines to stop the line
They do it by pulling a cord called the andon, a word that comes from the Japanese for a paper lantern. Toyota decided once, as a rule, that anyone who spots a threat to quality may halt production, so nobody has to find a manager first.
A decision made in advance
A question that keeps coming back, with known criteria, can be settled once as a rule. Then whoever is closest applies it.
Where the rule ends
A rule covers only the conditions it assumed. A good one says when it stops applying, so unusual cases go back to a person's judgment.
One-way and two-way doors
Jeff Bezos sorts decisions into one-way doors and two-way doors
In his 2015 letter to Amazon shareholders, he wrote that most decisions are two-way doors. If one goes badly, you can walk back through, so a small group should make it fast. Only the nearly irreversible ones deserve slow deliberation.
The trap for big organizations
Bezos warned that as organizations grow, they tend to use the slow one-way process on two-way decisions too. The result, he wrote, is slowness and less invention.
Add reach
How hard a choice is to undo is half the test. The other half is how far its effects travel beyond the team making it.
The warning that stopped halfway
The people who made the final call to launch Challenger didn't know engineers opposed it
The night before the 1986 launch, the booster maker advised waiting for temperatures above 53 degrees Fahrenheit. Its managers then reversed that against their engineers' views. The presidential commission found that those who decided to launch were unaware of the warning.
Authority isn't knowledge
Everyone knew who could approve the launch. Authority says who's allowed to choose, and it doesn't tell that person what they haven't been told.
Agree on triggers first
A team can write down in advance what would reopen a decision. Then raising a concern means following an agreed rule, and nobody has to challenge the person in charge.
Sources
- 10.1 Organizational Structures and Design - Principles of Management | OpenStax, OpenStax, Rice University
- 2.1 Overview of Managerial Decision-Making - Principles of Management | OpenStax, OpenStax, Rice University
- How the social context influences helping (Principles of Social Psychology, section 9.3), Saylor Academy open textbook
- Andon - Toyota Production System guide, Toyota UK Magazine (Toyota GB)
- Amazon.com 2015 letter to shareholders (Exhibit 99.1), U.S. Securities and Exchange Commission, EDGAR
- Report of the Presidential Commission on the Space Shuttle Challenger Accident, Chapter V: The contributing cause of the accident, NASA History Office
- Space Shuttle Challenger disaster, Wikimedia Foundation





