The calendar that eats your plan

Why this matters to you right now

The Mankins and Steele study in the Harvard Business Review ("Turning Great Strategy into Great Performance," 2005) remains the reference work on the gap between strategy and execution. Verdict: across dozens of companies measured, real delivered performance averages between 37% and 65% of the annual plan, and most of the gap doesn't come from operational execution. It comes from the continuous reallocation of resources that drifts away from the plan in the first months, without ever being named for what it is. The same mechanic operates at the scale of a solo consultant, more violently: there is no allocation committee, just a calendar that fills itself by default.

Today is the first Tuesday of H2 2026. The reflex is to schedule a mid-year review: open the OKR document, update the percentages, adjust the numbers, close the document. That ritual is cosmetic. It moves zero minutes of the calendar to come. The 26 weeks of H2 will be eaten by the same mechanics that ate the 22 weeks of H1, unless you touch the structure of your week itself.

Edition #5 on the 2026 plan on one page laid out the mechanic of the annual plan. This edition handles the mechanic of its survival at mid-point.

If your mid-year review doesn't come out with at least one weekly block sanctuarized and one initiative explicitly killed, you didn't run a review. You ran a status update.

Pricing: segment your fees on H1 data

The action: Pull your H1 numbers. Billed engagements, real hours, effective margin per client segment. Identify the bottom quintile, the 20% of engagements that consume the most hours for the least margin. Re-engineer your H2 pricing by segment: a 25% to 40% increase on the bottom quintile, or a polite exit. Never a flat increase.

Why it works: Frederick Reichheld, in The Loyalty Effect (Bain & Company), documented that across almost every services practice, roughly 20% of clients generate 80% of effective margin, and the bottom quintile often runs at negative margin once true cost is measured. H1 just gave you the raw numbers to locate exactly where that distribution sits in your own practice. The mid-year OKR review never looks at them; the segmented pricing review does. A flat increase re-encodes the asymmetry for 26 more weeks.

The trap: The flat increase ("+10% on all my H2 engagements"). It protects the low-margin clients by leaving them cheap, and it punishes the high-margin clients who would have accepted much more. The H1 data exists so you can be precise; using it on average wastes it. The logic is exactly the one in edition #18 on the seven thresholds: a leap to the next bracket assumes a client remix, not blanket inflation.

This week: Thirty minutes with a spreadsheet. List of each H1 engagement, column for effective margin per hour. If your hours aren't tracked, run the exercise on your three largest engagements only: that's enough to reveal the quintile. For each client in that quintile, write one sentence: "raise to $X" or "exit by Y." Three lines per engagement are enough to produce the decision matrix that will shape H2.

Sales and development: revive H1 before prospecting H2

The action: Before you open a single new prospecting channel for H2, inventory the five H1 conversations that stalled at "interesting but not now." Revive them. You now have five months of data they didn't have in January, and they have five months of budget and operational context that you didn't have either.

Why now: Donald Sull and Kathleen Eisenhardt, in Simple Rules, show that high-impact decisions come from a small number of simple rules applied with discipline, never from a more complex new plan. For mid-year prospecting, the simple rule is: before new, revive. A consultant's hottest pipeline is almost never in their cold leads file; it is in their "not now" history from the past five months.

I did the opposite for years. Every June, I opened three new channels assuming the answer was in volume. The real leverage was in ten precise emails, sent to ten conversations I let cool because they "weren't ready." H1 data gives you exactly what those prospects wanted to hear in June, and what you couldn't have phrased in January.

The trap: Confusing "more prospecting" with "better pipeline." H1 has already filtered the real signals; H2 starts by exploiting them, not by drowning them. This revival logic directly extends edition #25 on the client who brings three: the post-engagement cadence is a special case of reviving the H1 relationships that didn't convert right away.

This week: Identify your five "not now" conversations from H1. Send each of them a short email (five lines max) anchored on one specific thing you have learned since the last exchange. Not a follow-up, a value update.

Collaboration networks: the 60-minute peer audit

The action: Book 60 minutes with a trusted peer. Not a coach, not a mentor, a peer, someone in a practice similar to yours. Walk in with exactly three numbers: your H1 revenue split by segment, your H1 calendar split by activity type, and your won / lost engagement ratio. Ask one question: "What do you see that I don't?"

The mechanism: Annie Duke, in Thinking in Bets, documents the self-evaluation bias: we systematically interpret our decisions in the light of their outcome, not in the light of their quality at the moment they were made. The only empirically validated antidote is the outside view of a peer who doesn't share the emotional cost of your H1. Not an open conversation. One question, anchored on three numbers. The format protects against drift toward therapy or small talk.

