The Field of
Strategic
Foresight
A synthesis of forty years of scholarship, eight intellectual threads, and the practitioner implications for organizational decision-making
The field of strategic foresight is not a single discipline. It is a convergence. Scenario planning methodology developed at Royal Dutch Shell in 1985. Futures cone visualization formalized through three decades of scholarly refinement. The Oxford Scenario Planning Approach and its rigorous epistemology. UNESCO's Futures Literacy program. The ethnographic design tradition's participatory methods. A growing corporate foresight evidence base now spanning hundreds of organizations.
This synthesis traces eight intellectual threads running through 90 peer-reviewed articles and maps the point where they converge, and what organizational infrastructure they collectively require. That infrastructure is what ForesightOps names and what the Foresight Engine operationalizes.
The founding moment of practical scenario planning is not a textbook. It is two articles in Harvard Business Review, published in 1985 by Pierre Wack, the head of Shell's scenario team.
The first article, "Scenarios: Uncharted Waters Ahead," describes a problem that had no name in 1971 when Wack and his team began their work at Shell. The problem was not uncertainty itself. Organizations had always navigated uncertainty. The problem was the inability of decision-makers to update their mental models when the environment gave them information that contradicted what they already believed.
Shell's scenario team had identified in 1972, two years before the oil crisis, that the global oil market was entering a period of structural change. They built scenarios describing this change and delivered them to Shell's senior management. The scenarios were analytically sound. They were also completely ineffective. The managers read them, acknowledged the logic, and continued planning as they always had. The scenarios had changed nothing.
The second article, "Scenarios: Shooting the Rapids," describes what Wack's team did differently the second time. They stopped trying to inform managers and started trying to change the way managers saw. The scenarios were redesigned not as forecasts but as experiences. Carefully constructed narratives designed to make alternative futures feel real enough that managers could emotionally inhabit them, not just intellectually acknowledge them.
When the oil crisis arrived in 1973, Shell was the only major oil company that had prepared. Not because they had predicted the crisis. Because their mental models had been prepared to perceive it arriving.
Betty Flowers, writing in 2003, identified the element Wack had discovered that made scenarios work: narrative. A scenario is not an analysis. It is a story. Stories work differently in human cognition than logical arguments. They make possible futures inhabitable in the present, which is the only condition under which they can actually change behavior.
"The first scenario effort had changed what managers knew. The second changed how they saw. Only the second changed what they did."
The futures cone is the most recognized visual in foresight. It is also among the most misunderstood. Its forty-year lineage reveals that what appears to be a simple diagram is actually a compressed argument about epistemology, agency, and the nature of time.
The concept begins not with a cone but with Norman Henchey's 1978 taxonomy of futures: possible, plausible, probable, and preferable. These four categories do not describe types of events. They describe relationships between knowledge, evidence, and value. Four fundamentally different ways a future can be imagined from the present.
Charles Taylor translated this taxonomy into a visual form in 1990, creating what he called the "cone of plausibility" for his work on Alternative World Scenarios for Strategic Planning. The cone's geometry makes a claim: starting from the present moment, the space of what is imaginable expands as it moves further into the future. The further out you look, the wider the range of what could plausibly occur. Most planning happens inside a very narrow slice of this cone, the probable zone, while the most important strategic intelligence lives in the plausible and possible zones further from the center.
The cone lineage does not end with Christophilopoulos. Stuart Candy's work on Experiential Futures, and Dunne and Raby's speculative design practice, extend the cone's reach into design methodology. The cone gives foresight practitioners a spatial language for the futures they are working with. Speculative design and experiential futures give them tools for making those spaces inhabitable rather than merely imaginable.
Christophilopoulos applies Special Relativity to the futures cone, arguing that the cone expands in both directions. Multiple futures, yes. But also multiple pasts. The present is not a fixed point of departure. It is itself an interpretation.
Börjeson et al.'s 2006 typology of scenario types, predictive, explorative, and normative, maps onto the cone's zones with precision. Most planning uses predictive scenarios, which work within the Probable zone. Strategic foresight requires explorative and normative scenarios, which work in the Plausible, Possible, and Preferable zones. The choice of scenario type is not a technical preference. It is a fundamental decision about what kind of strategic thinking an organization is capable of.
"The present is not a fixed point of departure. It is itself an interpretation, shaped by which past we choose to understand as having led to it."
The Oxford Scenario Planning Approach gives the field its most rigorous epistemological foundation. Where Wack identified the problem empirically, scenarios that inform don't work while scenarios that transform do, Ramírez and Wilkinson explain why.
The central diagnosis is frame rigidity. A frame is the mental model through which a decision-maker perceives and interprets incoming information. Frames are not conscious. They are the taken-for-granted assumptions about how the world works that determine which information is noticed, how it is interpreted, and what responses it makes thinkable. Most organizational strategy failure is not a failure of intelligence. Organizations have access to relevant information. It is a failure of framing. The information arrives but cannot penetrate the existing frame. It is either ignored, dismissed, or reinterpreted to confirm what the frame already expects.
The TUNA framework is not a description of exceptional circumstances. It is a description of the permanent condition of organizational strategy-making. TUNA replaces VUCA, the military framework for volatile, uncertain, complex, ambiguous environments, with a more epistemologically precise formulation. Where VUCA describes what is happening, TUNA describes why traditional strategic planning fails to navigate it.
The OSPA's contribution to scenario methodology is the distinction between reframing and reperception. Reframing is cognitive. It means considering alternative ways of understanding a situation. Reperception is deeper. It is the moment when a genuinely new frame becomes operative, when the decision-maker does not just know that the world could be different but actually sees it differently. Reperception changes behavior. Reframing, like scenario documents that inform without transforming, often does not.
The OSPA also distinguishes between the transactional environment, the space of stakeholders and actors that an organization can directly influence, and the contextual environment, the broader operating context that cannot be directly influenced but must be understood and navigated. Most organizational planning focuses almost exclusively on the transactional environment. Strategic foresight is primarily concerned with the contextual environment, where the structural forces that will reshape the transactional environment in five to ten years are already visible to those who know how to look.
MacKay and Stoyanova's 2016 work augments the OSPA with sociological methods, extending scenario planning beyond its economic and political roots to incorporate cultural, social, and institutional dynamics that economic models cannot capture. This is particularly relevant for community-based foresight, where the forces shaping an institution's future are often sociological rather than economic.
"The organization becomes most blind precisely when accurate perception matters most. Under TUNA conditions, frame-rigid sensing channels filter out exactly the signals that would change the organization's view."
The most consequential claim in the Cicero reference list does not come from the scenario planning tradition. It comes from Riel Miller at UNESCO: futures literacy is a learnable organizational competency, not a specialized expertise.
Miller's Futures Literacy framework, developed through UNESCO beginning in 2007 and formally established through the Transforming the Future publication in 2018, defines futures literacy as the capacity to understand how and why we use the future to prepare, plan, and interact with complexity and novelty. This definition is more precise than it first appears. It does not define futures literacy as the ability to predict the future, or even to imagine multiple futures. It defines it as the ability to become aware of one's own anticipatory assumptions, to understand what images of the future are operating in the present, where they come from, and what they cause us to see and miss.
The practical instrument for building futures literacy in organizations is the Futures Literacy Laboratory (FLL). The FLL is a structured participatory process with a specific design principle that Miller identifies as essential: the demand for futures literacy must come from within the community, not be imposed from outside it. Organizations that are told they need futures literacy rarely develop it. Organizations that discover through their own experience that they lack it, because they are navigating a problem that their existing anticipatory assumptions cannot handle, become motivated to build it.
Mortensen, Larsen, and Kruse's 2021 research on barriers to developing futures literacy in organizations identifies the structural obstacles: time pressure that prevents reflective practice, cultural resistance to uncertainty, and the absence of leadership commitment to a process whose value is not immediately visible in quarterly metrics. These barriers are not technical. They are organizational. Solving them requires not better methods but a change in organizational culture and leadership orientation.
"The capacity to imagine multiple, diverse futures, and to use futures as lenses through which we look at the present anew, is a skill that can be cultivated. The question is whether organizations are willing to invest in cultivating it."
The most significant development in strategic foresight in the past decade is its convergence with design methodology. This convergence is not cosmetic. It is not about making scenario documents more visually appealing. It is about bringing a fundamentally different epistemology into the foresight process.
The convergence has a structural logic. Design thinking and strategic foresight share a core epistemological commitment: both use structured inquiry to expand the space of the thinkable before committing to action. Raford's 2015 process model maps this shared architecture precisely. Design thinking expands in the present, opening up the solution space by deeply understanding user needs before generating concepts. Strategic foresight expands in the temporal dimension, opening up the strategic option space by inhabiting alternative futures before making commitments. The two disciplines are not collaborating. They are doing the same thing along different axes.
The place where foresight and ethnographic research make direct contact is Ethnographic Experiential Futures (EXF), a four-phase framework developed by Candy and Kornet in 2019. This is the most important convergence point in the Cicero reference list.
The EXF cycle is, in structural terms, a rigorous hybrid of Contextual Inquiry and scenario planning. The Map phase is ethnographic inquiry, the same methodology I have practiced for thirty years. The Multiply phase is scenario development. The Mediate phase is experiential design. The Mount phase is community engagement. EXF is the scholarly validation of what ForesightOps does.
The convergence extends further into a concept that the design tradition calls "futurization," using design tools to make future states concrete and navigable, and its complement, "de-futurization," working backward from an imagined future to identify the decisions and conditions that would need to obtain in the present to make it reachable. Fu and Xia articulated this dual movement in their 2022 "Design Foresight" framework. The logic is backcasting, one of foresight's oldest methodological tools, now re-theorized through design epistemology.
Neither approach works as well alone as the two work together. Empirical research on business model innovation, published by Hall et al. in 2022, demonstrates that the combination of strategic foresight and human-centered design produces outcomes that neither discipline achieves independently. Foresight provides the temporal depth. Human-centered design provides the behavioral grounding. The intersection is precisely where ForesightOps operates.
The design tradition exists to correct a specific failure mode, and it has a name: the faster horses trap. Organizations that conduct customer research exclusively through structured questioning get answers shaped by what customers already know. They cannot surface the unarticulated needs and emerging behaviors that indicate where the market is actually going. Gordon, Rohrbeck, and Bjerre named this trap in 2019, and the name sticks because it describes what most organizations are doing right now. Asking customers to articulate the future using only the concepts of the present. Ethnographic and design-led foresight escapes this trap by observing behavior rather than eliciting opinion.
"Futures work begins by listening to how community members already imagine their future. Then it builds from those existing images rather than imposing externally constructed scenarios."
The Cicero reference list is heavy with empirical research. Not just theoretical frameworks, but large-scale studies of organizations that have implemented strategic foresight practice. The findings are consistent and striking.
The landmark finding is this: organizations with systematic internal foresight infrastructure consistently outperform those without it on strategic decision quality, and this performance advantage compounds over time. That is the result from a study of over 400 managers in large European companies, published by Rohrbeck and Schwarz in 2013. The organizations that have been practicing foresight for longer are more capable, not just more informed. The capability itself grows.
Three organizational capabilities distinguish the high performers. The ability to sense weak signals before they become visible in standard environmental scanning. The ability to translate those signals into strategic implications that decision-makers can act on. And the ability to integrate foresight insights into ongoing strategic planning cycles rather than treating them as one-off deliverables. A comprehensive 2015 review of corporate foresight by Rohrbeck, Battistella, and Huizingh established these as the structural requirements, and they hold across industries and organizational types.
But here is the practical problem: even good foresight fails to change decisions if it arrives at the wrong organizational level, at the wrong time in the planning cycle, or in the wrong format for the decision being made. Calof and Colton's 2024 research identifies seven structural barriers that prevent foresight insights from reaching the decision-makers who could act on them, and maps what organizational design can close those gaps. The translation problem is not primarily a communication problem. It is a structural problem. Better reports do not solve it. Only infrastructure that connects signal to decision at the right moment can.
The concept that makes the most direct connection to ForesightOps methodology is Strategic Customer Foresight, a framework developed by Schweitzer, Hofmann, and Meinheit that explicitly combines future orientation (how might customer needs and behaviors change?) with community grounding (what are specific groups of customers already experiencing?). It is distinguished from general strategic foresight by its behavioral specificity, and from consumer research by its temporal depth. The framework identifies "trend receivers," the visionary customers who sense where needs are heading before the mainstream. This is the academic foundation for the community researcher model: the people closest to behavioral change as the primary source of strategic signal.
Foresight does not automatically produce innovation. The connection between strategic foresight and business model innovation, as recent research by Moqaddamerad and Ali demonstrates, is mediated by two factors: sensemaking (the ability to interpret incoming signal in ways that reveal strategic implications) and organizational learning (the ability to incorporate those implications into ongoing decision-making). These two factors are not automatic outputs of foresight practice. They require organizational infrastructure to develop and sustain. Without that infrastructure, foresight insights remain stranded between observation and action.
"The translation problem is not a communication problem. It is a structural problem. Insights at the wrong level, wrong time, or wrong format will not change decisions regardless of their quality."
Every strategic plan is built on assumptions. Most organizations cannot name theirs. The thread of scholarship that addresses assumption-based planning is the most directly applicable to organizational decision quality, and the most underutilized in practice.
The assumptions that destroy strategic plans are almost never the ones that planners know they are making. Dewar's Assumption-Based Planning framework, the most systematic treatment of this problem, sorts planning assumptions into three categories: assumptions that are load-bearing (the plan fails if they are false), assumptions that are vulnerable (they could plausibly turn out to be wrong within the planning horizon), and assumptions that are both, load-bearing and vulnerable simultaneously. The third category represents the organization's highest strategic risk. These are the assumptions doing the most work in the plan while being the most exposed to the environment. And in most organizations, they were never made explicit.
The assumption problem gets worse at the level of industry structure. An organization competing for today's market while its industry is being restructured is operating on the wrong set of assumptions entirely. Hamel and Prahalad made this argument in 1994, and it has only gotten sharper with time. The most dangerous assumptions are not the ones that are wrong about details. They are the ones that are wrong about the strategic game being played. Foresight's function, in this frame, is to help organizations see the game before it shifts.
There is a cognitive science dimension to this. Anticipatory thinking, as Klein describes it in his work on military and organizational preparedness, is the active practice of imagining future states before they arrive. Not to predict outcomes, but to prepare cognitive structures that can recognize relevant patterns when they emerge. Organizations that practice anticipatory thinking systematically are less surprised not because they predict more accurately but because they have already encountered, in imagination, the range of conditions they might face. The preparation is not informational. It is perceptual.
The most direct connection between the assumption problem and ForesightOps methodology comes from a finding that sounds simple and has enormous consequences: contextual insight is an antecedent to strategic foresight. The quality of scenario planning is bounded by the quality of the environmental observation that precedes and feeds it. Mastio and Dovey established this empirically in 2021. Organizations with thin or biased observation processes build scenarios that are systematically constrained by the assumptions embedded in that observation. The sensing gap is not just a gap in the strategic planning process. It is a gap in the observation infrastructure that strategic planning depends on.
"Foresight without sensing infrastructure is assumption-recycling, not scenario planning. The quality of what you can imagine is bounded by the quality of what you can observe."
Seventeen articles in the Cicero reference list do not belong to a single thread. They span multiple traditions simultaneously, and that is precisely their value. They are where the field stops being seven separate conversations and starts becoming one.
Foresight infrastructure works across institutional types, not only in corporations. A comparative study of strategic foresight in public policy across the UK, Singapore, and the Netherlands, conducted by Habegger in 2010, demonstrates that the practices producing strategic advantage in the private sector produce governance advantage in the public sector. The mechanism is the same: continuous environmental observation connected to decision-making before commitments are locked in.
The field also carries a limitation embedded in its own origins. The scenario planning tradition that began at Shell was developed by and for Western industrial organizations navigating geopolitical uncertainty. When foresight methods are applied to communities with different cultural relationships to time, tradition, and collective identity, the methods themselves need to be reimagined. Bisht's 2019 work on decolonizing futures confronts this directly. Whose futures count is not a neutral question. The participatory turn in foresight methodology, from Miller's Futures Literacy Laboratories through Candy and Kornet's EXF, is partly a response to this challenge.
Stories keep coming back to the center of this work, and there is a reason for that. In technology foresight specifically, story-based methods surface implications that purely technical assessment misses because they force consideration of how technologies will be experienced by actual people in actual contexts. The argument, developed by Marshall et al. in their 2022 work on story thinking, runs parallel to Flowers's observation about Wack: stories do cognitive work that analysis cannot. The methodology closes the gap between what a technology can do and what it will mean.
What the cross-cutting literature establishes is that the seven threads are not seven separate arguments. They are seven articulations of a single structural claim: organizations need continuous, behaviorally grounded, participatory sensing infrastructure that connects what is happening in the environment to what decisions are being made. The threads differ on vocabulary. They differ on entry point. They converge on the infrastructure requirement.
What the Field
Has Converged On
Across ninety peer-reviewed articles, five years of daily reading, and eight distinct intellectual traditions, the field of strategic foresight has reached consensus on eight foundational claims. These are not contested propositions. They are the settled floor of the discipline, the things the scholarly community agrees on, even when practitioners have not yet caught up with them.
What the field has not converged on is the infrastructure required to make these eight claims operational at organizational scale. That is the gap. That is what ForesightOps names.
The Gap the Field
Cannot Close Itself
Eight foundational claims. Forty years of scholarly consensus. A growing empirical evidence base. Practitioner toolkits from Oxford, UNESCO, and Carnegie Mellon. A design tradition that has built the bridge between foresight methodology and human-centered research practice. The field of strategic foresight is mature, rigorous, and increasingly evidence-based.
And still, most organizations do not have continuous foresight capability. Not because the methodology is too complex, or too expensive, or too specialized. Because the field has built excellent episodic tools and has not yet built the operational infrastructure to make them continuous. Every engagement ends. Every research report circulates and then stops circulating. Every scenario set ages until it no longer describes the world it was built to illuminate.
The eight claims above collectively point to a single infrastructure requirement: an organization needs a continuous, behaviorally grounded, bias-aware observation system that surfaces signal from the Plausible and Possible zones of the futures cone, translates that signal into strategic intelligence before commitments are made, and builds internal capability that persists after any external engagement concludes.
The Cicero Challenge is the proof of a different approach. Ninety articles. Five years. Daily reflection, not as a consulting deliverable, not as a report, but as a daily practice of deepening the discipline. The organization that reads one article each day and writes one reflection does not need a scenario consultant every three years. It has built something more durable: a genuine intelligence orientation, continuously fed, continuously refined.
That is what ForesightOps operationalizes. Not the wisdom of a single engagement. The compounding advantage of continuous organizational learning about the futures that matter.