A complete scenario planning sample defines a decision, identifies the uncertainties that could change it, and tests every available option against several plausible futures. This worked SaaS operations example covers capacity expansion under uncertain demand, staffing, and infrastructure costs, including assumptions, consequences, leading indicators, trigger points, owners, and contingency actions.
Key Takeaways
1Build scenarios around critical uncertainties, rather than writing optimistic and pessimistic versions of the same forecast.
2Compare every capacity option inside every scenario so that a changed constraint updates the whole decision rather than one preferred path.
3Convert each uncertain assumption into a monitored signal, a trigger point, an accountable owner, and a pre-agreed action.
What does a complete scenario planning sample include?
A complete scenario planning sample connects a present decision to plausible future operating conditions. It should let another decision owner understand what is being decided, which assumptions matter, how the alternatives behave, and when the chosen course should change.
The focal decision in this example is:
Which capacity posture should a SaaS company approve for the next 12 months: commit to expansion now, expand in stages, or defer commitment while improving demand visibility?
The illustrative operating baseline and all figures below come from a hypothetical SaaS model created for this tutorial. They are planning assumptions, not industry benchmarks.
Template field
Worked SaaS example
Focal decision
Choose between committed expansion, phased expansion, and deferred expansion
Planning horizon
12 months, set by the hypothetical annual infrastructure commitment cycle
Baseline condition
Peak utilization is 68%, based on the tutorial's hypothetical operating baseline
Demand assumption
Customer workload may grow between 5% and 35%, based on the tutorial's scenario range
Staffing assumption
Platform hiring may take between 60 and 150 days, based on the tutorial's planning assumptions
Cost assumption
Infrastructure unit cost may fall by 8% or rise by 18%, based on hypothetical supplier outcomes
Decision constraint
Maintain the service objective while keeping unused committed capacity within the approved budget
Demand, utilization, hiring lead time, unit cost, and service reliability indicators
Governance
Named signal owners, monthly reviews, and trigger-based escalation
A forecast would select one expected demand number and optimize around it. A scenario examines several internally consistent futures without claiming that one is the prediction. The UK Government Office for Science futures toolkit treats scenarios as structured ways to explore uncertainty, which is the useful distinction for capacity decisions.
The three capacity options also need precise definitions. Commit now means reserving the full planned capacity and opening permanent roles. Expand in stages means approving an initial increment while preserving the option to add more. Defer means holding current commitments and using temporary operating controls until demand becomes clearer.
A scenario board becomes a practical decision support system when it preserves these links between assumptions, alternatives, consequences, and actions. Lucid supports that use by converting an unstructured dilemma into an options map and refining every path when a constraint changes.
How do you define drivers and critical uncertainties?
Drivers are forces that influence the decision. Critical uncertainties are drivers with both a meaningful range of possible outcomes and enough impact to change the preferred option.
Demand growth is a critical uncertainty in this example because weak and strong growth create different capacity needs. The current number of customer contracts is merely an input. Treating every variable as uncertain produces noise and gives decision owners no basis for constructing coherent futures.
Start by separating known conditions, directional drivers, and critical uncertainties:
Classification
SaaS capacity example
Treatment
Known condition
Existing service architecture and current commitments
Hold constant unless a formal constraint changes
Directional driver
Customers are using more processing-intensive features
Include in the demand narrative
Critical uncertainty
Timing and scale of workload growth
Vary across scenarios
Critical uncertainty
Time required to recruit qualified platform staff
Vary across scenarios
Critical uncertainty
Future infrastructure unit cost
Vary across scenarios
Control variable
Timing and size of the capacity commitment
Represent as an option
Leading indicator
Peak utilization and signed workload commitments
Monitor after the decision
The strongest scenario set usually rests on a small number of uncertainties that combine into distinct operating conditions. For this model, demand is the primary uncertainty. Staffing availability and infrastructure cost then shape whether each demand path is manageable or expensive.
Do not choose uncertainty ranges through group negotiation alone. Write down the evidence source, the person responsible for the estimate, and what would invalidate it. For infrastructure costs, the FinOps Framework guidance on unit economics provides a useful way to connect consumption, cost, and business value rather than treating the supplier invoice as an isolated budget line.
Decision bias enters when the team defines scenarios around a preferred proposal. An expansion sponsor may assume strong demand and fast hiring, while a finance owner may combine weak demand with rising costs. Both have built arguments, not scenarios. Use the decision bias types and practical controls to separate evidence from advocacy before assigning scenario ranges.
A useful control is to make one person document assumptions and another challenge their causal consistency. Strong demand may increase infrastructure discounts through committed volume, for example, but it can also worsen staffing pressure. Each scenario needs a defensible chain of consequences.
How do you build and compare three paths in a scenario planning sample?
Build three plausible scenarios by combining critical uncertainties into coherent futures, then test every option inside each future. A baseline, upside, and stress path are enough for this capacity decision because they expose the main tradeoffs without creating a grid too large to maintain.
The following figures are illustrative assumptions from the hypothetical SaaS operating model used throughout this scenario planning sample.
Scenario
Demand path
Staffing condition
Infrastructure cost
Operating narrative
Controlled growth
Workload rises 15% over 12 months
Roles fill within 90 days
Unit cost remains stable
Growth continues near plan and capacity can be added without emergency measures
Accelerated adoption
Workload rises 35% over 12 months
Roles fill within 60 days
Unit cost falls 8% after commitment
A major feature drives usage and committed scale improves supplier economics
Margin squeeze
Workload rises 5% over 12 months
Roles take 150 days to fill
Unit cost rises 18%
Demand softens while specialist labor and infrastructure become more expensive
These labels are more useful than “best case” and “worst case.” A nominally positive demand surge can still produce service failures if hiring lags. A weak-demand path can preserve reliability while damaging margins through unused committed capacity.
Now compare the options against each future:
Capacity option
Controlled growth
Accelerated adoption
Margin squeeze
Commit now
Adequate headroom, but some capacity may remain unused early
Best reliability protection and lowest delay risk
Highest exposure to unused capacity and fixed commitments
Expand in stages
Matches demand with manageable execution overhead
May require rapid second-stage approval and temporary safeguards
Limits sunk commitment while preserving an expansion route
Defer
Protects cash but narrows the response window
Creates the highest reliability and delivery exposure
Avoids excess capacity, though supplier prices may worsen before commitment
The staged option is the most resilient starting position in this example. It performs acceptably across all three scenarios and preserves the ability to accelerate if demand signals strengthen. A weighted decision matrix process can quantify the final comparison once the scenario consequences are visible, but scoring should follow scenario design rather than replace it.
Real options analysis preserves flexibility
Real options analysis values the right to make a later commitment after uncertainty resolves. In this example, phased expansion may carry higher short-term unit costs, yet that premium purchases time and limits the cost of being wrong.
The practical question is whether the option fee is lower than the avoidable downside. If a staged contract costs slightly more but prevents a large unused commitment under the margin-squeeze scenario, flexibility has operational value. Where outcomes can be assigned credible probabilities and financial values, a worked expected-value tree example helps test that tradeoff.
What happens when one constraint changes?
A changed constraint must update every option and scenario. Suppose the hypothetical service owner raises the availability requirement from 99.9% to 99.95%. Those figures come from the tutorial's illustrative change request rather than an external benchmark.
Committed expansion may need extra redundancy. Phased expansion may require the first stage to include failover capacity rather than demand capacity alone. Deferral may cease to be viable because existing headroom cannot support the revised resilience requirement.
Updating only the preferred option hides comparative effects. This is one reason spreadsheet scenario tabs become unreliable: formulas diverge, copied assumptions survive, and reviewers cannot see which consequence came from which constraint. Collaborative decision-making software is most useful when a single edited assumption propagates through the complete option map.
How do you turn scenario signals into actions?
Scenario signals are observable measures that indicate which future is emerging. Each signal needs a trigger, an owner, a review date, and an agreed response; otherwise, the scenario plan becomes a document nobody updates.
The thresholds below come from the hypothetical SaaS model created for this tutorial. A real team should derive its thresholds from architecture limits, approved budgets, supplier terms, and service objectives.
Signal
Illustrative trigger
Owner
Review rhythm
Contingency action
Peak infrastructure utilization
Exceeds 78% for 3 consecutive weekly reviews
Platform operations lead
Weekly
Activate the next capacity stage and validate failover headroom
Contracted workload
Signed demand exceeds the controlled-growth assumption by 10%
Revenue operations lead
Monthly
Reclassify the demand path and bring forward the expansion review
Hiring lead time
Forecast exceeds 120 days
Engineering operations lead
Every recruiting review
Approve temporary specialist coverage and reduce concurrent migration work
Infrastructure unit cost
Supplier quote rises more than 12% from baseline
FinOps or procurement owner
At each pricing event
Rebid the workload, renegotiate term length, or reduce noncritical consumption
Availability risk
Error budget consumption breaches the internal escalation threshold
Service owner
Weekly
Freeze discretionary load growth and accelerate resilience capacity
Trigger points should prompt a defined decision, not an automatic purchase. Crossing the utilization threshold might require the owner to verify that the increase is sustained, customer-driven, and not caused by an inefficient release. The escalation rule should still have a deadline so that “validate first” does not become indefinite delay.
Monitoring also needs expiry dates. Set the next formal review when the decision is approved, and bring it forward when a trigger fires. The risk control matrix approach for SaaS teams is useful when contingency actions introduce new risks that require separate owners and controls.
A sound recommendation should therefore state: choose phased expansion, preserve the right to accelerate, monitor demand and capacity weekly, reassess supplier costs at each pricing event, and reopen the decision when a trigger is crossed. That format is far more defensible than “proceed cautiously” because every condition has an observable test.
Frequently Asked Questions
Can you provide a simple example of scenario planning?
A SaaS company can compare committed, phased, and deferred capacity expansion under controlled growth, accelerated adoption, and margin-squeeze scenarios. Each option is assessed for reliability, cost exposure, staffing pressure, and future flexibility.
What is another name for scenario planning?
Scenario analysis, scenario development, and strategic foresight are commonly used related terms. Sensitivity analysis is different because it usually changes one variable at a time rather than building coherent future conditions.
What is a scenario planning process?
The process defines a focal decision, identifies critical uncertainties, builds plausible futures, compares all options, and assigns indicators and contingency actions. Teams then review the signals until the decision horizon ends or a trigger requires reassessment.
What are the three common types of scenarios?
Teams often use a baseline path, an upside path, and a stress path. These should represent plausible combinations of demand, cost, staffing, and external conditions rather than simple percentage adjustments to one forecast.
A useful scenario plan ends with an owned decision and an update mechanism. If you need to turn an unstructured capacity dilemma into comparable paths with visible tradeoffs and future consequences, register for Lucid and build the option map before the next commitment becomes difficult to reverse.
