The office clock in your Makati headquarters strikes 6:00 PM. You are hunched over your desk, reviewing a stack of “urgent” requests. Your Marketing Manager is waiting for you to approve a single Facebook ad headline. Your Operations Lead is waiting for you to sign off on a small equipment repair. Your Sales Head is waiting for your “final look” at a standard client proposal.
You feel like a hero. You are the engine that keeps this company running. But as you look at your team, you feel a quiet frustration: Why is everyone so slow? Why can’t they just get things done?
If you’ve been searching for leadership training for startup founders or looking into how to build a corporate structure for a small business, you likely think your problem is “efficiency.” You think you need faster people.
The truth is much harder to swallow: Your managers aren’t slow. They are perfectly capable. They just don’t decide. And the reason they don’t decide is because you have unintentionally built a culture where “the founder’s word” is the only thing that matters.
To scale, you must move from being a centralized bottleneck to a leader who delegates accountability.
The Story of Paulo and the “Approval Trap”
Paulo founded a successful logistics startup. He was a brilliant problem solver. In the early days, his speed was his competitive advantage. If a courier was lost, Paulo found them. If a client was angry, Paulo called them.
As the company grew to forty employees, Paulo hired experienced managers. But something strange happened. These high-level hires—people with impressive resumes—seemed to lose their edge the moment they started working for him. They became “order takers.”
Paulo’s search for business operations consulting for founders led him to a realization: He was suffering from the Approval Trap. Because Paulo had a habit of “tweaking” every decision his managers made, his managers stopped making them. They realized that making a choice was a waste of energy because Paulo would eventually change it anyway.
They weren’t slow; they were waiting. They were waiting for Paulo to give them the answer so they wouldn’t have to risk being “wrong.”
Lesson 1: Clarity of Direction (The “Success Criteria” Shift)
Managers don’t decide because they don’t know what “right” looks like in your eyes. Most founders provide vague goals and specific instructions. To scale, you must do the opposite: Provide specific goals and vague instructions.
- The Bottleneck Way: “Make the new website look premium.” (Subjective. They will wait for you to “feel” if it’s premium).
- The CEO Way: “The new website is successful if it reduces our bounce rate by 10% and follows the minimalist brand guidelines in our handbook.” (Objective. They can decide based on data).
When you provide Clarity of Direction, you give your team a yardstick. They no longer need to ask for your opinion because the goal is the judge, not you.
Lesson 2: Radical Delegation (Handing Over the “Baton”)
Delegation is not a task; it is a transfer of authority. If you tell a manager to “run a project” but then jump into their Slack threads to correct minor details, you haven’t delegated. You’ve just hired a very expensive personal assistant.
To move to a corporate structure, you must give the “baton” and stay on the sidelines. This means accepting the 80% Rule: If a manager can do a task 80% as well as you can, let them do it. The 20% “loss” in quality is the price you pay for the 100% gain in your own time.
Lesson 3: Not Being a Bottleneck Owner (The “Wait and See” Strategy)
The fastest way to train your managers to decide is to stop being so helpful. Paulo implemented a “No-Answer Monday.” When a manager came to him with a problem, he wasn’t allowed to solve it. He could only ask:
- “What does the data say?”
- “What is your recommendation?”
- “What is the risk of doing nothing?”
By refusing to be the “Answer Man,” Paulo forced his managers to exercise their decision-making muscles. He stopped being the owner of every problem and became the Architect of Accountability.
Lesson 4: Designing Systems, Not Solving Fires
If you are constantly putting out fires, you are a firefighter. Firefighters don’t have time to build skyscrapers. To scale your startup, you must move from “firefighting” to System Design.
Every time a manager asks you for a decision, ask yourself: “What system is missing that would have allowed them to decide this without me?”
- Is it a lack of a clear budget?
- Is it a missing SOP (Standard Operating Procedure)?
- Is it a fear of failure?
Fix the system, not the fire. When you build a system of accountability, you aren’t just offloading work; you are building a company that can thrive while you sleep.
The Goal: The “30-Day Test”
How do you know if you have successfully stopped being a bottleneck? Take the 30-Day Test. If you were to leave your office for 30 days, would your managers keep the company on course, or would they sit in the lobby waiting for your return?
A company that can’t decide without its founder isn’t a business; it’s a very stressful hobby. True scaling happens when your team stops asking, “What does the boss want?” and starts asking, “What does the goal require?”
If you stopped answering “quick questions” for the next 48 hours, which of your managers would step up to lead, and which would wait in silence?
Relevant Articles from JordanImutan.com
- The Founder’s Ego: Your Biggest Scaling Roadblock: Why the need to feel “essential” is preventing your managers from growing.
- How to Write a ‘Definition of Success’: A simple tool to help your team make decisions without your constant input.
- The 5 Levels of Delegation: Identifying exactly how much authority you are actually giving your team.
- Building a Culture of Accountability: Moving away from a “blame” mindset to a “results” mindset in your startup.
- The CEO’s New Job Description: Why your role must shift from “Chief Problem Solver” to “Chief System Designer.”
Too many companies have untrained leaders that fail. 