Why do employees wait for the owner to decide?
People wait for the owner because nobody told them which decisions are theirs. Without a written limit, asking is the safe move, so every decision lands back on the owner. That's learned helplessness, usually taught without anyone meaning to. Give each recurring decision one owner and one limit, and the waiting stops.
Last updated:
What surprises owners most
How much they're needed everywhere. That's what opens everyone's eyes. Owners don't realize people are waiting for them.
It turns out everyone is waiting for the owner, and the owner had no idea. And the owner is furious that people don't work without them.
What it looks like
For one week, count the decisions that wait on you and sort them by department. Every row below is an example.
| Department | What waits on the owner |
|---|---|
| People and admin | Time off, a new hire's start date |
| Marketing and sales | A discount, a quote on non-standard terms |
| Finance | A vendor payment, a write-off |
| Operations | Overtime, a schedule change |
| Customer success | A refund, a call back to an unhappy customer |
Start with the department that has the longest list. The 7-day decision log shows how to sort what you find.
Why it's learned
That's what I call learned helplessness. If you don't give people decision authority, if you don't delegate, they don't know where they can decide on their own and where they can't.
The owner never set up delegation the right way, so people just sit there, afraid to do something wrong.
A decision made alone and then reversed teaches the whole team to ask first. When people don't know which decisions are theirs, waiting is the safe choice.
Three questions every person should be able to answer
- Which decisions are mine?
- Up to what amount?
- What brings it back to the owner?
If someone can't answer all three for a decision, they'll wait on it.
How to write the limits
Take each recurring decision from your count. Give it one name, one number, the condition that sends it back to you, and what done right looks like. Written down, that's a decision authority matrix.
For example: refunds go to the client success lead, up to $500 per case. Above that, or a third refund from the same client, it comes to the owner. Your numbers will be different.
Put the limits where the team works. When someone brings you a decision inside their limit, hand it back with one word: yours.
What changes
People start deciding once the answer is written down and the owner stops overriding it. Exceptions come up once a week, in the weekly operations meeting, instead of all day.
In one engagement, $1.2M of $1.4M in overdue receivables was collected in three months once one person owned receivables.
Where this sits in SCOPE™
SCOPE™ by Efficiency Sprint maps where a company stands: Stabilize, Codify, Ownership, Pulse, Engine. A team that decides inside written limits is Ownership: people run it reliably.
It comes before AI for a reason. An agent needs the same limits a person does, and someone to bring the exception to. You always need to know who is responsible. And it can't be AI.
Find out where your company stands
Efficiency Sprint makes companies operationally ready for AI. The operational AI readiness check takes about two minutes and shows where your company stands. More about how I work: About Luba.
Questions
Is learned helplessness at work the employee's fault?
No. It's a sensible response to unclear limits. When deciding alone can go wrong and asking never does, people ask. Write the limits down and the asking drops.
How do I know my team is waiting on me?
Spend one day out of the office and count what's waiting when you're back. Each item is a decision nobody knew they could make.
Will people make mistakes once they can decide?
Some, inside the limit. That's what the limit is for. A $300 mistake costs less than a week of everything waiting. If the same mistake repeats, rewrite the standard for that decision.
Is this the same as the owner bottleneck?
Same problem, two sides. The owner sees a bottleneck. The team sees no permission. Both close the same way: one owner and one limit per decision.