Why Everything Still Needs Your Sign-Off
The Weekly Fix
Real stories and lessons from the messy middle of scaling
Growth doesn’t usually stall because of one bad decision.
It slows because too many decisions still need your approval.
At first, it barely registers. A quick Slack message here and there or a pricing/costing check. A team member waiting for confirmation before moving something forward. Nothing dramatic, nothing that stands out, but over time, those pauses begin to stack up, and the business starts losing momentum in places that are hard to see but easy to feel. It is the old boiling frog analogy.
That’s when founders start thinking:
“Why does everything still seem to come back to me?”
If that feels familiar, you’re not leading badly, it’s just your decision structure hasn’t caught up with your growth.
The Hidden Cost of Constant Sign-Off
In the early stages, founder approval feels efficient. It feels right, safe even. You are closest to the customer, the product, and the risk. Making the final call keeps things moving, and for a while, that works. You have control, and it feels necessary because you believe the business runs best when you are on top of everything.
But growth changes the shape of the business. More people means more handoffs. More customers means more exceptions. More channels, categories, SKUs, suppliers, and moving parts create more moments where someone wants reassurance before acting.
Without clear decision ownership, everything flows in one direction and that is upward, back to you. No filter, no backstop, no guardrails, just a one-way constant flow straight to your desk.
Why Approval Loops Form
Most approval loops are not created intentionally. They form when delegation happens at the task level, but not at the decision level. Work gets done, but as soon as something changes, people are unclear what they are trusted to decide on their own.
That gap creates friction; a team member drafts the response but waits for approval before sending it. An ops lead identifies the issue but still escalates the fix. A commercial decision is 95 percent obvious, yet progress pauses because nobody is clear on where authority actually sits.
The business looks delegated on paper, you may even have nice neat SOPs and cheat sheets but when executed, in real world scenarios, it is still founder routed.
Why This Persists as Revenue Grows
This is especially common in founder-led product businesses between roughly $3M and $8M. Revenue is growing, the team is bigger, and the founder is trying to step into a more strategic role. But the internal system is still operating like a smaller business.
That creates a mismatch, the systems are holding but the decision making doesn’t grow organically like the rest of the business.
The founder wants space to think and focus on the next phase of growth, but the team still relies on constant access. Decision-making remains informal because it has always been founder-led. Escalation rules are vague, and knowledge is shared unevenly. So even capable people default to caution and send decisions upward.
Revenue doesn’t remove this pattern, it exposes it, and it starts compounding.
The Approval Loop Test
You do not need a full structure analysis to identify whether this is happening.
Start with one simple review. Look back over the past 48 hours and ask:
- Which decisions came to you that did not genuinely require founder input?
- Where did progress pause while someone waited for your sign-off?
- Which team members had enough context to decide, but still hesitated and escalated?
- What keeps returning to you even after you thought it had been delegated?
If the same categories show up repeatedly, that is not random.
It is an unintentional structural loop, created through the repeated unknown bad habits you have been fostering.
What the Loop Is Really Costing You
The obvious cost is speed. Work slows down when everything needs checking, this was ok in the beginning, but when you get to 10 x it stands out like a sore thumb. Execution gets delayed further, teams hesitate, projects stall and progress loses all momentum. Priorities become harder to move, staff become less motivated, all because the system is waiting on one person.
But the deeper cost is mental load, when every decision still routes through the founder, the business never fully leaves your head. Even when you are out of office, switched off for the evening, or trying to think strategically, part of your attention is still being held in reserve for approvals, exceptions, and course-corrections.
That is not sustainable scaling, it is controlled dependency, and it is wearing you down every day.
What Changes When Decision Ownership Is Clear
When approval loops are reduced, the business starts to feel different very quickly. The team moves faster because they know where authority sits. Execution improves because fewer tasks are left waiting in limbo. Escalations become more meaningful because they are reserved for decisions that genuinely need founder-level judgement.
The founder’s role changes too; you stop being the checkpoint for everything and start becoming the architect of how decisions are made. Instead of absorbing constant interruption, you are building the conditions for independent movement, you are now fostering good habits.
That is when growth starts to feel calmer, not because complexity disappears, but because it is no longer all landing in the same place.
The Practical Shift
Pick one recurring decision that still comes to you. For example, a customer issue, a pricing exception, or an operational fix that keeps getting escalated. Define who owns it. What a good decision looks like. And when escalation is actually required. Then let it run without stepping in immediately.
Watch what happens. Where it holds. Where it breaks. Where clarity is missing.
You do not need perfection to reduce dependency; you need confidence it works. And for that, you need proof that the system can move without constant founder confirmation.
Your Next Step
If everything still needs your sign-off, growth will continue to feel heavier than it should.
Not because your team is incapable. Not because you are failing. Because the structure is still routing decisions through you.
Pick one approval loop this week and map it properly.
If you are not sure where the biggest one sits, send me a message and we will pressure-test it together.
Fix the system, and the pressure drops.