Hiring strategy
Forecast workforce needs with three operating scenarios
Use scenarios to show how workforce choices change when demand, funding, or delivery assumptions move. Build a base case, a constrained case, and an expansion case from the same workload model. For each, name the roles, sequencing, risks, and trigger that would justify switching. The value is preparedness, not a confident prediction.
On this page
Choose the uncertain drivers
Identify the few variables that materially change the work: customer volume, launch timing, service scope, attrition in a critical team, or an approved expansion. Avoid a giant list of weak possibilities. For each driver, record the current evidence, owner, and next point when better information should arrive. Scenarios are easier to update when assumptions are visible.
Use one workload model
Translate each driver into work units and capability needs using the same logic across scenarios. If the expansion case assumes more customers, show which tasks grow and which do not. Keep productivity improvements separate from headcount so leaders can see when the plan depends on an untested process change. Include management and onboarding capacity, not only delivery roles.
Write three coherent cases
The base case reflects the most supported current assumptions. The constrained case shows what the company protects if resources or demand fall. The expansion case adds work only when named signals appear. Each case should be internally workable, not simply the base plan with a percentage added or removed.
- What work exists in this case?
- Which roles become critical first?
- What risk is consciously accepted?
- What signal changes the case?
Identify no-regret moves
Some actions help across all scenarios: clarify roles, cross-train a single point of failure, prepare a scorecard, or improve workforce data. Other actions are harder to reverse, such as adding several permanent roles before demand is confirmed. Sequence no-regret preparation first and tie commitments to evidence. This preserves speed without pretending uncertainty has disappeared.
Use triggers in the review
Illustrative example: a service company models a stable base, delayed expansion, and faster customer onboarding. All cases need one operations lead because ownership is already missing. Two additional coordinators appear only in the expansion case, triggered by approved customer launches rather than sales conversations alone. The constrained case pauses back-office improvement work and shows which service response the team would protect.
Challenge false precision
A spreadsheet can make uncertain assumptions appear exact. Use ranges where the underlying workload varies and label the confidence of each input. Ask which single assumption changes the plan most, then seek better evidence there. Do not spend equal time refining minor inputs. If leaders disagree, preserve both views in scenarios rather than averaging them into a number that nobody actually believes or knows how to act on. Archive the superseded assumption when evidence changes so the team can explain why the plan moved.
Next step
Build three cases from one workload model and attach a named trigger, decision owner, and accepted risk to every role that changes between them.