One of your best people just walked into your office with a decision they were completely capable of making themselves. You made the call anyway, because it was faster, because you weren't sure they'd get it right and because it felt easier than explaining what "good" looks like.
Every time you do that, you teach them not to try next time, and you become the bottleneck every decision in your team has to pass through.
Decision-making rights are the explicit, agreed answer to four questions for any decision that matters in your team:
who can decide it alone,
who has the final call once it's above a certain size,
who needs to be consulted before it's made, and
who simply needs to be told once it's done.
When leaders skip this step, delegation quietly fails, no matter how much responsibility they've handed over on paper.
Decision-making rights are the explicit answer to who is allowed to decide what, at what size, with whose input, before a decision is treated as final. They're different from responsibility, and the difference is where most delegation quietly breaks down.
Responsibility is what someone is expected to deliver. Decision rights are what they're actually allowed to decide on the way there, without it bouncing back to you first. You can hand someone full responsibility for a project and still make every meaningful decision inside it yourself. That isn't delegation. That's supervision wearing delegation's clothes.
In my coaching practice, this is the single most common reason delegation looks like it's working and isn't. A manager tells a team member "this is yours now," hands over the responsibility, and then keeps quietly deciding the parts that matter: the budget, the client exception, the priority call when two things clash. The team member notices, even if nobody says it out loud. They stop reaching as hard, because reaching didn't actually change what happened.
If this is happening on your team, it usually shows up as one or more of these patterns:
None of these are confidence problems. They're clarity problems. And they cost more than time.
Managers influence roughly 70% of what actually drives team engagement and wellbeing (Gallup), and burnout shows up differently depending on where someone sits in the business.
For the person in the middle absorbing decisions that were never clearly theirs to make or hand off, unclear decision rights don't just slow the team down. They quietly wear that person out, usually your best people, because they're the ones who keep absorbing the ambiguity rather than pushing back on it.
This is the part most delegation advice skips. It isn't complicated, but it does need to be deliberate.
1. List the decisions that keep coming back to you. Not in the abstract. Write down the actual, specific decisions that have landed on your desk in the last month: a budget reallocation, a client discount, a hiring call, a schedule change or a priority clash between two projects.
2. For each one, name four things out loud. Who can decide it alone, up to what size or threshold. Who has the final call above that threshold. Who needs to be consulted before the decision is made. Who simply needs to be told once it's done. If there's a genuine veto sitting with you, your director, or a compliance requirement, name that too, so nobody discovers it after they've already committed to a call.
3. Say it, don't just write it. A decision-rights document nobody has actually discussed changes nothing. Tell the person directly: "This one's yours to decide, up to this point. I trust your read on it. Let me know what you land on and why." That sentence does more work than any policy.
4. Let the first mistake be theirs. One of the things I say in my book, Trusted to Thrive, is that you can't talk your way into trust, you have to behave into it. Handing back a decision and then quietly fixing it if it goes sideways teaches your team the opposite of what you just told them. Let it be theirs. Mistakes included.
5. Review it as people grow. Decision rights aren't a one-off conversation. Revisit them every few months, especially after someone's handled a few decisions well. The threshold that made sense six months ago is often too conservative now.
It rarely looks like chaos. It looks like a team of capable people quietly checking with everyone else, because nobody's fully sure what they're actually allowed to decide alone.
That ambiguity has a cost, and it isn't only measured in slower decisions. Businesses with high organisational design maturity, meaning clear, simplified decision rights and transparent accountability, achieve 23% higher revenue growth over three years than low-maturity peers, and are significantly more likely to hit their financial targets (Deloitte).
Fixing this isn't just about reducing friction for your team. It's one of the more overlooked growth levers available to a manager who's willing to have the conversation.
Pick one team member and one recurring decision, and ask them two questions directly. Write down what they actually say, not what you assume they'd say.
"Which of your decisions do you feel confident are genuinely yours, and which do you still bring to me out of habit rather than necessity?" The second half of that answer is where the ambiguity is hiding.
"What would make you trust that a decision I've handed you is actually yours to keep?" Some people will say a clear threshold. Others will say being left alone after a mistake instead of quietly corrected. Don't assume. Ask.
Run this with two or three people and a pattern will usually appear fast: the same one or two decision types, repeated across different people, that nobody has ever actually assigned.
Your team isn't escalating decisions because they can't handle them. They're escalating because nobody has ever told them, clearly and out loud, what's actually theirs to decide. That's a conversation you can have this week, not a system you need to build over a quarter.
If naming decision rights with your team feels like exactly the kind of leadership skill you were never formally taught, that's precisely what the Tribe of Trusted Leaders program builds systematically over 12 months, alongside the accountability and feedback skills that go with it. It's designed for managers and emerging managers carrying real responsibility without ever having been taught how to hold real authority either.
How is delegation different from delegating decision-making rights? Delegation often hands over responsibility for an outcome while the leader keeps making the decisions inside it. Delegating decision-making rights goes further: it explicitly hands over the authority to decide, not just the task of delivering. Without that second step, delegation looks real but quietly isn't.
How do I know if my team has unclear decision rights? Watch for the same decisions coming back to you repeatedly, meetings that multiply without resolving anything, people waiting instead of acting, and quiet rework or resentment after a decision gets overridden. These are clarity problems, not confidence problems.
What should I do if my team keeps bringing decisions back to me? Name the specific decision, agree out loud who owns it and at what threshold, and say so directly rather than assuming it's understood. Then let the first outcome, including a mistake, genuinely belong to them.
How often should decision rights be reviewed? Every few months, and especially after someone has handled a decision well a few times. Thresholds that made sense when someone was new are often too conservative once they've built a track record.
Does giving my team more decision-making rights slow things down if too many people need to be consulted? It slows things down if you over-design it. Keep the "who must be consulted" list genuinely short, usually one or two people, and reserve it for decisions with real downstream risk. Most decisions only need an owner and a threshold, not a committee.