Quick experiment. Think about the last five decisions that got stuck in your business. Not the big strategic ones. The everyday ones. Whether to refund that client. How to handle the scheduling conflict. Which vendor to use for the new project. Whether to approve the expense.
Now ask yourself: did those decisions get stuck because they were genuinely hard, or because nobody knew whose call it was to make?
In my experience, it's almost always the second thing. The decisions themselves are usually straightforward. What's missing is clarity about who owns them.
The invisible bottleneck
Every business has a decision-making structure, whether they designed one or not. In most small businesses, the default structure is simple: everything goes to the owner. Every question, every approval, every judgment call routes upward and sits there until the owner has time to deal with it.
This works when you're a team of three. It absolutely does not work when you're a team of ten or fifteen or twenty. At that scale, the owner becomes a human switchboard, spending their entire day answering questions and approving things instead of doing the work that only they can do.
The frustrating part is that most of those decisions don't actually need the owner. They need someone with enough context and authority to make a reasonable call. But because nobody ever explicitly said "you can make this call," everyone defaults to asking the boss.
RACI, minus the corporate nonsense
You may have heard of RACI. It stands for Responsible, Accountable, Consulted, Informed. It's a framework that big companies use to map out who does what for any given process or decision. And in its full corporate form, it's overkill for a small business. Nobody needs a color-coded matrix for a team of eight people.
But the core idea is gold. For any decision or task, there should be clear answers to four questions. Who does the work? Who owns the outcome? Who needs to weigh in before it's final? Who just needs to know what happened?
That's it. Four questions. You can answer them in a conversation, write them on a whiteboard, put them in a shared doc. The format doesn't matter. The clarity does.
Making it concrete
Let me give you an example. Say a client asks for a change to their project scope. In a business with no decision rights defined, here's what happens: the project manager says "let me check with the owner." The owner is in a meeting. The client waits. The owner gets out of the meeting, reads the message, asks for context, gets context, thinks about it, responds. Total elapsed time: maybe a day. Maybe two.
Now here's the same scenario with decision rights defined. The project manager knows that scope changes under $500 are their call. They know the pricing framework. They know that scope changes over $500 need the owner's sign-off, and that the turnaround for that approval is four hours. They respond to the client within the hour, either with an answer or with a clear timeline for when they'll have one.
Same decision. Same people. Completely different experience for the client and completely different load on the owner.
The decisions you should give away
Not every decision should be delegated, obviously. But most owners hold onto far more than they need to. Here's a rough framework for thinking about which decisions to keep and which to hand off.
Decisions you should keep: anything that could significantly damage the business if it goes wrong, anything involving large financial commitments, major client relationship decisions, hiring and firing, strategic direction. These are the decisions that justify your role as the owner.
Decisions you should define and delegate: recurring operational decisions (pricing within a range, scheduling, vendor selection within approved options, client communications for routine situations, expense approvals under a threshold). These are the decisions that eat your day without needing your judgment.
The gap between these two categories is where most owners are stuck. They're making $200 expense approvals and reviewing routine client emails because nobody was ever told "you can handle this."
How to write it down
The actual document can be ridiculously simple. A table with three columns: the decision, who owns it, and any boundaries or escalation triggers.
For example: "Client refunds up to $500. Owned by: Operations Manager. Boundary: refunds over $500 or repeat refund requests from the same client escalate to owner." That's one row. You might have twenty or thirty rows for a typical small business, covering the decisions that come up regularly.
The key word there is "regularly." You don't need to map out every possible decision. You need to map out the ones that happen often enough to cause a bottleneck. Start with whatever you were interrupted about most often in the last month. Those are your high-frequency decisions, and they're the ones that will give you the most time back when you clarify ownership.
Making it stick
Writing decision rights down is the easy part. Making them stick is harder, because it requires behavior change on both sides. You have to stop answering the questions that aren't yours anymore, and your team has to start making calls they've never made before.
Both sides will be uncomfortable at first. Your team will come to you with decisions they now own, out of habit or uncertainty. You need to redirect them, gently. "That's your call. What do you think the right move is?" Not dismissively, but clearly. You're training a new habit.
You, meanwhile, will feel the urge to weigh in on things that are no longer your decisions. You'll see something handled differently than you would have handled it and want to step in. Resist this unless the outcome is actually wrong. Different isn't wrong. Different is just different. And the person making the call needs the space to develop their own judgment.
Give it a month. The first week will be bumpy. By week three, it'll feel more natural. By the end of the month, you'll wonder why you were ever making those decisions yourself.
And if you're looking at this and thinking "I don't even know where to start," that's a good signal to step back and look at how decisions flow through your business as a whole. A flow check can help map that out and identify which decisions are worth defining first.