Scenario Planning for Provinces, a Two-Day Workshop Shape
Scenario planning done well is a serious discipline; scenario planning done badly is theatre. Between the two extremes sits the practical middle: a well-designed workshop that produces internally-consistent scenarios, wind-tunnels current strategy against them, and hands the participating team a small number of decisions and monitoring commitments to work with.
This piece sits under the m5 pillar on strategic futures for boards and public leadership. It sets out a two-day workshop shape that works for a provincial planning team, based on the format used in the Western Cape Strategic Infrastructure Intent (2026 to 2050) and comparable engagements.
Who this is for
The audience is a provincial or municipal planning team of ten to twenty senior officials, joined by two or three external practitioners. The workshop is not a public engagement; it is a working session for the team responsible for the province's strategic infrastructure planning. Public engagement happens separately, after the workshop has produced draft scenarios that public engagement can validate and refine.
The workshop is not appropriate for boardroom scenario planning at a corporate level; that has a different audience, different outputs, and different workshop shape. See the m5 pillar for the boardroom equivalent.
Preparation before the workshop
Three preparation streams matter before the workshop opens.
A driver-scan pre-read. Prepared by the facilitators, this is a 10-to-15 page document identifying the drivers most likely to shape the province's environment over the planning horizon. The pre-read is not a set of conclusions; it is a curated set of inputs the team can react to and challenge. The document should reference primary sources for each driver so the team can go deeper if they want to.
Existing strategy artefacts. The team's current strategic plan, the current infrastructure pipeline, and the current fiscal envelope should be gathered so the workshop can wind-tunnel these against the emerging scenarios. Without the existing artefacts, the scenario work floats free of the planning it is supposed to inform.
Room and format. The workshop needs a room with wall space for scenario logic diagrams, breakout space for small-group work, and connectivity for referencing primary source material during discussion. Zoom-only formats can work for follow-up sessions but not for the core two-day workshop; the workshop produces its value through the sustained conversation the physical setting supports.
Day one, drivers and scenario logics
Day one focuses on establishing the drivers and building scenario logics from them.
Morning session one, driver review. The facilitators walk through the pre-read drivers. The team adds, removes, and modifies the drivers based on their own knowledge of the environment. The output is a curated list of typically 15 to 25 drivers, each with a short definition and a source reference.
Morning session two, driver classification. The drivers are classified by materiality (how much would a change in this driver affect the province's strategic position) and uncertainty (how uncertain is the direction the driver is moving). The classification produces a four-quadrant map: high-materiality-high-uncertainty drivers are the ones that will shape the scenario logic; high-materiality-low-uncertainty drivers are the ones that operate through the base case; low-materiality drivers are noted but not central to the scenario work.
Afternoon session one, scenario logic. The team selects two drivers from the high-materiality-high-uncertainty quadrant to define the scenario axes. The two axes produce four scenarios; the team develops a short logic statement for each scenario describing what the world looks like in that quadrant.
Afternoon session two, scenario narratives. The team develops a short narrative (typically one page) for each scenario, describing the pathway from today to the scenario end-state, the pace of the pathway, and the specific characteristics of the scenario world.
Day two, wind-tunnelling and outputs
Day two focuses on testing current strategy against the scenarios and producing the artefacts the team will use afterwards.
Morning session one, wind-tunnel. The team reviews the current strategic plan and the current infrastructure pipeline against each of the four scenarios. For each scenario, the team asks: which elements of our current plan hold up under this scenario? Which elements need to change? What new elements do we need? The output is a set of scenario-specific commentary on the current plan.
Morning session two, robust strategies and options. The team identifies elements that hold up across all four scenarios (robust strategies) and elements that only make sense under specific scenarios (options that need triggers). The robust strategies get funded now; the options get monitored and triggered if the environment moves toward the relevant scenario.
Afternoon session one, monitoring signals. For each scenario, the team identifies the specific signals that would indicate the environment is moving toward that scenario. The signals become the driver-tracking commitment coming out of the workshop; the team commits to monitoring them and reporting on them through the ongoing planning cadence.
Afternoon session two, artefact commitment. The workshop closes with a specific set of artefacts the team commits to producing: the scenario document, the wind-tunnel commentary, the robust strategies summary, the options and triggers list, and the signal-monitoring plan. Each artefact has a named owner and a delivery date within the following four weeks.
The artefacts
The five artefacts produced by the workshop are the tangible outputs the team uses afterwards.
The scenario document (typically 15 to 25 pages) describes the four scenarios in detail: the drivers, the logic, the narratives, the pathway from today. This document is the reference point for all subsequent scenario-related conversations in the team.
The wind-tunnel commentary (typically 5 to 10 pages) records the team's assessment of the current strategy against each scenario. This document is used in subsequent strategy discussions to remind the team of the exposures and opportunities they identified.
The robust strategies summary (typically 2 to 3 pages) identifies the elements of strategy that hold up across all scenarios. These are the elements the team can commit to now with confidence.
The options and triggers list (typically 3 to 5 pages) identifies elements that only make sense under specific scenarios, and specifies the signals that would trigger them. This document keeps the team's attention on the options that are not yet time to fund.
The signal-monitoring plan (typically 2 to 3 pages) sets out the signals the team commits to tracking, the frequency of the tracking, and the reporting mechanism. This document is the discipline that keeps the scenario work alive after the workshop.
Embedding the outputs
The workshop's value depends on what happens afterwards. Three embedding mechanisms are essential.
Quarterly signal reviews. The team reviews the signal-monitoring plan quarterly. Where signals indicate movement toward a scenario, the team assesses whether options should be triggered and reports the assessment to the political leadership.
Annual scenario refresh. The team refreshes the scenarios annually against the changing environment. Some drivers move faster than expected; some slower. The refresh keeps the scenarios current.
Integration with strategic planning cycles. The next round of strategic planning cross-references the scenario outputs. Robust strategies are prioritised; options are recorded with their triggers; monitoring signals appear in the planning cycle's tracking artefacts.
Without these three mechanisms, the scenario work sits on a shelf and the workshop was a two-day expense that produced no ongoing value. With them, the workshop is the beginning of a ongoing strategic futures discipline.
Common workshop failure modes
Three failure modes recur in scenario workshops.
Facilitator dominance. Where the facilitators drive the workshop rather than the team, the outputs reflect the facilitators' views rather than the team's. The team does not commit to the outputs because they do not feel like the team's work. Facilitators should structure the workshop but let the team do the substantive thinking.
Politeness over challenge. Where the workshop culture is too polite, the driver debate and the scenario logic debate stay at surface level. Genuinely challenging scenarios are harder to develop in a polite environment. Facilitators should push for disagreement and let the disagreement produce the scenario logic.
No follow-up. Where the embedding mechanisms are not established, the workshop ends and nothing follows. The team's time was spent producing artefacts they do not use.
Cross-jurisdictional considerations
The workshop shape described is oriented to a South African provincial context. Comparable adaptations work for other African provincial or state-level teams, for national planning teams, and for municipal planning teams in the larger metros. The pre-read, the drivers, and the wind-tunnel content adapt to the jurisdiction; the workshop shape holds.
What good looks like
A well-run workshop produces internally-consistent scenarios grounded in defensible drivers, wind-tunnels the current strategy against them, and hands the team a small set of decisions and monitoring commitments. The team feels ownership of the outputs and follows through on the embedding mechanisms. Six months later, the team is still working with the scenarios.
A poorly-run workshop produces scenarios the team does not commit to, wind-tunnel commentary that does not affect the strategy, and monitoring commitments that are not honoured. Six months later, the team has forgotten the workshop happened.
The CentraSolve Strategic Futures module supports the workshop workflow through the driver register, the scenario logic template, the wind-tunnel discipline, and the signal-monitoring plan.
References
Foundational literature
Van der Heijden, K. (2005). Scenarios: The art of strategic conversation (2nd ed.). Chichester: Wiley.
Ramirez, R., and Wilkinson, A. (2016). Strategic reframing: The Oxford scenario planning approach. Oxford: Oxford University Press.
Kahane, A. (2012). Transformative scenario planning: Working together to change the future. San Francisco: Berrett-Koehler.
Strategic futures sources
Adendorff, C. M. (2019). Infrastructure development scenarios for South Africa towards 2050. Prepared for the Presidential Infrastructure Coordinating Commission, Republic of South Africa.