Section 1
The five challenges at a glance
Small firms fail at futures thinking in five characteristic ways, and each has a documented root in the scenario literature. First, forecast dependence: planning around a single expected case, the exact habit Wack found fatal at Shell, where forecasts worked until they failed precisely when it mattered most (Wack, 1985). Second, mental model lock-in: founders unconsciously assume next year resembles this year, which Shell's practice was explicitly designed to break (Wilkinson and Kupers, 2013). Third, the scale myth: believing scenarios require a planning department, when Schoemaker's process is a structured workshop, not an institution (Schoemaker, 1995). Fourth, scenario theater: producing narratives that never touch a real commitment, the failure mode Wack warned about when scenarios reach facts but not the perceptions inside decision makers' heads. Fifth, missing tripwires: even firms that imagine futures rarely define the observable signals that would trigger a pre-agreed response, so the scenario work decays into a forgotten document. The table maps all five. The deeper analyses that follow concentrate on forecast dependence, lock-in, and scenario theater, because those three account for most of the gap between firms that merely worry about uncertainty and firms that are positioned for it.
Section 2
Challenge one: forecast dependence and why single-point plans break
Wack's foundational insight came from watching forecasting fail at the world's most sophisticated planning operation. Shell's forecasts in the late 1960s signaled disruption ahead, but point forecasts could not prepare executives for discontinuity; they encoded the assumption that tomorrow's world would be structurally similar to today's (Wack, 1985). His response was to replace the single expected future with a small set of structurally different futures, which let Shell anticipate not one but two oil shocks in the 1970s (Wilkinson and Kupers, 2013). The small-firm version of forecast dependence is the annual budget built on one revenue number, one hiring plan, and one assumed close rate. In 2026, with only 30% of CEOs confident in near-term revenue growth and uncertainty itself ranked the top threat by 43% of US CEOs, single-point planning is a structural liability (PwC, 2026; Conference Board, 2026). The fix is not better forecasting. Schoemaker's research frames scenarios as a tool that bounds uncertainty: instead of asking what will happen, the firm asks what range of futures it must survive and which commitments hold across that range (Schoemaker, 1995). A pipeline that supports the plan in three of four scenarios is a plan; one that works only in the optimistic case is a wish with a spreadsheet.
Section 3
Challenge two: mental model lock-in is the real planning failure
Wack's most quoted distinction is that scenarios deal with two worlds: the world of facts and the world of perceptions, and their purpose is to change the perceptions inside decision makers' heads (Wack, 1985). Wilkinson and Kupers, who interviewed nearly every living veteran of Shell's scenario operation, concluded that the practice survived half a century because it broke the ingrained corporate habit of assuming the future will look like the present (Wilkinson and Kupers, 2013). Founders are unusually exposed to this lock-in because their mental models were forged in a specific demand environment. The agency founder who built a firm in the cheap-leads era of paid social keeps operating that model years after acquisition economics inverted. The consultant who scaled on referrals assumes referral flow is a constant rather than a regime that can end. Lock-in is invisible from inside; no internal dashboard reports that your worldview is stale, because every metric is interpreted through the worldview itself. Scenario work is the cheapest known instrument for surfacing these assumptions, because writing a plausible future in which your core assumption is false forces the assumption into the open. The output that matters from a small-firm scenario day is not the narratives; it is the list of previously invisible assumptions the narratives exposed, ranked by how much of the firm's revenue depends on each.
Section 4
Challenge three: scenario theater, when futures work changes nothing
The most common failure among firms that do attempt scenarios is producing them without consequence. Wack saw this at Shell: his early scenarios were intellectually admired and behaviorally ignored, and he judged them failures because they reached managers' inboxes but not their decisions (Wack, 1985). He concluded that scenario work succeeds only when it connects to the specific commitments executives are about to make. Wilkinson and Kupers found the same pattern across five decades: Shell's scenarios endured because they were embedded in strategy making, risk management, and leadership processes rather than published as standalone documents (Wilkinson and Kupers, 2013). Small firms replicate the theater version easily: an energizing offsite, three clever futures named after weather patterns, and a Notion page nobody opens again. The test that separates theater from planning is simple: did any current commitment change? Schoemaker's process design builds this in by ending with strategy evaluation, checking each existing strategy against each scenario and flagging the ones that only survive in one future (Schoemaker, 1995). For a service firm, the commitments worth stress-testing are concrete: the lease, the senior hire, the niche concentration, the single channel that produces 70% of leads, the two clients that produce half of revenue. A scenario exercise that does not interrogate those five is entertainment.
Section 5
Innovative solutions
The scaled-down method keeps Shell's mechanism and discards Shell's overhead. Innovation one: the two-by-two compression. Schoemaker's full process identifies many uncertainties; the small-firm version selects the two most consequential and least predictable, demand regime and capacity economics for most service firms, and crosses them into four futures in an afternoon (Schoemaker, 1995). Innovation two: assumption bounties. Before drafting scenarios, each team member writes the three assumptions the business most depends on; the scenario day pays out by falsifying at least one, operationalizing Wack's perception-change mechanism (Wack, 1985). Innovation three: commitment stress-tests replace narrative polish. Each existing commitment gets a survive, adapt, or fail rating in each future; effort goes into the ratings, not the prose. Innovation four: tripwires with pre-agreed moves. Each scenario gets two or three observable leading indicators, pipeline conversion below a stated floor, a platform policy change, a key-client concentration breach, each tied to a decision the firm has already made in advance. This converts scenario output into decision velocity: when the tripwire fires, the firm executes rather than deliberates, which is exactly the readiness advantage Shell demonstrated in 1973 (Wilkinson and Kupers, 2013). Innovation five: the quarterly half-day refresh, which reviews tripwires and retires scenarios that reality has resolved, keeping the practice alive at a cost of four days a year.
Section 6
Solution framework
The One-Day Scenario System runs in four blocks. Block one, ninety minutes: frame the focal decision. Scenarios serve a decision, so pick the live one, whether to make the senior hire, enter the new vertical, or re-platform the offer; Schoemaker's process begins by defining scope and timeframe for exactly this reason (Schoemaker, 1995). Block two, two hours: build the matrix. List the external forces that bear on the decision, separate predetermined elements from genuine uncertainties as Wack's method requires, select the two critical uncertainties, and draft four futures of one page each, plausible, divergent, and internally consistent (Wack, 1985). Block three, two hours: stress-test. Rate every major commitment and the focal decision in each future. Decisions that win in three or four futures are robust; decisions that win in one are bets and should be sized as bets. This is where the method joins the decision-velocity pillar: scenario work done this way speeds decisions up, because it replaces vague dread with a bounded set of futures and pre-evaluated responses. Block four, one hour: set tripwires and owners. Each future gets observable indicators, each indicator gets a named owner who monitors it monthly, and each tripwire gets its pre-committed response logged in the firm's decision log. Total cost: one day per quarter of focused attention.
Section 7
Evidence-based action plan
Week one: collect the raw material. Pull the trailing-24-month numbers that describe your demand regime, lead volume by channel, conversion rates, average engagement value, client concentration, and have each leader independently write the firm's three load-bearing assumptions. Independent written input before discussion reduces the noise and anchoring documented in group judgment research (Kahneman, Sibony and Sunstein, 2021). Week two: run the scenario day using the four-block structure: focal decision, two-by-two matrix, commitment stress-test, tripwires. Hold the team to Wack's standard, that the exercise succeeds only if it changes someone's mental model about a real commitment (Wack, 1985). Week three: integrate with the decision system. Enter every tripwire and pre-committed response into the decision log, assign monitoring owners, and reclassify any commitment the stress-test exposed as a one-future bet, resizing it accordingly. Week four: communicate and schedule. Brief the whole team on the four futures in plain language, because Shell's experience shows scenarios create value when they spread through the organization's conversations, not when they sit in a deck (Wilkinson and Kupers, 2013). Put the next quarterly half-day refresh on the calendar before the month ends. Within two quarters the firm should be able to point to at least one decision it made faster, and one loss it avoided, because the future that arrived had already been rehearsed. For adjacent evidence in this pillar, see [The Data-Driven Trap: Why Decision-Driven Analytics Beats Data-First Thinking for Operators](/blog/growth-data-driven-trap-decision-driven-analytics) and [Reversible vs Irreversible Decisions: The Bezos Type 1/Type 2 Framework and the Research Behind It](/blog/growth-reversible-vs-irreversible-decisions).