December 1, 2025 · 5 min read
Simplifying a Quarterly Planning Process That Had Become Its Own Project
A client's quarterly planning cycle had grown to consume nearly six weeks of the quarter it was supposed to plan. We cut it to two.
By the time I got involved, the client's quarterly planning process took close to six weeks of a thirteen-week quarter — nearly half the quarter spent planning the quarter. Nobody had designed it that way on purpose; it had grown one well-intentioned addition at a time: a pre-planning survey, a planning offsite, a post-offsite synthesis doc, a review round with three separate stakeholder groups, a final sign-off meeting.
Every individual step had a reasonable justification when it was added. The survey improved input quality. The offsite improved buy-in. The three-group review improved cross-functional alignment. None of that reasoning was wrong — the problem was that nobody had ever asked what the whole thing cost in aggregate, because each addition was evaluated in isolation.
A planning process built one justified addition at a time can still add up to something nobody would have designed on purpose from scratch.
What we cut and what we kept
- Kept the pre-planning input survey, but cut its window from two weeks to three days — the extra time wasn't producing better input, just later input.
- Replaced the three sequential stakeholder reviews with one joint session, which actually surfaced disagreements faster because people heard objections live instead of relayed secondhand.
- Cut the standalone synthesis doc entirely — it was being written for an audience that was the same people who'd just been in the offsite.
- Kept the final sign-off meeting, unchanged, because it was the one step everyone agreed was load-bearing.
The result
Six weeks became two, and the decisions that came out of planning were, if anything, sharper — forcing disagreements into one joint room instead of three sequential ones meant they got resolved instead of smoothed over at each handoff. The lesson that generalized past this one client: processes rarely get bloated through one bad decision, they get bloated through many good ones made without anyone looking at the sum, and the fix is almost always subtraction, not a better tool.