Decision-Making Rights: How To End Your Leadership Team's Bottleneck
Most founders treat decision-making as binary. Either you make the call or you delegate everything. The framework that fixes the bottleneck gives you a more practical approach.
A founder told me last quarter that her leadership team had become "a really expensive group chat." Every decision routed back to her. Even the ones she had no business making. She was burning hours each week answering questions her team was perfectly equipped to answer themselves. When I asked why she didn't push them back, she said, "Because if I don't decide, no one will."
She wasn't wrong. Her team had stopped deciding. And that's The Decision Gap. Not a confidence problem, not a talent problem, not a trust problem. A clarity problem. Her people didn't know which decisions they actually owned, so they kicked everything upstairs.
Most founders I work with see this as a binary choice. Either you make the call, or you delegate everything. That mental model is what creates the gap in the first place. Binary thinking forces a binary outcome. Either you're in every decision, and your team stalls without you, or you're in none of them, and your team makes uncoordinated calls without you.
There's a more practical approach. It involves naming what role each person plays at each stage of a decision. Most teams have never thought about decisions this way. Once they do, the gap closes.
Three Faces of the Decision Gap
The Decision Gap shows up in three different faces. Most teams have at least one. Some have all three at the same time on different decisions.
The first face is the one most founders recognize. Every meaningful decision routes through the founder. The team sees something that needs deciding, packages it up, brings it to the founder, and waits. Sometimes they wait for approval. Sometimes they wait for the founder to actually make the call. Either way, the founder becomes the chokepoint. I worked with a CEO who was getting twenty Slack messages a day from his team asking what to do about X, Y, and Z. His calendar had become a queue of decisions waiting for him. He told me he felt like a switchboard operator, not a leader. That's the bottleneck face. The founder is in every decision because no one knows which ones they can make without her.
The second face is harder to spot from the outside but more common than founders realize. I call it Violent Agreement. The team gathers around an issue. Everyone agrees on what's true. Everyone agrees on what should happen. The conversation loops. No one makes the call. The meeting ends with someone saying, "Okay, let's circle back next week." The same conversation happens next week. Then the week after. The team isn't stuck because they disagree. They're stuck because no one knows who owns the decision. There are no defined Make Rights, so the team treats every meeting as a discussion forum rather than a decision-making forum. In one engagement, I watched a leadership team have the same conversation about pricing tiers in three consecutive weekly meetings. They were aligned every time. They just never decided.
The third face is the inverse failure mode. The founder, having heard "you need to delegate more," delegates everything. No structure, no framework, no clarity on who decides what. Now every department head makes their own calls. Marketing rolls out a campaign that contradicts what sales committed to. Operations sets a customer policy that conflicts with the one finance just signed off on. The founder thinks she's empowering the team. The team thinks they have full authority over everything. The result is Decision Sprawl. Decisions happen, but they happen in isolation, often in conflict, and without coordination. The company moves, but not in one direction.
These three patterns look like opposites. The bottleneck is too few decisions. Sprawl is too much. Violent Agreement is a decision that never happens. But they share a single root cause. None of these teams has defined who owns each decision and what role everyone else plays. The gap is the same. Only the symptoms differ.
The Binary Trap That Creates the Gap
Most founders have never seen a real alternative to "I make the decision" or "I delegate the decision." That's the binary trap. It's a mental model that forces every decision into one of two boxes, and both boxes are wrong most of the time.
Founders default to the trap because no one taught them another way. Business school doesn't typically teach this. Neither do most management books. The frameworks people learn at the operational level, like RACI, are designed for project execution, not for the executive table. So founders inherit a binary view. Be in or be out. Make the call or delegate the call.
The cost of the binary view is what you're seeing on your team right now. Every decision becomes a question of "is this important enough that I should be making it?" High-stakes decisions you're in. Low-stakes decisions you're out of. There's no nuance about how you're involved, when you're involved, or what role you actually need to play. So the team defaults to either bringing you everything or running with everything.
The fix isn't to draw a sharper line between what you decide and what they decide. The fix is to recognize that decisions have multiple rights distributed across the people involved at different stages. Your role in a given decision might be to provide input. Or to approve. Or just to be informed afterward. None of those is the same as making the call, and none of them is full delegation.
When founders see this for the first time, the response is often the same. "I didn't know I had that option." That's exactly the gap closing.
The Five Stages: How Decision-Making Rights Actually Work
Every decision moves through five stages. At each stage, specific people have specific rights. The framework is called Decision-Making Rights. The five stages are Input, Collaborate, Make, Approve, and Inform.
Input. The first stage is gathering the information that informs the decision. Whoever has Input rights provides data, perspective, or context that the decision-maker needs. Input rights are the most underused. Founders skip this stage and go straight to deciding, which means they decide without the information they actually need. The work of defining Input rights is naming who has the data or judgment that should shape the call, and what form that input takes. Sometimes, input is a written brief submitted 24 hours before the decision meeting. Sometimes it's a single Slack message answering a specific question.
Collaborate. The second stage is joint sense-making. Collaborate rights belong to people who need to actively shape the decision together with the decision-maker, not just provide one-way input. This is where cross-functional decisions get worked out. Marketing and sales might have Collaborate rights on a pricing change because the decision affects both functions and needs joint design. Collaborate is heavier than Input because it involves dialogue and revision. It's lighter than Make because no one in the Collaborate column has the final say.
Make. The third stage is the actual decision. Whoever has Make rights makes the call. This is the right that founders most commonly crowd. Most leadership teams I work with try to put three or four people in the Make column for a single decision, which turns every decision into a committee process. My standard move is to push people out to the edges. Most of the people you currently have in Make should be in Input or Inform. Make should typically be one person. If more than one person has Make rights, the team needs an explicit sub-process for reaching a single decision among them.
Approve. The fourth stage is ratification. Approve rights belong to whoever can sign off on or veto the decision, but isn't making it. This is where founders often live without realizing it. You don't make the call, but you need to sign off before it goes live. Naming your role as Approve rather than Make lets the team work through the decision before bringing it to you, instead of waiting for you to drive it from start to finish. MIT Sloan calls this "deciding about deciding." Be explicit about which decisions you're approving versus making.
Inform. The final stage is communicating the decision to people who need to know but weren't involved in the decision. Inform rights matter more than founders typically think. A decision that's made but not communicated doesn't actually take effect. Like Input, Inform can be specified down to the form, timeframe, and channel. "Engineering leadership will be informed via email within 48 hours of the decision." That level of specificity prevents the common failure where the decision was made in the room, but no one outside the room knew about it three weeks later.
What Senior Teams Get Right About Decisions
The senior teams that win don't make perfect decisions. They make good decisions quickly, and they make a lot of them.
Harvard Business Review made the case in 2017 that senior teams should treat decisions as a structured workstream, not as the accidental output of whatever happens to be on the meeting agenda. That framing is the right one. If the leadership team's primary job is making decisions, then decisions deserve their own process, cadence, and discipline. Most teams treat decisions as a side effect of meetings instead of the point of meetings.
Two principles separate good decision-making teams from stuck ones.
The first is the 80 percent rule. Most decisions don't need to be made with 99 percent confidence. They need to be 80 percent confident, which is reachable in a reasonable amount of time and lets you make many decisions without spending months on each one. Some decisions deserve higher confidence: irreversible decisions, decisions with regulatory or fiduciary stakes, decisions that are hard to walk back. Most decisions don't fall in that bucket. A 50 percent threshold is too low for most calls. A 99 percent threshold is too high. 80 percent is the sweet spot for the bulk of what your team decides.
The second is the cost of being slow. Slow decisions cost twice. They cost the company once on the decision itself, because the impact of any decision degrades the longer you wait. The window for a pricing change closes. The candidate accepts another offer. The competitor moves. They cost the company a second time in the backlog, because every week you spend on one decision is a week you're not spending on the next ten. Senior teams that can make good decisions quickly compound their advantage. Senior teams that grind on every call accumulate a queue of un-made decisions that drags on the whole company.
This isn't just theory. Senior team effectiveness research from Harvard Business Review, MIT Sloan, and others consistently shows that clarifying roles, processes, and decision authority is among the highest-leverage interventions a leadership team can make. The improvements aren't from better people. They're from better clarity on who does what.
Diagnostic: Where Your Team's Decision Rights Break Down
Five questions to test whether The Decision Gap is showing up on your team.
Can you name the person with Make rights on each of your team's five most important recurring decisions? Try it right now. Write down the five most important recurring decisions your leadership team handles, like quarterly priorities, hiring above a certain level, customer escalations, pricing exceptions, or major vendor selection. Next to each, write the name of the person with Make rights. If you can't name them quickly or if the answer is "we discuss it as a team," you have a gap. Discussing as a team isn't a decision-making process. It's a conversation.
When was the last time your leadership team had the same conversation about the same issue in three consecutive meetings without resolving it? If you can think of one easily, you're probably watching Violent Agreement in real time. The team is aligned, but no one owns the call. Map the decision against the framework and notice where the Make rights aren’t assigned.
In the last 30 days, how many decisions did your team escalate to you that didn't actually need you in the Make seat? Count them. If it's more than two or three, you have a bottleneck. Some of those decisions probably needed you to Approve, not Make. Some didn't need you at all. The escalation pattern is the gap showing up at scale.
How often do two of your direct reports make conflicting decisions in their respective domains? If the answer is more than rarely, you have Decision Sprawl. Either there's no Approve right defined for cross-functional calls, or the people with Make rights aren't coordinating their inputs. Both are gap problems.
On your last major team decision, who provided Input, who Collaborated, who Made the call, who had to Approve, and who got Informed? If you can't answer all five for a recent decision, the framework wasn't applied. The gap is wherever your answer is "I'm not sure."
Where To Start: Your First Decision-Making Rights Chart
Don't try to map every decision your company makes. Start with the recurring ones that cause the most friction.
Pick three to five decisions that come up regularly and currently feel slow, contentious, or routinely escalated to you. Common candidates are hiring above a certain level, pricing exceptions, customer escalations, marketing campaign approvals, vendor selection above a threshold, and project go/no-go decisions. Write each one across the top of a whiteboard or a large sheet of paper.
Down the side, list the five stages: Input, Collaborate, Make, Approve, Inform.
Now fill in names. For each decision, name who plays each role. This is the simplest version of a decision-making rights chart. You can do it on post-it notes in 30 minutes. The conversation while you fill it in is more valuable than the chart itself, because it surfaces every assumption your team has been carrying about who decides what.
When you have the basic chart, sophisticate it. For Input rights, specify the form (written brief, verbal in a meeting, email response), the timeframe (24 hours, by Friday, before the next staff meeting), and the channel (Slack, email, in person). Same for Inform rights. "Customer success will be informed via the weekly cross-functional update within five business days of any pricing change." That kind of specificity prevents 80 percent of the breakdown patterns I see in coaching engagements.
Expect pushback when you propose this. The most common objection is "this is too complicated." My response: if it feels too complicated, this probably isn't a decision that needs defined rights. The framework is for two kinds of decisions. The first is complicated decisions where you need to make sure the right people are involved in the right way. The second is frequent recurring decisions that need to be made quickly and decisively. Decisions that don't fit either bucket can usually be handled by one person making the call without ceremony.
Build the chart. Use it for two weeks. Adjust it. You'll know you've closed the gap when your team starts having decision conversations instead of decision discussions.
Questions for You and Your Team
Use these three questions to test where The Decision Gap might be showing up on your team. Specific answers reveal more than general ones, so try to anchor each question to a real decision your team has handled in the last quarter.
Of the last five significant decisions your leadership team made, can you name who held the Make rights on each? If you have to pause or guess on more than one, that's the gap showing up. Not in the decisions themselves. In the clarity around who owned them.
When you think about the decisions that currently come to you most often, how many of them genuinely need you in the Make seat versus needing you in Approve or Inform? The answer is often that more than half can move out of Make. The exercise itself is the start of closing the gap.
What is one recurring decision your team has been stuck on for more than a month that you could map against the framework this week? Pick one. Map it. Watch what shifts when rights become explicit rather than implicit.
The goal isn't to have perfect answers. It's to surface whether The Decision Gap might be affecting your team.
Take the Next Step
Most leadership teams don't lack talent. They lack clarity on who decides what. The Leadership Team Assessment gives you a structured read on your team's biggest gaps, including decision-making, role clarity, and accountability.
Take the Leadership Team Assessment
Or if you'd rather talk through where the gap is showing up on your team, book a call.
The Exit Planning Book for Founder-CEOs
Why do 75% of founders regret their exit within a year—even when they hit their number? Because most exit planning ignores what actually matters: personal readiness, life after the transaction, and building a business that sells on your terms.
SPRINGBOARD: A Founder's Guide to Selling Your Company With Purpose, Clarity, and a Vision for What's Next provides a comprehensive framework for planning exits that serve your life goals, not just your financial targets. It covers the four phases most founders miss: preparing yourself, preparing your business, executing the transaction, and navigating what comes next.
The first three chapters are available now.
About the Author
Bruce Eckfeldt is a strategic business coach and exit planning advisor who helps founder-CEOs of growth-stage companies scale systematically and exit successfully. A former Inc. 500 CEO who built and sold his own company, he brings real-world operational experience to strategic planning and leadership development. He's a certified ScalingUp and 3HAG/Metronomics coach, Certified Exit Planning Advisor (CEPA), an Inc. Magazine contributor, and host of the "From Angel to Exit" podcast. Bruce works with growth companies in complex industries, guiding leadership teams through growth challenges and exit preparation. Reach him at bruce@eckfeldt.com with any questions or if you want more information or to book a call with him.
