How do I know if I'm the bottleneck in my company?

Ask one question: if you disappeared for two weeks, would your business grow, stall, or die? If it would die, you're the bottleneck. If it would stall, you're load-bearing in places you probably shouldn't be. If it would grow, the constraint is somewhere else. Most founders land on "die" or "stall" — and most of them have a different explanation for why things are slow.

The five everyday signs

You don't need the thought experiment if you recognize these:

1. A lot of thinking, not a lot of deciding. Your calendar is full of considering. The decisions themselves keep sliding.
2. The thing you said you'd resolve last month still isn't resolved. And you have a good reason. You had a good reason last month too.
3. Smart, busy, same place as six months ago. Activity is high. Position hasn't moved.
4. Same problem, different explanation each quarter. Q1 it was marketing. Q2 it was the team. Q3 it's focus. The problem underneath hasn't changed.
5. Your team is moving but nothing is landing. Sprints end, decisions pile up, and your best people are waiting on you for everything.

Any two of these, sustained for a quarter, and the two-week test will not go well.

Why you can't see it from inside

Here's the uncomfortable part: being the bottleneck doesn't feel like being the bottleneck. It feels like being thorough. Careful. Professional. The overpreparation, the hedging, the "let me think about it" — from inside, every one of those reads as diligence. Ask a founder "are you avoiding a decision?" and they'll sincerely say no.

That sincerity is the trap. The founders who stay stuck longest are the ones with the most convincing explanation for why they're stuck — an explanation that has quietly been arranged to keep one particular decision off the table. I call this being confidently wrong: you know something's off, you've explained it to yourself in a way that's comfortable, and the explanation hasn't yet hit the moment where it stops working.

Minh at Algomate is a clean example. Ten to fifteen hours a week of outreach, three real conversations in six months, and a confident diagnosis: execution. The actual pattern was a niche decision he hadn't made, so every message hedged. He said it himself afterwards: what he thought was the problem "is like just the branch of the tree, not like the root core problem."

What usually causes it

In almost every case I've diagnosed, the chain looks the same. There's a decision the founder hasn't made — a niche, a hire, a product line to kill, a number to look at. Everything downstream of an unmade decision hedges: the team waits, the messaging blurs, the founder compensates with personal effort. The company then scales around the unmade decision, which is expensive, and the founder reads the expense as an execution problem or a people problem.

More effort makes this worse. So does hiring — a common move after a raise is to add headcount before knowing what problem the hire is supposed to solve, which converts one waiting-on-the-founder queue into five.

What not to do

Don't reorganize, hire, or change strategy based on your current explanation of the problem. Your explanation is the thing in question. Testing it costs 90 minutes; acting on it wrong costs a quarter.

The decision rule

Run the two-week test honestly. "Grow" — go work on whatever your real constraint is; it isn't you. "Stall" — write down the three things that would stall first; those are the decisions and handoffs to fix, and you can likely do it yourself. "Die" — the bottleneck is you. That's fixable, and it's precisely the case a Founder Bottleneck Diagnostic is built for: someone outside the system pulls the facts, finds the unmade decision, and names it so you can act.

---

More on the person behind it: About Trung Nguyen · Related: What happens during a Founder Bottleneck Diagnostic? · Why is everyone still waiting on me for everything? · Why is nothing moving in my startup?