When the Bottleneck Isn't a Hiring Problem (And You Still Have to Fix Something)

A practical read on what to do when you've named the bottleneck, ruled out the hire, and now have to choose what to fix first without thrashing through three quarters of the wrong sequence.

Three weeks of this series have walked through a specific arc. Week 19 named the bottleneck. Week 20 separated the genuine hire problems from the workflow ones in disguise. Week 21 wrote down the artifact a hire would inherit if the hire was the right call.

This week is for the founders who finished those three weeks and concluded the hire isn't the next move.

If you're in that group, you're now in a harder question than the one the prior weeks closed. You can see the workflow problem AND the positioning problem AND the pricing problem. Every one of them looks like the move everything else depends on. Every one of them reads as a six-month commitment if you start there. The thing the prior weeks didn't tell you, because the prior weeks were about a different question, is what to fix first.

That's this week. The order matters. Get it wrong and the firm spends six to nine months in motion without progress, because each fix lands into a context that wasn't yet ready for it.

Where most founders are right now

Founder-led firms who've worked the prior three weeks tend to land in one of three states.

The first state is decision-paralyzed. The founder can name the bottleneck cleanly. They can also name three other things that look fixable. None of them is obviously first. Each one has an argument for going first. The result is a kind of low-grade thrash where the founder works on whichever fix has the most current pressure (a client escalation, a pricing question, a near-miss hire conversation), which means the sequence is being driven by inbound noise rather than operational logic.

The second state is half-sequenced. The founder has decided the workflow is the first move and started writing the doc. Two weeks in, the doc is at three pages, the second pass keeps getting deferred to next Friday, and a senior referral conversation has reopened the hire question even though the workflow doc isn't done. The fix is in motion but the order keeps slipping.

The third state, less common, is wrong-sequenced. The founder has decided to start with the visible lever (a price increase, a new positioning statement, a new website) because those feel like decisive moves. The workflow remains undocumented underneath. Three months later the visible lever has produced some movement but the firm's underlying capacity hasn't changed, which means the new positioning can't be delivered at scale and the new pricing has produced refund risk the founder didn't see coming.

All three states are recoverable. The fix is the same: name the order and run it.

Why the sequence matters more than any single fix

Here is the pattern that is consistent across founder-led firms, and the structural reason most founders sequence wrong.

Each operational fix has dependencies. Hiring depends on the workflow being documented enough to inherit. Repositioning depends on the workflow being able to deliver the new positioning consistently. Repricing depends on the workflow being legible enough that the new price is defensible against scope. None of those fixes is independent. Each one assumes a foundation that may or may not be in place.

When the foundation isn't in place and the fix happens anyway, two things tend to happen, and often both.

The fix doesn't take. The new hire kicks decisions back to the founder because the workflow they were supposed to inherit lives in the founder's head. The new positioning produces inquiries the firm can't credibly scope because the delivery shape hasn't shifted. The new price produces refund conversations because the scope-change protocol still defaults to "ask the founder," which means scope creep that should have been billed gets absorbed.

The fix masks the real problem. The founder works on the fix that didn't take, blames the fix (the hire, the positioning, the price), and reopens the search for a different fix in the same shape. The workflow problem underneath stays invisible because the founder is in motion. Six to nine months pass. The bottleneck is still there.

The pattern is consistent enough that we'd argue the single most consequential decision a founder makes in this state isn't which fix to pursue. It's the order to pursue them in, which is what the rest of this week is about.

The order, in three sentences

Here is the order Altvina applies inside Blueprint engagements. The argument for it lives in tomorrow's piece (the cost of getting it wrong) and Wednesday's full decision tree. For today, the headline:

Workflow before hire. Every other fix lands into the workflow that exists. Document it before any hire walks into it. If the workflow can't be documented in two to four weeks of focused founder work, the documentation isn't the gap, the architecture is, and that's a different kind of fix.

Hire before reposition. Repositioning produces demand the firm has to deliver against. If the operational layer doesn't have the senior bench to absorb the new shape, the repositioning surfaces capacity problems that look like delivery quality problems, which the firm then misdiagnoses as a hiring problem in the new shape. Get the senior layer right against the current positioning first.

Reposition before reprice. Pricing changes get justified by what the firm is delivering. Repositioning changes what the firm is delivering. Reprice into the new positioning, not the old one, or the price increase reads as opportunistic to existing clients and the new positioning lands without the margin shift it was supposed to enable.

That sequence isn't universal. There are firms where the right first move is positioning (when the workflow is already strong but the engagement shape is producing the variability). There are firms where the right first move is repricing (when the workflow and positioning are aligned but the firm is delivering well above its current price). The point of the decision tree on Wednesday is to surface which of those exception cases applies to your firm, in eight questions.

What to do this week

Three things, in order.

One. Name the bottleneck step. Not the bottleneck in general, the specific step. Intake, scoping, delivery, quality, billing, follow-up. Be specific. "The founder is the bottleneck" isn't specific. "Quality review is the bottleneck because every deliverable routes through the founder for sign-off, and the senior team won't ship without it" is specific.

Two. Test whether the bottleneck step is documented. Sit down for two hours this Friday and try to write the rules a senior person would apply at that step. Pricing band, quality bar, scope-change protocol, whichever decision the step turns on. If you can write the rules in two hours, the documentation is mostly there and the next gate is whether someone else could read it. If you can't, the documentation work is the next move and the rest of the sequence depends on it.

Three. Test whether the bottleneck is concentrated or distributed. A concentrated bottleneck (one step, one decision type) is a different fix than a distributed bottleneck (founder is in five steps for five different reasons). Concentrated bottlenecks usually fix with a workflow doc and possibly a hire. Distributed bottlenecks usually fix with a workflow architecture pass first, before any hire question is even on the table.

If those three checks come back as "documented, concentrated, ready to receive a hire," the prior three weeks of this series were the right read for your firm and the hire question is open. If they come back as "not yet documented" or "distributed across multiple steps," the next move is upstream of the hire, and the rest of this week walks through what that looks like.

What's coming this week

Tomorrow's post walks the cost piece, what sequencing wrong actually costs, the six-to-nine-month price most founders pay when they fix the visible lever before the foundational one.

Wednesday we publish the full Sequencing Decision Tree, eight yes/no questions that name the one thing to fix first, with the five paths the tree branches to.

Thursday is the Blueprint angle, how a sequenced fix actually unfolds inside an engagement, walked through from documentation through to repositioning so the rhythm is concrete.

Friday closes with the most expensive sequencing choice in founder-led firms, the "fix everything at once" reflex and why it produces firms that look like they're improving on every dimension and aren't.

The point of this week isn't to slow you down. It's to make sure the next six months of operational work compounds rather than thrashes.

Continue the series

This is part 1 of a 5-part series on The Order to Fix Things In. The full arc:

• Monday: When the Bottleneck Isn't a Hiring Problem (And You Still Have to Fix Something) (this post)
• Tuesday: What Sequencing Wrong Costs You (Six to Nine Months of Movement Without Progress)
• Wednesday: The Sequencing Decision Tree (Eight Questions That Tell You What to Fix First)
• Thursday: How a Sequenced Fix Actually Unfolds (A Walk-Through, From Documentation to Reposition)
• Friday: Why "Fix Everything at Once" Is the Most Expensive Sequencing Choice in Founder-Led Firms

Content and Accuracy Disclaimer

This article was drafted with AI assistance and reviewed by the Altvina team. We rigorously fact-check all content to ensure reliability.

Should you notice any inaccuracies or outdated information, please contact us so we can correct it. Your feedback helps us maintain high standards of accuracy and transparency.