The Sequencing Decision Tree (Eight Questions That Tell You What to Fix First)

The eight gates a founder-led firm should walk before committing to the next operational fix, with the five paths the tree branches to and how to read the result.

You've decided the next move isn't a hire. You've sat with the cost of getting the order wrong. You're somewhere between "I know I have to fix something" and "I don't know which thing to start with."

Pause for fifteen minutes. Walk the eight questions below. The first no in the chain ends the path and tells you what to fix first.

Founders of founder-led service firms often know they should be doing operational work. The harder question, the one that decides whether the work compounds or thrashes, is which work, in which order.

Why running the next fix without this gate usually fails

The instinct, when the bottleneck has been live too long, is to pick the visible lever. Repositioning, repricing, a sales hire, a delivery hire. Each one feels decisive. Each one is the kind of move a founder can describe in one sentence to a peer. Each one, in a firm where the underlying workflow isn't documented, lands into a context that wasn't ready for it.

The pattern that follows is well-rehearsed. The visible-lever fix doesn't take. The founder works on it for two quarters. The underlying workflow remains undocumented. Somewhere in month nine, the founder realizes the foundational fix was the right starting move all along. The cost is the six-to-nine-month gap.

The reason this happens, in our framing, is structural. The workflow lives in the founder's head. It doesn't feel like the foundation. It reads as basic work the founder has already done. Writing it down feels like busywork, not strategy. The visible moves (pricing, positioning, hiring) feel like the real strategic work. The pattern, in our framing, is the reverse. For a firm at this size, the documentation step is the strategic work. The visible moves only pay off once the documentation step is done.

The corollary, from yesterday's post, is that the cost of sequencing wrong is meaningfully higher than the cost of pausing for two weeks to walk the tree. The decision tree below is the gate that separates those two outcomes.

The 8 decision points

These are the eight gates a founder-led firm should walk before committing to the next operational fix. Each is a yes/no decision. The first no in the chain ends the path and names what to fix first.

Decision 1. Is the operating workflow documented enough that someone other than you could run it without daily founder input?

If no, stop. Fix workflow first. Documentation isn't optional and it isn't second. Every other fix that follows lands into the workflow that already exists. Hiring against an undocumented workflow guarantees the hire inherits the founder's head, not the role. Repositioning against an undocumented workflow guarantees the new positioning can't be delivered consistently. Repricing against an undocumented workflow guarantees the price increase produces refund risk you can't see coming.

The doc doesn't have to be a 40-page operations manual. One to three pages per major workflow node, written in language a senior peer could read without you in the room. The point isn't completeness. The point is legibility.

If yes, move to decision 2.

Decision 2. Could a peer who runs a similar firm read your workflow doc and tell you which step is the bottleneck without you in the room?

If no, stop. Fix workflow second pass. The doc exists but isn't yet legible. The bottleneck step is hiding inside language only you understand, which means a hire reading the same doc will inherit the same blindness. Two more weeks on the doc, ideally with one peer pressure-test, before any other move.

This is the most-skipped step of the sequence and the one that makes the difference between a firm that scales the workflow and a firm that scales founder dependence.

If yes, move to decision 3.

Decision 3. Is the bottleneck step concentrated in a single workflow node?

If no (the bottleneck is distributed across multiple nodes), stop. Fix workflow architecture, not the hire, not the reposition. Distributed bottlenecks are usually a sequencing problem inside the workflow itself, not a capacity problem that a hire would solve. The fix is rewiring the routing between nodes so each one stops feeding the founder.

A hire dropped into a distributed bottleneck absorbs the distribution and becomes a second routing hub, which is structurally worse than where you started.

If yes (one node), move to decision 4.

Decision 4. Is the work at the bottlenecked node stable enough that the rules could be written for someone else to apply them?

If no (the work is too variable to write rules for), stop. Fix positioning before hire. A node where rules can't be written for someone else is usually a node where the firm is taking on engagements broader than the positioning supports. The variability isn't an operational problem, it's a commercial-design problem.

Hiring into commercial-design variability guarantees the hire faces the same variability and either kicks decisions back to the founder or makes calls the founder would have made differently. Narrow the engagement shape first. Then the rules become writable. Then the hire becomes possible.

If yes, move to decision 5.

Decision 5. Have you written down the specific rules a senior person would apply at the bottlenecked node, in a doc someone else could read?

If no, stop. Write the decision-rules document first. This was last week's post and it is the gate that catches founders who've decided the hire is the right call but haven't yet written the artifact the hire would inherit.

The artifact is concrete: the eight categories of decisions a hire would inherit (pricing exceptions, scope creep, client escalations, refund authority, hiring authority, vendor selection, project sequencing, quality bar), with the rule and the exception for each, on paper, before the role goes live.

If yes, move to decision 6.

Decision 6. Does the firm have a 30-day stretch in the next quarter where the founder could clear 10 hours a week to onboard a senior hire?

