How to Find the One Bottleneck That's Capping Your Growth
Most scaling founders know something is broken. Very few can name exactly what.
Last week I wrote about the scaling wall. The pattern where a company hits product-market fit, doubles the team, and then watches operational overhead eat everything.
The response surprised me. Not because people disagreed. Because the most common reply was some version of: “OK, I get it. But where do I actually start?”
Fair question. Naming the problem is step one. But if you can’t point to the specific constraint that’s capping your team, you’re just agreeing with a diagnosis you can’t act on.
So here’s the diagnostic I run in the first two hours of every engagement. You can do it yourself, Monday morning, with a whiteboard and your leadership team.
The Three-Question Diagnostic
I’ve tried complicated frameworks. Weighted matrices. Priority scoring systems. None of them work as well as three direct questions.
Question 1: Where is your most expensive person spending their cheapest time?
McKinsey research found that managers spend just 23% of their time on strategy. Another 31% goes to individual-contributor work. Nearly a full day each week disappears into administrative tasks.
Now think about your CTO. Your COO. Your head of ops. What are they actually doing all day?
Not what their job description says. What they’re actually doing.
In my experience, the answer usually involves some combination of: manually pulling reports, coordinating across tools that don’t talk to each other, onboarding new hires into processes that only exist in someone’s head, and putting out fires that started because nobody automated the thing that catches them early.
That’s your CHF 180k-a-year person doing CHF 60k-a-year work. Not because they’re bad at their job. Because the systems around them force it.
Question 2: What would break if one person went on vacation for two weeks?
This is the fastest way to find single points of failure.
If the answer is “nothing, we’d be fine,” congratulations. You don’t have the problem I’m describing. But in most 15-35 person companies, at least one critical process lives entirely in one person’s head. The weekly client report. The deployment pipeline. The invoice reconciliation.
That’s not a people problem. That’s a systems problem wearing a people costume. And it tells you exactly where your fragility sits.
Question 3: What are you doing manually that you’ve been meaning to automate for six months?
Every scaling founder has a list. The spreadsheet that should be a dashboard. The email sequence that should be triggered automatically. The data entry that someone does every Friday afternoon.
The reason it hasn’t been automated isn’t that it’s technically hard. It’s that nobody has the bandwidth to fix it, because everyone’s bandwidth is consumed by the manual work itself.
That’s the loop. And breaking it is usually simpler than you’d expect.
How to Read the Answers
Run these three questions with your leadership team. Write down every answer. You’ll probably end up with 8-12 items across all three.
Now sort them by one criterion only: which one costs the most senior attention per week?
Not the most annoying. Not the most technically interesting. The one that eats the most hours from the people whose time matters most.
That’s your bottleneck. That’s where you start.
Not three things. Not a roadmap. One constraint.
Why One, Not Three
The instinct is to fix everything at once. Build a “digital transformation roadmap.” Hire a consultant to map all the processes. Spend two months planning.
I’ve watched this play out dozens of times. The roadmap gets built. It sits in a slide deck. Six months later, the same fires are burning.
One bottleneck, fixed completely, does something a roadmap never does: it creates belief.
When the team sees their Friday afternoon data entry disappear, or the CTO gets four hours back because the deployment pipeline doesn’t need hand-holding anymore, something shifts. The next fix becomes easier to justify. Not because of ROI calculations. Because everyone saw it work.
The Mercury Startup Economics Report 2025 found that 69% of companies with significant AI adoption increased their use of external specialists in the past year. Not because they couldn’t build internally. Because they learned that fixing the first constraint fast creates momentum that internal teams can then carry forward.
What Happens After the First Fix
This is the part that matters more than the diagnostic.
Once the bottleneck is solved, the question becomes: can your team solve the next one without outside help?
The best engagements I’ve run follow a pattern:
→ Week 1: Fix the constraint. Working software, running in your environment.
→ Week 3: Hand over. Train the team to extend and maintain what was built.
→ Month 3: Advisory. Available for strategic questions, not daily operations.
→ Month 6+: Independence. Your team picks up the next bottleneck themselves.
Every other option on the market has a structural incentive to keep you dependent. Agencies bill monthly. Consultancies extend engagements. Internal hires become permanent cost.
This model has a structural incentive to leave. And that’s exactly the point.
Try It Monday
Block 90 minutes with your co-founder or leadership team. Ask the three questions. Write down everything. Sort by senior attention cost.
You’ll walk out with one clear constraint. Not a strategy deck. Not a hiring plan. One thing you can fix, probably faster than you think.
The scaling wall is real. But it’s not abstract. It’s specific. And specific problems have specific solutions.
Start there.
Damian Nomura helps scaling startups close the capability gap between where they are and where they need to go. His Build Week format takes the biggest operational bottleneck and turns it into working software in 5 days. Simple. Clear. Applicable.