You Ran the Load Test. Now What?

Most finished tests hold fewer problems than answers. Often just one.

The short version: Five answers from the load test usually point at one constraint. Two are tasks you can do this month, two are workarounds to run with clear eyes about their shelf life, and one is the shape of the firm underneath all five. Read your answers as a map, not a project list.

Last Wednesday we published the 15-minute H2 Load Test. Five questions, run against your H2 plan. If you did it, you're sitting with five answers.

Here's the trap.

Five answers don't mean five projects

It looks like a to-do list. Hire someone. Build the workflow. Write the playbook. Fix escalations. Protect your calendar. So you try to do all five, spend five times the energy to move one thing, and often that one thing still doesn't move.

When a single diagnostic asks five questions about one operation, the answers usually point at the same constraint, just dressed up differently.

Here's what that usually looks like

This isn't a real client. It's the shape these answers tend to take in founder-led services firms.

1. Capacity that isn't there. "The new advisory line assumes fifteen senior hours a week. Our two senior people are booked through September." Real finding. But ask why senior hours are scarce. In a lot of firms, only senior people (often only the founder) are allowed to make the calls the work requires.

2. The shared well. "The H1 referral push stalled because my hours kept getting pulled into delivery. The H2 marketing line draws on those same hours." This isn't a marketing problem. It's the same calendar fact as answer 1, on a different line.

3. Where work stacks up. "When volume rose in March, everything piled up at my review step. Deliverables waited days for sign-off." Now the constraint stops hiding. The queue is your attention.

4. Who can decide without you. "Nobody scopes or prices a proposal without me." Answer 3 at the front door instead of the back.

5. What the plan quietly assumes. "The client-escalation workaround held in H1, barely. The plan assumes it keeps holding." That workaround exists because escalations route to you, whose attention is already the queue from answer 3. Not a fifth problem. The first four under stress.

Read the annotations down the page. Five answers, one constraint: decisions route through one person, and every line of the plan waits on that. Yours might land somewhere else. A handoff. A review step. An overloaded role. The point is, it probably converges somewhere.

The finding isn't "founders are bottlenecks." You've heard that one. The finding is the method: before any answer becomes a project, ask what single fact could have produced all five, and only staff what survives. And if your five answers genuinely don't converge, that's information too.

What you can fix yourself this month

Two of these are actual tasks. Treat them that way.

The capacity math (answer 1). Take every plan line that can't name the hours funding it. Shrink it, push it to when those hours exist, or cut it. An afternoon with a calendar. It works because you're changing the plan, not the people.

The loud thing (answer 5). Give the workaround an owner who isn't you. Ask that person to write the actual process this month, while H1's evidence is still fresh. A workaround with an owner and a written page is just a process.

The two that are structural

The other two (the queue at your review step, and the decisions nobody makes without you) aren't tasks. They're the shape of the firm. You can still work them yourself. Just know what you're buying.

For the queue: batching helps. Two fixed review windows a week instead of a constant pile. It works for a while, then decays. Urgent items earn exceptions, exceptions become the norm, and eventually the windows are decoration. Batching shortens the queue. Everything still enters it.

For the decision dependence: a written scoping and pricing guide helps. It decays for a quieter reason. The guide captures the cases you've already seen. New cases route back to you, asking is faster under deadline than interpreting a page, and the habit stays while the guide goes stale. The workaround manages the constraint. It doesn't move it.

Here's another way to hold both. A workaround is the firm telling you, in behavior instead of words, exactly where the constraint lives. Batching points at the queue. The guide points at the decisions still routing through you. Even while they decay, your workarounds are the most honest map of the constraint you already have.

One page, one problem

The honest summary of a finished load test is rarely five projects. Closer to: two tasks this month, two workarounds run with clear eyes about their shelf life, and one constraint underneath all five answers.

And if that one constraint keeps surviving every operational fix you point at it, it might live in a layer you haven't price-checked yet. Not how the work moves through the firm, but what the work was priced to carry in the first place.

If reading your own answers feels worth doing with another set of eyes, a short fit call is one option. The Altvina Blueprint is scoped work that names the constraint under your five answers and prices only what survives the read. If it isn't the right next step, you'll still leave the call with a cleaner version of your own load test.

Book a fit call →

Continue the series

This is part 2 of a 4-part series on The Quarter Inheritance. The full arc:

• Monday: Nothing Resets on July 1
• Tuesday: You Ran the Load Test. Now What? (this post)
• Wednesday: Which of Your Problems Are Pricing Problems?
• Thursday: The Load Leaves Before the People Do (coming Thursday)

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.