If no, stop. Fix calendar capacity before opening the search. This is one of the most common sequencing failures. The readiness work is done. The spec is sharp. The rules are written. Then the founder opens the search into a quarter where the onboarding ramp can't actually happen.

The hire lands into a firm where the founder is too busy to transfer authority, and the routing pattern reasserts. Two to four weeks of calendar surgery first. Move standing meetings, defer two engagements, push the search start by 60 days.

If yes, move to decision 7.

Decision 7. Is the firm's pricing aligned with the value the workflow is currently producing?

If no (you're delivering well above the price you're charging), stop. Reprice before hire. Hiring into an under-priced engagement load doubles the under-pricing because you're now paying senior comp against revenue that doesn't support it.

Reprice the next engagement renewal cycle. That's usually a 30 to 60 day cycle and produces immediate margin without changing anything else about the firm. Then the hire decision gets made against the new margin profile, which is meaningfully different math.

If yes, move to decision 8.

Decision 8. Are the firm's positioning, workflow, decision rules, calendar, and pricing all aligned, with the bottleneck still concentrated in a single node where rule-application is the constraint rather than rule-writing?

If yes, the hire is the next move. You're in the small fraction of founder-led firms that approach the hire with the operational sequencing already done. Run the search.

If no, loop back to the first no in the chain above.

The five paths the tree branches to

Walking the tree produces one of five recommended starting points.

Path 1: Workflow documentation first (decisions 1, 2). The doc doesn't exist, or doesn't read cleanly to an outsider. Two to four weeks of focused documentation work, ideally with a peer pressure-test in week two. Most founders end the path here, even when they expected the answer to be the hire.

Path 2: Workflow architecture before hire (decision 3). The doc exists, the doc is legible, but the bottleneck is distributed across multiple nodes. The fix is rewiring the routing between nodes. This is usually a 4 to 6 week piece of work. It's also the one founders are least likely to attempt without outside help, because the firm's existing architecture is invisible to the people inside it.

Path 3: Positioning before hire (decision 4). The rules can't be written for the bottleneck node because the engagement shape is too broad. The fix is narrowing the positioning, which is uncomfortable because it means saying no to current revenue. Usually a one-quarter horizon.

Path 4: Decision-rules document before hire (decision 5). The doc exists, the architecture is sound, the positioning is right, the rules just haven't been written for the bottleneck node yet. Two-week artifact, exactly the work last week's post walked through.

Path 5: Calendar surgery, or repricing, before hire (decisions 6, 7). The operational layer is in good shape and the gating constraint is either founder calendar capacity or current pricing being below current value. Both are 30 to 60 day fixes.

Path 6: Hire is the next move (decision 8). All eight gates pass. Run the search.

Most founder-led firms end the path at decision 1, 2, or 3. The pattern is consistent. Founders look at the symptoms, see the bottleneck, and assume the answer is later in the chain (hire, reposition, reprice). It is almost always earlier in the chain: the workflow doc, the legibility of the doc, or the architecture of how the workflow nodes route to one another.

That isn't a moral judgment. It's a structural read. The workflow lives in the founder's head, so it doesn't feel like the foundation.

Reading the result

The first no in the chain names what to fix first. The path the tree branched to names the work.

If your first no was at decision 1, the next two to four weeks are documentation. Not strategy. Not search. Not pricing analysis. Documentation. Resist the pull to do anything else first, because everything else depends on this.

If your first no was at decision 2, you have a doc but it isn't yet legible. The next two weeks are a second-pass with a peer pressure-test built into the schedule. The doc isn't done until a peer can read it and name the bottleneck step without you in the room.

If your first no was at decision 3, the next 4 to 6 weeks are workflow architecture. That usually means redrawing the routing diagram. Identify the two or three nodes where the founder is the default fallback. Each one becomes a routing fix.

If your first no was at decision 4, the next quarter is positioning work. This is the longest of the paths and the most strategically consequential. It is also the one where outside pressure-testing helps most. Positioning blind spots are nearly invisible from inside the firm.

If your first no was at decision 5, the artifact is the Decision-Rules Worksheet from last week. Two weeks of work, on paper, before any role goes live.

If your first no was at decision 6 or 7, the fix is short and concrete: calendar surgery or a renewal-cycle repricing. 30 to 60 day operations, neither of which require outside help in most cases.

If you walked all eight gates with yeses, the hire is the next move and the prior three weeks of this series are the right read for your firm.

Closing

Tomorrow we'll walk through how a sequenced fix actually unfolds inside a Blueprint engagement, the rhythm from documentation through to repositioning, so the abstract sequence above becomes a concrete arc.

The decision tree is the gate. The sequenced fix is what passes through it.

There's a gap between "I have to fix something" and "the order is named, the first move is the workflow doc, the next four moves are scheduled in the right sequence." That gap is the difference between a firm that compounds in the next nine months and one that thrashes.

Continue the series

This is part 3 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)
• 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) (this post)
• 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.