Tag: Scenario Planning

Once you hire someone, you’re committed to at least several months of salary, and letting someone go is costly in both financial and human terms. So leaders are cautious — they want certainty before committing to headcount.

Scenario planning doesn’t give you certainty. But it gives you the next best thing: pre-made decisions for multiple possible futures, so when conditions become clear you can move fast.

The Hiring Decision Problem

The classic hiring dilemma looks like this: “We think we’ll need three more engineers in Q3, but we’re not sure how Q2 revenue will land. If Q2 hits target, we definitely hire. If it misses, maybe we wait. So let’s wait and see.”

By the time Q2 results are known, you’re in Q3. The hiring process takes 3–4 months. The engineers won’t be productive until Q4 at the earliest. You’ve lost the entire year.

The scenario planning solution is to make the decision conditional in advance. “If Q2 revenue is >$X, we begin hiring immediately. If it’s between $Y and $X, we hire for two of the three roles. If it’s below $Y, we hold.”

Now the decision is made. What’s left is monitoring the trigger, not agonising over the framework.

Building a Hiring Decision Tree

For each scenario, define:

• Trigger: What signal tells you you’re in this scenario? (Revenue milestone, funding close, win rate threshold)
• Hiring response: Which roles, how many, in what sequence
• Timeline: When does hiring begin, what’s the target start date
• Budget impact: What does this headcount cost, and where does it come from

This decision tree should be built during the annual or quarterly planning process — not when the signal arrives.

Moving From Decision to Action Quickly

When the trigger fires, the decision is already made. The operational task is to execute it quickly — job descriptions are drafted, interview panels are identified, recruiting partners are briefed. Everything that can be done in advance should be.

The goal is to compress the lag between “we know we need to hire” and “the person is in the role” from six months to three.

The default planning mode is a single best-estimate forecast: here is what we expect revenue to be, here is the headcount we’ll hire, here is the roadmap we’ll deliver. One plan, one future, all energy focused on executing against it.

The problem is that the future rarely looks like the plan.

The Illusion of Precision

Single-point forecasts create an illusion of precision. A budget that says “we will spend $4.2M in H1” sounds precise. It implies a level of confidence in the underlying assumptions — revenue trajectory, hiring timeline, project scope — that almost never exists in practice.

This illusion is dangerous because it discourages adaptive planning. If the plan is specific, deviating from it feels like failure. So organisations stick to the plan past the point where the plan is clearly wrong — because changing the plan requires admitting the original was flawed.

The Cost of Single-Scenario Betting

The cost of planning for only one future shows up differently depending on which direction reality diverges. If things go better than expected, the organisation is slow to accelerate — there’s no pre-built plan for upside. If things go worse, there’s no pre-built response — leadership has to improvise under pressure, in a compressed timeframe, with deteriorating options.

Both are expensive. The upside miss is often invisible — you never know how much faster you could have grown. The downside scramble is painful and visible — decisions made under pressure that a little prior thinking could have made better.

Building Adaptive Capacity

The alternative to single-scenario betting is not analysis paralysis. You don’t need to model every possible future. You need to model the futures that matter — the ones where you’d respond differently.

Start by identifying the two or three most uncertain variables in your operating environment. For each pair of extremes, ask: would we do anything differently? If the answer is yes, you need a scenario for it. If no, you don’t.

Most businesses need three to four scenarios, not fifty. The value is not in the modelling — it’s in having made the decisions in advance.

It’s the practice of developing multiple explicit alternative futures and preparing the organisation to navigate each of them, rather than betting everything on a single forecast.

In a predictable environment, scenario planning is useful. In an uncertain one — economic volatility, rapid market change, geopolitical disruption — it’s essential.

What Scenario Planning Is Not

Scenario planning is not the same as forecasting. A forecast is your best estimate of what will happen. A scenario is a coherent narrative about a possible future, not necessarily the most likely one.

Scenario planning is also not the same as contingency planning. Contingency plans are reactive — “if X happens, we’ll do Y.” Scenario planning is proactive — “we’ve thought through what world X looks like, and we’ve made decisions in advance that make us resilient to it.”

The Four-Scenario Framework

A practical COO-level scenario framework covers four quadrants of the two variables that matter most for your business. For a growth-stage SaaS company, these might be: market demand (high/low) and access to capital (ample/constrained).

This generates four scenarios:

• High demand + ample capital: Aggressive growth mode — full hiring plan, accelerated investment
• High demand + constrained capital: Prioritise ruthlessly — hire only critical roles, maximise revenue capture
• Low demand + ample capital: Product investment — use capital advantage to build while demand is soft
• Low demand + constrained capital: Survival mode — protect core, extend runway, minimum hiring

Each scenario should have pre-agreed responses across headcount, budget, and strategic priority. The goal is to make the decisions in advance, not under pressure.

The Planning Process

Step 1: Identify your two key uncertainties — the variables with the highest impact and the highest uncertainty for your business.

Step 2: Build four scenarios from the extremes of those two variables.

Step 3: For each scenario, define what the company would do differently across three dimensions: headcount, budget, and strategic priorities.

Step 4: Identify leading indicators — early signals that would tell you which scenario is developing.

Step 5: Agree decision triggers — at what point would you move from one scenario response to another?

The Update Cadence

Review scenarios quarterly. The scenarios themselves don’t need to change frequently — what changes is your assessment of which scenario is most likely to develop, and whether the early indicators are pointing in one direction.