Most quarterly planning processes work like this: leadership agrees a roadmap, project managers estimate effort, someone runs a spreadsheet to see if it fits, and then everyone agrees it fits even when it clearly doesn’t — because nobody wants to be the person who says the plan is unrealistic.
Scenario-based capacity reviews break this cycle. Instead of trying to fit everything in and hoping for the best, you model two or three explicit alternatives before the quarter starts and make a deliberate choice between them.
What Is a Scenario-Based Capacity Review?
A scenario-based review presents decision-makers with multiple versions of the quarter’s plan, each with different assumptions, trade-offs, and outcomes. Rather than one “the plan,” you have:
- Scenario A (Aggressive): Full roadmap, requires every team at 95%+ utilisation. High risk of slippage.
- Scenario B (Balanced): Core roadmap items delivered, two initiatives deferred. Teams at 75–80% utilisation.
- Scenario C (Conservative): Focuses on three strategic priorities only. Teams have capacity buffer for unplanned work.
Leadership chooses the scenario, not the capacity analyst. That’s the key difference.
Step 1: Build the Baseline Scenarios
Before the planning meeting, the operations team should have built at least two scenarios using the team’s actual capacity data. Each scenario should show, for each team: total available capacity, total demand in scenario, utilisation percentage, and which projects are included or excluded.
Step 2: Surface the Trade-Offs Explicitly
Each scenario should come with an explicit statement of what you gain and what you lose. Scenario A delivers more output but carries delivery risk. Scenario C carries less risk but sacrifices velocity. Leadership can only make a good decision if the trade-offs are visible.
Step 3: Account for Known Unknowns
Every quarter has unplanned work — support escalations, urgent board requests, unexpected attrition. Build a “unplanned work buffer” (typically 10–20% of total capacity) into each scenario. Scenarios that don’t include this buffer are not realistic, regardless of how clean the numbers look.
Step 4: Decide and Document
Once leadership has chosen a scenario, document which projects are in, which are out, and what the decision criteria were. This documentation is what you return to mid-quarter when someone asks “why isn’t Project X further along?”
Why This Works
Scenario-based reviews shift the conversation from “can we deliver everything?” (always answered with optimistic yes) to “which version of the quarter do we want?” (a real choice with real trade-offs). That shift is small but powerful — it creates accountability for the plan rather than ambiguity about it.
