Your H2 Plan Is a Forecast of Your Bottleneck

The mid-year review scores the outcomes. It rarely examines the machine that produced them.

It is the last full week of June, and many founder-led firms are sitting down to some version of the same ritual. Pull up the H1 numbers. Revenue against plan. Pipeline. Utilization. Score the half, sigh or celebrate, and then write the H2 plan.

The review usually gets done honestly. The misses get named. Nobody is hiding from the numbers.

And yet, in most of these reviews, something large goes unexamined. Not the outcomes. The thing that produced them.

The mid-year review looks at the scoreboard

A typical mid-year review is built to answer one question: how did we do? It compares results to intentions. Revenue versus target. Projects delivered versus projects promised. It is a scoreboard exercise, and as a scoreboard exercise it works fine.

But a scoreboard tells you what happened. It does not tell you why. The why lives in the operation itself: how work moves through the firm, where it waits, who it has to pass through, what gets dropped when things get busy.

That layer rarely makes the agenda. Look at your own template: a row for every number, and probably no row for the machine. So the review ends with a clear picture of the gap between plan and reality, and almost no picture of what created the gap.

The machine that produced the misses

This is the point that matters most this week.

Your H1 results were not random. They were produced. The late project, the stalled service launch, the quarter where delivery ate every hour of selling time: each of those was the output of a specific operating system, with specific habits, handoffs, and choke points.

If the review never examines that system, the H2 plan gets written on top of it unexamined. The numbers change. The dates change. The system that produced the H1 misses stays exactly where it was, fully intact, ready to produce them again.

That is not a character flaw in founders. It is a natural consequence of how the ritual is built. Outcomes are easy to measure and uncomfortable to ignore. The machine is hard to see from inside, especially when you are a working part of it.

January's plan with new dates

This is why so many H2 plans read the way they do. Strip out the formatting, and most of them are January's plan with new dates.

The growth target survives, lightly trimmed. The initiative that slipped gets re-promised for Q3. The operational change that never happened gets carried forward with a fresh deadline. The plan looks new because the calendar is new.

But a plan inherits whatever it is built on. Write it on an unexamined operation and it inherits the H1 bottlenecks by default. Not because anyone chose that, but because nobody chose otherwise.

A forecast of the constraint, not the ambition

So here is the inversion worth sitting with this week.

A plan written on an unexamined machine is not really a statement of ambition. It is a forecast. And what it forecasts is not the goal. It is the constraint.

If client work routed through you was the reason H1 deliverables slipped, then the H2 plan that assumes more deliverables is a forecast of more slipping. If proposals stalled because only one person could price them, the H2 revenue line is a forecast of that queue. The plan does not say this out loud. It says it structurally, in every line that assumes the machine will behave differently without anyone changing it.

Read that way, the H2 plan is one of the most honest documents in the firm. It is just honest about the constraint, not the ambition.

None of this means mid-year planning is pointless. The timing is genuinely good: a full half of evidence behind you, a clean half ahead, and Q3 2026 starting Wednesday, July 1. The point is narrower. The review, as usually run, examines the wrong layer. The outcomes get the scrutiny. The machine gets a pass.

One thing to try this week

Before you write a single H2 line, take your H1 review and add one sentence to every miss.

Not a sentence about the number. A sentence about the mechanism. For each commitment that slipped or fell short, write down what in the operation produced that result. Where the work waited. What it had to route through. What got displaced and by what.

Do not fix anything yet. Just write the sentences. If you find that several misses produce nearly the same sentence, you have learned more about your H2 plan than the scoreboard will ever tell you, because whatever appears in those sentences is what the new plan is about to be built on.

This week we are staying on this one theme. Tomorrow we will look at the single most revealing line in most H2 plans, and on Wednesday we will share a short, practical way to test a finished plan against the operation that has to carry it.

Continue the series

This is part 1 of a 5-part series on Load-Test the Plan. Then Look at the Price.. The full arc:

• Monday: Your H2 Plan Is a Forecast of Your Bottleneck (this post)
• Tuesday: The Line You Copied From January
• Wednesday: The 15-Minute H2 Load Test
• Thursday: The Workflow Is Not Broken. It Is Executing the Price.
• Friday: Utilization Is High Because Pricing Is Broken

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.