Decision Rights: Why Your Team Can’t Move Without You

Here is a number that should bother every founder running a $5M to $20M company. At a typical large firm, McKinsey estimates that 58 percent of the time managers spend making decisions is used ineffectively, which works out to more than 530,000 lost working days and roughly $250 million in wasted labor a year. In a smaller company that waste never shows up as a clean line item. You feel it in your calendar instead, in the fourteen Slack messages that all start with “quick question,” in the deal that stalled for a week because the person closest to it was waiting for you to bless a discount you would have approved in four seconds.

The problem is almost never the decisions themselves. It is that nobody in your company has ever written down the decision rights: who actually gets to decide what, and how much room they have to decide it, without routing back through you first. Most founder-led companies run for years with zero explicit answer to that question. The default answer, the one everyone quietly operates under, is “ask the founder.” That default is the bottleneck. And you built it.

I have sat across the table from a lot of owners who describe themselves as buried, then in the same breath describe a team they do not trust to make a call. Those two statements are the same statement. The team is not making calls because you never told them which calls are theirs to make.

What decision rights actually are

A decision right is a simple thing: it is a documented answer to “who decides this, and within what boundaries.” Not who does the work. Not who has an opinion. Who decides.

The reason this gets muddy is that in a growing company three roles get collapsed into one person, usually you. There is the person who does the work. There is the person with useful input. And there is the person who chooses. When all three live in the founder’s chair, every decision becomes a meeting with yourself, and the whole company waits on the length of your day.

Bain built an entire framework around pulling those roles apart. It is called RAPID, and it was popularized in the 2006 Harvard Business Review article “Who Has the D?” by Paul Rogers and Marcia Blenko. RAPID separates five roles on any decision: Recommend, Agree, Perform, Input, and Decide. The whole point of the tool is that there is exactly one Decider, veto rights (Agree) are explicit and narrow, and the people who merely have Input are clearly told that input is all they have. You do not need the full acronym to run a 30-person company. You need the underlying discipline: name the single decider for each recurring decision, and stop being that person for 80 percent of them.

Inside a Business Operating System, this discipline lives in the Accountability Chart. Each seat owns a set of roles, and owning a role means owning the decisions inside it, not just the tasks. When I set this up for clients, the tool we operationalize it in is Ninety.io, because it keeps the Accountability Chart, the seat, and the person’s actual measurables in one place instead of in a slide nobody opens. The chart is where decision rights stop being a vague promise (“I trust my ops lead”) and become a documented fact (“the ops lead owns all vendor decisions under $10K, full stop”).

Why “just delegate more” never fixes it

Every founder has been told to delegate. Most have tried, gotten burned, and pulled the authority back. That is not a discipline failure. It is a design failure. Delegation without a defined boundary is just handing someone a task and then hovering, which teaches them to escalate everything to avoid getting it wrong. Delegating the decision, with a clear boundary, is the opposite. It tells someone: inside this box, you decide, and I will back your call even when I would have chosen differently.

The research on this is not subtle. Gallup studied 143 CEOs from the Inc. 500 list of fastest-growing private companies and found that only about one in four employer-founders have high “Delegator” talent. The ones who did generated 33 percent more revenue than the low-delegator group, $8 million versus $6 million, and posted a three-year growth rate of 1,751 percent, 112 percentage points higher than the founders who kept a tighter grip. Delegation of authority is not a soft skill. It is one of the sharpest lines between the companies that scale and the ones that plateau at the founder’s personal bandwidth.

The founders who never get there almost always share one habit. They confuse being needed with being valuable. When every decision requires you, you feel important. You also feel exhausted, and your best people feel like expensive order-takers, which is exactly why they leave.

Sorting decisions before you assign them

Not every decision should leave your chair, and pretending otherwise is how founders overcorrect and blow something up. Before you hand authority down, sort your recurring decisions into three buckets.

The first bucket is reversible and low-stakes. Refund a customer under $500. Approve a same-day schedule swap. Pick the vendor for a routine reorder. These should never touch you. If a wrong call costs a few hundred dollars and can be undone by Friday, the cost of you being the gate is far higher than the cost of an occasional miss. Push these all the way down and stop reading the emails.

The second bucket is reversible but higher-stakes, or irreversible but small. A new hire below the leadership team. A pricing exception on a mid-size deal. These get a named decider on your leadership team with a written boundary, and you get told after, not asked before.

The third bucket is genuinely yours. Anything that changes the company’s direction, spends serious capital, or cannot be walked back: a key leadership hire, a major client you might fire, a pivot in your market. Keep these. The goal was never to abdicate. It was to stop drowning bucket-one and bucket-two decisions in the same chair that has to protect bucket three.

Most founders I work with discover that 70 to 80 percent of what crosses their desk is bucket one or two, sitting there only because no one was ever told it was theirs.

What this looked like at a $12M contractor

A design-build contractor I worked with, about $12M in revenue and 45 people, had a founder who could not take a vacation without the jobs slowing down. Every change order over a few thousand dollars, every subcontractor swap, every “the client wants to move the kitchen island” moment routed to his cell phone. His project managers were capable people who had been trained, by two years of him overruling them, to ask first and decide never.

We did not run a leadership retreat about trust. We opened the Accountability Chart, took the project manager seat, and wrote the actual decision boundaries into it. Change orders under $15,000: the PM decides, no call. Subcontractor performance issues: the PM decides, tells the ops lead after. Anything that moved the completion date more than a week or the margin more than three points: escalate. Then he did the hard part, which was holding his mouth shut for a quarter when a PM made a call he would have made differently.

Two things happened. Field decisions that used to sit for a day got made in an hour, and his phone stopped buzzing on Saturdays. The PMs, given real authority, got visibly better inside a quarter, because you cannot develop judgment you are never allowed to use. That is the part founders miss. Withholding decision rights does not protect quality. It prevents your people from ever building the judgment that produces quality.

Signs you are the decision bottleneck

You do not need a diagnostic tool to know if this is you. A few honest tells:

• Your team texts you routine questions on evenings and weekends, and you answer, because it is faster than explaining.
• Work visibly slows when you are out for more than two days.
• You catch yourself reversing your managers’ calls in front of their own reports.
• Nobody on your team can tell you, without hedging, which decisions are theirs to make alone.
• You are working 55-plus hours and most of it is answering, approving, and unblocking rather than thinking.

If three of those land, the constraint on your company right now is not the market or the talent. It is that the decisions live in one chair.

Installing decision rights this quarter

You do not fix this in a weekend, and you do not fix it with a memo that says “you are all empowered now.” Start narrow and concrete. Pick the five decisions that interrupt you most this week and write, for each, a single sentence: who decides, and up to what boundary. Put those sentences somewhere the team actually sees them, ideally attached to the seat on your Accountability Chart, not buried in a doc. Announce the boundaries out loud in your next leadership meeting so there is no ambiguity about who owns what. Then defend the handoff. The whole thing dies the first time you override a decision that was inside someone’s boundary, because everyone learns the authority was never real.

If you want the deeper foundation under this, start with the Business Operating System pillar, which frames how the pieces fit, then read Delegate and Elevate for the tool that shows where your week actually goes and why you keep becoming the bottleneck. If the real issue is that your team stays quiet about what is broken, the CEO accountability gap is the companion problem to this one, and the accountability chart is where you put decision rights in writing. All of it connects back to the work of becoming the kind of leader a growing company needs.

Decision rights are not a control you give up. They are a system you install so the company can move at the speed of your team instead of the length of your day. The founders who scale past their own capacity are not the ones who make the most decisions. They are the ones who decided, on purpose, which decisions were never theirs to make.