Framework Foresight

Framework Foresight

Overview

Framework Foresight is a comprehensive strategic foresight methodology developed at the University of Houston's graduate foresight program. Originally created as "framework forecasting" in the late 1990s by Peter Bishop and later expanded by Andy Hines to include action-oriented elements, it provides a structured start-to-finish approach for exploring futures and their strategic implications.

The method classifies foresight information into templates arranged in a logical nine-step flow. It centers on developing a baseline future (most likely continuation of current trends) and alternative futures (plausible divergences), then extracting implications for strategy and action. Unlike ad-hoc forecasting, Framework Foresight is systematic, teachable, and designed for semester-length projects - meaning it balances rigor with practical completion timeframes.

What distinguishes Framework Foresight is its flexibility: it's a meta-framework that allows practitioners to plug in appropriate methods, techniques, and tools at each step. It provides structure without prescribing specific analytical techniques, making it adaptable across domains from technology forecasting to organizational strategy.

When to Use

• Conducting structured foresight projects with defined scope and timeline (3-6 months)
• Exploring futures for a specific domain, industry, technology, or organization
• Needing systematic approach rather than intuitive scenario generation
• Training teams in foresight methodology (designed for education)
• Balancing thoroughness with practical project completion constraints
• Integrating diverse foresight methods into coherent workflow
• Developing actionable strategic plans informed by multiple futures
• Creating comprehensive future-oriented knowledge artifacts for stakeholders

The Process

Step 1: Define the Domain

Scope the foresight inquiry - what system, industry, technology, or question are you exploring?

Example: "The future of remote work technologies and practices for knowledge workers, 2025-2035."

Step 2: Review the Recent Past

Examine last 5-10 years to understand trajectory and baseline. What changed? What stayed constant? What surprised experts?

Key questions: What trends are already established? What disruptions occurred? What historical context shapes stakeholder assumptions?

Step 3: Describe the Current State

Create comprehensive snapshot of the domain today - key metrics, stakeholder landscape, technologies, pain points, regulations.

Output: Baseline understanding that grounds future projections in reality.

Step 4: Identify Forces of Change (Drivers)

Catalog the forces pushing the domain toward different futures - technological, social, economic, environmental, political.

Technique: Use STEEP analysis, expert interviews, trend databases, weak signal scanning. Distinguish trends (directional movement) from drivers (underlying forces).

Step 5: Develop Baseline Future

Project the most likely future if current trends continue without major disruptions - this is NOT desired future or worst case, but extrapolation of established momentum.

Key insight: Baseline provides reference point. Most organizations only do this step, stopping before exploring alternatives.

Step 6: Develop Alternative Futures

Generate 2-4 plausible futures that diverge from baseline based on critical uncertainties or driver combinations.

Techniques: Scenario matrices (2x2), morphological analysis, wild cards. Alternatives should be meaningfully different, internally consistent, and plausible (not utopian/dystopian extremes).

Step 7: Analyze Implications

For each future (baseline + alternatives), extract strategic implications: opportunities, threats, decisions required, capabilities needed.

Output: "If this future unfolds, we should..." statements. This bridges futures thinking to strategy.

Step 8: Develop Plans and Actions

Create robust strategies that work across multiple futures or adaptive plans that specify triggers and branch points.

Deliverable: Actionable roadmap informed by foresight, not locked to single future.

Step 9: Monitor and Update

Establish ongoing scanning system to detect which future is emerging and update forecasts accordingly.

Mechanism: Horizon scanning, indicator tracking, periodic refresh cycles.

Example Application

Situation (University of Houston graduate students): Learn systematic foresight methodology through hands-on project.

Application: Semester project on "Future of Urban Mobility 2030-2040"

Execution:

• Domain: Personal transportation in cities >1M population
• Recent past: Uber/Lyft emergence (2010s), early EV adoption, COVID impact on public transit
• Current state: Mixed fossil/electric, ride-sharing established, autonomous testing, bike lanes expanding
• Drivers: Battery technology curves, climate policy, consumer preferences, urban density trends, autonomous vehicle regulation
• Baseline future: Gradual EV transition, human-driven ride-sharing dominant, incremental infrastructure improvements
• Alternative futures:
  • "Autonomous Abundance": Self-driving fleets achieve scale, personal ownership declines sharply
  • "Green Mandate": Aggressive carbon regulation forces rapid modal shift to bikes/transit/walking
  • "Suburban Resurgence": Remote work reverses urbanization, sprawl returns, car dependency increases
• Implications: For auto manufacturers, city planners, real estate developers, energy companies
• Plans: Develop flexible manufacturing (EVs + AVs), adaptive zoning policies, charging infrastructure scenarios

Outcome: Comprehensive foresight artifact demonstrating methodology mastery, applicable to client work.

Example Application 2

Situation (Corporate strategy team): Technology company needs 5-year strategic plan amid AI disruption.

Application: Framework Foresight project on "Enterprise Software AI Integration 2024-2029"

Execution (abbreviated):

• Drivers identified: LLM capability curves, regulatory responses, customer willingness to replace humans, compute cost trends, open-source vs. closed model dynamics
• Baseline future: Copilot-style augmentation becomes standard, human-AI collaboration, incremental workflow improvements
• Alternative futures:
  • "Agentic Automation": Multi-agent systems handle complex workflows end-to-end, jobs eliminated
  • "Regulation Slowdown": Privacy/liability concerns create compliance costs, AI advantage diminishes
  • "Commoditization Collapse": Open models achieve parity with proprietary, moats evaporate
• Implications: Different R&D priorities, talent strategies, pricing models for each future
• Strategic plan: Invest in both augmentation AND automation capabilities (hedge), build compliance infrastructure early, develop unique data moats independent of foundation models

Outcome: Leadership aligned on multiple plausible futures, strategy robust across scenarios rather than brittle single-future bet.

Anti-Patterns

• ❌ Skipping to alternative futures without understanding baseline (creates disconnected scenarios)
• ❌ Generating only extreme futures (utopia/dystopia) rather than plausible variations
• ❌ Stopping at Step 5 (baseline) and calling it "strategic foresight" (most common failure)
• ❌ Treating the framework as rigid checklist rather than flexible structure
• ❌ Failing to extract actionable implications - producing interesting futures with no strategic value
• ❌ Using single preferred method for all nine steps rather than selecting appropriate tools
• ❌ Creating so many alternative futures that stakeholders suffer analysis paralysis
• ❌ Ignoring baseline future because it seems "boring" compared to dramatic alternatives
• ❌ Treating futures as predictions to be proven right/wrong rather than tools for strategic thinking
• ❌ Never returning to monitor and update (Step 9), letting foresight grow stale

Related

• generic-foresight-process (Voros framework, similar systematic approach)
• iftf-foresight-insight-action (IFTF's three-phase methodology)
• three-horizons (complementary framework for managing transition between futures)
• scenario-planning (techniques used in Steps 6-7)
• backcasting-from-desired-futures (alternative approach starting from vision rather than drivers)