Decision Rights Before Management Layers
You Hired a Manager. Why Are You Still Making Every Decision?#
Three months after hiring your head of sales, you're still the one approving the discount. Still the one killing the deal that was never going to close. Still the one your team calls before they say yes to anything.
The hire was good. The person is capable. And you are more in the weeds than before you hired them.
What You Think Is Broken#
The assumption most founders make at this point is that they hired the wrong person. Or that they need to hire someone more senior. Or that the team isn't ready to operate without them.
So they start looking for a better manager. Someone who won't need so much input. Someone who will just figure it out.
That search usually fails. Not because the right person doesn't exist, but because the problem was never about the person.
What Is Actually Broken#
You delegated work. You did not delegate decisions.
You told your head of sales to own the pipeline. You told your team lead to manage their team. Those instructions sound like authority. They are not authority. They are a to-do list.
When your manager can't approve a discount, they ask you.
When they can't kill a deal, they ask you.
When they can't spend money or change a process or say no to a customer, they ask you.
Every escalation that lands back on your desk is not a failure of the person. It is a missing decision rule. Nobody knows what they can make final without you, so they default to asking. And you default to answering. The bottleneck doesn't disappear when you add a layer. It just takes one extra step to reach you.
What to Do Before You Restructure#
Do not draw an org chart. Do not promote anyone. Do not hire another manager yet.
First, list the ten decisions that come back to you most often. Be specific. Not "sales stuff" or "hiring." The exact recurring decisions that your team escalates to you every week.
For each one, write a single owner and a rule that makes it final.
Not "the head of sales can handle discounts." That is still vague enough to create ambiguity.
Write it like this: "Head of sales approves discounts up to 15% on deals over $50K. Final. No founder sign-off needed. On deals under $50K, any rep can approve up to 10%."
When the rule is specific, your manager knows exactly where their authority ends. They stop asking not because they got more confident, but because the answer to "can I do this" is already written down.
Escalation becomes a choice, not a reflex.
The Pattern We See Across Scaling Companies#
The clearest signal that an org isn't maturing is repeated escalation back to the founder. Not because the team is weak. Because nobody clarified ownership before the structure was built.
A head of sales who can't say yes to a contract term is not a head of sales. They are a recommendation engine that routes everything back to you. The title changed. The process did not.
This is why adding management layers often makes companies slower, not faster. Structure without ownership is overhead. You now have more people involved in the same decision, and the decision still ends up on your desk.
Assign Ownership Before You Build Anything Else#
Map your recurring decisions. Name one owner per decision. Write the rule that makes it final.
Do that before you restructure. Before you promote. Before you hire.
Once the decision rights are clear, the org chart becomes obvious. The right structure follows the actual work. It does not create the work.
You do not have a delegation problem. You have an ownership problem. Solve that first, and the management layers you build next will actually hold weight.
If you are at the point where your structure is in place but the work still routes back to you, that is exactly what Nexdation helps you untangle: which decisions are actually delegated, which ones are just labeled that way, and how to fix the difference before you scale further.