The trap: Solo introspection. You see what you chose to see for five months. The pattern that cost you H1 is invisible to you precisely because it is the pattern. The peer doesn't correct, they reveal, exactly like the offer-review mechanic argued in edition #24 on the offer that bleeds you.

This week: Book the hour. If you don't have a direct peer in your circle, a consultant from an adjacent practice (even a 30-minute exchange) produces the effect you need: the outside view without the shared emotional cost. Before the session, prepare your three numbers in one single one-page document. Prepare nothing else. The subject of the conversation is what the peer sees in it, not what you want to demonstrate.

Value creation: kill one initiative to save one

The action: Identify a stalled H1 initiative explicitly and kill it this week. Not "put it on pause." Not "move it to Q4." Kill it: remove it from the document, communicate it to the person who depended on it, and reallocate the corresponding calendar block to one single H2 initiative that comes out stronger.

Why it changes everything: Richard Rumelt, in Good Strategy Bad Strategy, lays out the kernel of any strategy in three elements: a diagnosis, a guiding policy, and a coherent set of actions. The classic mid-year mistake is to add a policy without removing one. Result: the list grows, the calendar doesn't move, the pattern continues. The fundamental strategic move isn't addition, it is subtraction. Cal Newport adds, in Deep Work, the mechanical half of the same principle: with no protected calendar block, no strategic initiative survives a month of active engagements. You kill to free a block, and the block becomes the only thing keeping the next initiative from stalling.

I personally postponed that gesture for years. I kept four strategic initiatives alive on paper because killing one meant admitting I had been wrong in January. None of them moved. The day I officially buried two of them, the two survivors started moving for the first time.

The test: How many initiatives on your plan have less than 20% progress at mid-year while still sitting as "active"? Those initiatives aren't late. They are dead without a death certificate. The inertia that keeps them on the list is exactly the inertia that prevents the others from advancing. The protected block that results from their burial is a piece of calendar infrastructure, exactly the kind of system argued in edition #13 on systems that scale without you.

This week: Choose. Write the one-page kill note: diagnosis, what we learn, what we free. Send it to a peer for accountability. Without a written note, the initiative resurfaces in three weeks, because no one will have made its death official.

AI: the mid-year auditor

The seasonal pivot assumes cold data on five months. No one calmly reads five months of calendar and CRM. AI does, in fifteen minutes.

The action: Use AI not to plan H2, but to reveal what H1 actually was. The patterns you no longer see because you lived them from the inside. Five use cases accessible this week, with no infrastructure.

1. 1.H1 calendar auditor. Export your calendar for the past five months (Google Calendar, Outlook, iCal). Submit to Claude with this prompt: "Categorize each block into four types: billable engagement, prospecting, operations and admin, non-billable strategic work. Give me the weekly distribution and the trend." AI does in five minutes what a manual spreadsheet would demand six hours of.

1. 1.Plan-delivery misalignment mapper. Give it your January OKRs and the actual list of H1 deliverables. Ask: "For each OKR, classify the actual deliverables as aligned, partially aligned, off-topic. Calculate the share of H1 effort actually aligned with the OKRs." The resulting number is almost always lower than expected, and that is exactly the number that justifies the pivot.

1. 1.Emerging-signal detector. Submit your list of client conversations from H1 (discovery notes, proposals sent). Ask: "Which themes or needs come up in more than three conversations without having been planned in January?" That is probably your next signature offer, already validated by the market without your knowing.

1. 1.Opportunity-cost calculator. For each stalled initiative, ask the AI to estimate a realistic scenario: "If this initiative had shipped at the end of April as planned, what revenue or benefits would have been plausible by end of December?" The number makes killing the initiative emotionally harder and strategically clearer.

1. 1.H2 protected-block simulator. Give the list of your H2 constraints (already-signed engagements, client commitments, vacations) and ask: "What is the smallest weekly re-engineering that frees a four-hour block per week for strategic work, without breaking any existing commitment?" The AI produces three concrete scenarios. You choose.

Where most consultants get it wrong: Believing AI will do the pivot for you. It won't. AI exposes patterns, calculates costs, proposes scenarios. The decision (kill, raise, protect, refuse) stays a human act, and often a political one. AI removes the logistical excuse ("I don't have time to read five months of data"), it doesn't substitute for the courage of the choice.

The warning: As edition #14 on AI for senior consultants argued, AI amplifies an existing discipline, it doesn't create a new one. Without the human decision to kill an initiative, the five workflows will produce a beautiful report that will still have no effect by December.

This week: Run workflow 1 on your past five months. Bring the output to your peer audit (section 4). You will arrive at the conversation with cold data instead of warm opinions.