You’re the Reason Nothing Moves Fast Anymore
Your team isn’t slow.
Your processes aren’t broken.
Your market didn’t suddenly get harder.
You became the constraint. And you don’t even see it.
Let me show you how this happened:
Six months ago, you could make decisions in real-time. Strategy sessions were fast. Projects launched quickly.
Now? Every initiative takes three times longer. Your team seems less decisive. Momentum feels like something you used to have.
You’re blaming culture. Or hiring. Or “people just don’t execute like they used to.”
Wrong.
You changed. And everything downstream adjusted to you.
Here’s the pattern nobody tells you about:
As your companies grew, you stayed involved in everything. Because that’s what got you here—being the person who sees around corners, catches mistakes, makes the tough calls.
It worked. Until it didn’t.
Now you’re in 40 meetings a week. Every decision loops back to you. Your calendar is the master schedule for three companies.
And you still think you’re “staying close to the business.”
You’re not. You’re blocking the business.
The mechanisms are subtle. You don’t see them happening.
Mechanism 1: You’re still answering questions you shouldn’t be answering.
Someone asks your opinion on something tactical. You give it. Feels helpful.
What you just taught them: “Don’t decide this on your own. Check with the founder first.”
Next week, they ask about something similar. Then their peer asks. Then someone else.
You’ve now accidentally trained your entire team to route decisions through you.
Not because you demanded it. Because you kept answering.
Mechanism 2: You’re still “just checking” on things.
You drop into a meeting “just to listen.” You review a deck “just to make sure it’s tight.” You ask for an update “just to stay informed.”
Feels like responsible leadership.
What actually happens: that meeting now takes twice as long because people are presenting to you, not working together. That deck gets redone three times to match your aesthetic. That update becomes a recurring obligation.
Your presence changes behavior. Every time.
And you don’t notice because everyone tells you it’s helpful.
Mechanism 3: You’re undermining decisions after they’re made.
Your team makes a call. You agree with it. Everyone moves forward.
Three days later, you mention “we should maybe reconsider X” in a Slack message.
You think you’re being thoughtful. Keeping things flexible.
What you just did: signaled that decisions aren’t final until you stop second-guessing them.
So now your team waits an extra week after deciding anything—just to make sure you won’t change your mind.
You’ve added a hidden approval layer that doesn’t officially exist.
Mechanism 4: You’re solving problems people should be solving themselves.
Someone hits a roadblock. You jump in. Fix it. Move on.
Feels productive. Feels like leadership.
What you just taught them: “When something’s hard, wait for the founder to solve it.”
Next time they hit a roadblock, they don’t try as hard. Because they’ve learned you’ll handle it.
You’re accidentally training dependency instead of capability.
Mechanism 5: You keep saying “let me think about it.”
Someone brings you a decision that needs an answer. You say “let me think about it” because you want to be thoughtful.
They leave. You forget. They follow up a week later.
You think you’re being careful. Making sure you get it right.
What actually happened: you just added 7 days to a decision that should have taken 7 minutes.
And because you do this on 15 decisions a week, you’ve added months to your company’s execution timeline.
Not intentionally. Just by being “thoughtful.”
Here’s what’s insidious about all of this:
Every single behavior feels like good leadership in the moment.
Being available. Staying involved. Solving problems. Being thoughtful.
These aren’t bad instincts. They’re just scaling badly.
What worked when you had 8 people doesn’t work when you have 40 people across three entities.
But you’re still operating like you have 8 people.
And everyone else adjusted to you. So you don’t feel the friction. They do.
You want to know how bad it is?
Run this test: count how many decisions touched your calendar this week that you weren’t the ultimate decision-maker on.
Meetings where you were “giving input.” Reviews where you were “just checking.” Updates where you were “staying informed.”
Now imagine none of those involved you. What would have happened?
If your honest answer is “probably the same outcome, just faster”—congratulations. You’re the bottleneck.
The hard part is this: your team won’t tell you.
They can’t. Because telling the founder “you’re slowing us down” is career limiting.
So they work around you. They pad timelines. They wait for your schedule. They second-guess decisions because they’ve learned you might change your mind.
And you interpret all of this as “the team needs more direction.”
So you get more involved. Which makes it worse.
You’re in a feedback loop. And you’re the only one who can break it.
I know what you’re thinking: “But if I’m not involved, quality drops.”
Maybe. For a month.
Then your team learns you’re not going to swoop in and fix things. So they start fixing things themselves.
And yeah, they’ll make some mistakes. Recoverable ones. The kind you made when you were building your judgment.
But here’s the choice: short-term quality dips while people learn, or permanent growth ceiling because everything requires you.
Most founders choose the ceiling. Because it feels safer.
It’s not. It’s just slower to kill you.
The pattern I see constantly:
Founders who scaled to $10M, $20M, $50M—then hit a wall.
Not because the market changed. Not because they hired wrong.
Because they never learned to get out of the way.
They’re still operating like a 10-person startup. Making every call. Reviewing every decision. Being the person who “just needs to take a quick look.”
And their companies can’t grow past what one person can personally oversee.
The company didn’t hit a ceiling. The founder did.
Here’s what’s probably happening right now:
You have talented people who’ve stopped proposing ambitious ideas. Because ambitious ideas need fast decisions, and fast decisions require you, and you’re booked for three weeks.
You have projects that should take 4 weeks taking 12. Because they’re waiting for your review, your input, your “quick thoughts,” your availability.
You have people who’ve learned to work around you instead of with you. Because working with you means delay.
None of this is malicious. It’s just structural.
You became the architecture of slowness. And architecture is invisible to the person who built it.
The fix isn’t “delegate more” or “be less involved.”
The fix is recognizing which behaviors scale and which don’t.
Answering every question? Doesn’t scale.
“Just checking” on things? Doesn’t scale.
Second-guessing decisions? Doesn’t scale.
Solving every hard problem? Doesn’t scale.
“Let me think about it” on tactical decisions? Doesn’t scale.
These worked when you were small. They’re killing you now.
You don’t need to stop leading.
You need to stop doing the things that feel like leading but are actually just controlling.
There’s a difference. And your growth depends on learning it.
The companies you built can move faster than they are.
But not while they’re moving at your speed.
