01 — PurposeWhy We Need This
The bank already tracks disruption. Daily briefings scan signals across nine strategic lenses, scoring their intensity and momentum. Weekly syntheses join the dots. But there is a structural gap between knowing what happened this week and understanding what it means for the next decade. The Foresight Engine bridges that gap.
Most organisations approach the future as a complicated problem to be solved — throw enough data and expertise at it, and the answer will emerge. But the future is complex, not complicated. Outcomes are emergent and only apparent in hindsight. Cause and effect relationships are not fully understood or even knowable in advance. The Cynefin framework makes this distinction clear: complicated problems reward expert analysis; complex problems reward exploration, divergent thinking, and the ability to hold multiple plausible outcomes simultaneously.
Strategic foresight is not forecasting. Forecasting asks "what will happen?" and attempts to answer with precision. Foresight asks "what could happen?" and prepares for multiple possibilities. As the Copenhagen Institute for Futures Studies frames it: the future unfolds in a friction field between drivers pushing change forward and turners and blockers slowing or redirecting it. The outcome depends on this power struggle, and the implications for the bank flow from understanding it — not from picking a single trajectory and betting the strategy on it.
The Foresight Engine connects the two. It takes the daily intelligence we already produce, layers analytical rigour on top of it, and creates a living, proprietary knowledge base that informs strategic decisions across innovation, product, and strategy teams.
02 — ArchitectureFour Layers of Foresight
The Engine operates across three analytical layers and one translation layer. The analytical layers correspond to different time horizons. Information flows upwards from signals to scenarios, and insight flows back down — scenarios inform which signals to watch; trends tell us which scenarios are becoming more plausible. The Customer Impact Layer runs vertically through all three, grounding abstract analysis in the lived experience of the bank's customers.
Scenario Canvas
Named plausible futures, constructed from converging trends, stress-tested against strategic priorities. Refreshed quarterly. Each scenario explores what the banking landscape could look like if specific forces dominate — drawing from the futures cone to map possible, plausible, and preferable outcomes.
Output: 3–4 named scenarios per strategic theme, with implications mapped to business units.
Trend Registry
Persistent, named patterns of change that emerge when signals cluster and recur. Each trend is scored on three dimensions (velocity, impact, maturity), tagged to strategic lenses, and tracked monthly. This is the proprietary knowledge base — no one else has this, because no one else is scanning through our specific lenses with our specific strategic context.
Output: Living registry of 40–80 scored trends, updated monthly, with trajectory calls.
Signal Scanner
The daily intelligence operation. Raw signals captured from newsletters, influencers, prediction markets, regulatory filings, and patent databases. Each signal is classified by type, scored for intensity (Zeitgeist Score), and tagged to one or more of 12 strategic lenses. This is where new information enters the system.
Output: Daily briefings, weekly syntheses, rolling data tracker.
The Customer Impact Layer
Running vertically through all three analytical layers is the Customer Impact Layer — five banking archetypes that translate every signal, trend, and scenario into concrete human consequences. Without this layer, foresight remains intellectually stimulating but strategically inert. With it, a product manager can read a scenario and immediately understand what it means for their customers. The five archetypes are defined in Section 06.
03 — Layer 1The Signal Scanner
The Signal Scanner is the foundation — the always-on intelligence operation that feeds everything above it. It already exists in the form of the daily strategic briefings. The methodology upgrade adds three enhancements: signal typing, an expanded lens set, and formalised graduation criteria.
Signal Classification (CIPHER Framework)
Inspired by the Future Today Institute's CIPHER model, every signal captured in the daily scan is classified by type. This matters because not all signals carry the same weight. A new scientific breakthrough (Rarity) demands different attention from a workaround that early adopters are inventing (Hack). Classification helps prioritise and helps spot when multiple signal types converge on the same theme — which is a strong indicator that a trend is forming.
| Type | Definition | Example |
|---|---|---|
| Contradiction | A development that challenges prevailing assumptions or norms | A major bank shutting its innovation lab while doubling AI spend |
| Inflection | An idea, behaviour, or technology spreading rapidly across domains | AI agents moving from consumer novelty to enterprise procurement |
| Practice | An emerging behaviour gaining traction among early adopters | Gen Z using social platforms as primary financial planning tools |
| Hack | A clever workaround exploiting gaps in current systems | Stablecoin rails being used for cross-border payroll |
| Extreme | An outlier experiment pushing boundaries of what's possible | Quantum-resistant encryption deployed in a live payment system |
| Rarity | A novel invention or discovery with no precedent | A fundamentally new consensus mechanism for distributed ledgers |
The 12 Strategic Lenses
The existing nine lenses are retained and three new lenses are added to close gaps identified through PESTLE and STEEPV analysis. The new lenses cover forces that are already reshaping banking but were not previously tracked with dedicated focus.
Enhanced Signal Scoring
Each signal retains its existing Zeitgeist Score (1–10) and status label (NEW, HEATING, HOT, COOLING, DORMANT). The following additional metrics are added to enable richer analysis and trend graduation:
| Metric | Scale | What It Captures |
|---|---|---|
| Convergence Count | 1–12 | Number of lenses touched. Multi-lens signals (3+) are systemically significant. |
| Institutional Commitment | None / Exploratory / Committed / Dominant | Is there capital behind this? Investment, M&A, patent filings, strategic references in annual reports. |
| Regulatory Proximity | Distant / Proposed / Imminent / Active | How close is regulation? Distant = thought leadership only. Active = enforceable rules in place. |
| Counter-Signal Strength | Weak / Moderate / Strong | The friction field: what forces are working against this signal? Borrowing from CIFS: turners and blockers matter as much as drivers. |
| CIPHER Type | C / I / P / H / E / R | Signal classification per the CIPHER framework above. |
04 — Layer 2The Trend Registry
The Trend Registry is the proprietary core of the Foresight Engine. It is where signals graduate into named, scored, trackable patterns of change — and where the bank builds institutional knowledge that compounds over time.
What Is a Trend (and What Isn't)
A trend is not a single event or data point. It is a persistent pattern of change with discernible direction and momentum. For a signal to graduate to trend status, it must meet at least three of the following five criteria:
1. Persistence — The signal has appeared across 3+ daily briefings within a 30-day window.
2. Breadth — It touches 2+ strategic lenses (convergence count ≥ 2).
3. Institutional traction — There is evidence of capital commitment (investment, patents, strategic announcements).
4. Behavioural evidence — Consumer or enterprise behaviour is shifting, not just commentary or speculation.
5. Structural implication — It has identifiable second-order consequences for the banking value chain.
Trend Scoring: The VIM Model
Every trend in the registry is scored across three dimensions — Velocity, Impact, and Maturity. Together these form the VIM Score, which enables prioritisation, comparison, and tracking over time. The model borrows from Foresight Factory's dual-axis approach but adds a banking-specific impact dimension.
| Dimension | Scale | Assessment Criteria |
|---|---|---|
| Velocity | 1–5 | 1 = Decelerating (losing momentum, coverage declining) 2 = Stable (consistent but not growing) 3 = Moderate acceleration (growing steadily) 4 = Rapid acceleration (multiple signals converging, capital flowing) 5 = Exponential (breakthrough pace, market-defining momentum) |
| Impact | 1–5 | 1 = Peripheral (affects niche segments, limited value chain exposure) 2 = Moderate (affects one business line or customer segment) 3 = Significant (affects multiple business lines or creates new competitive dynamics) 4 = Structural (requires strategic response, reshapes how we compete) 5 = Transformative (redefines the industry, existential if ignored) |
| Maturity | Stage | Emerging (1–3) = Early signals, limited institutional adoption, high uncertainty Developing (4–6) = Growing evidence, some institutional commitment, direction clearer Maturing (7–8) = Widespread adoption underway, regulatory frameworks forming Established (9–10) = Mainstream, embedded in business-as-usual |
The Priority Matrix
Plotting Velocity against Impact creates a four-quadrant view that drives resource allocation:
High Impact + Low Velocity = WATCH & PREPARE — Structural but slow-moving. Build optionality.
Low Impact + High Velocity = MONITOR — Moving fast but limited strategic weight. Could escalate.
Low Impact + Low Velocity = LOG — Background. Review quarterly. May be a weak signal of something larger.
VIM Calibration Protocol
Subjective scoring is a known weakness in foresight frameworks — it risks embedding existing biases into the system. To mitigate this, every VIM score must be anchored to at least one external data point. This does not eliminate judgment, but it makes the judgment transparent and contestable.
| Dimension | Anchor Data Required | Source |
|---|---|---|
| Velocity | At least one of: VC funding growth rate (YoY), patent filing acceleration, Google Trends velocity, GitHub star growth, or adoption curve data | Crunchbase, Lens.org, Google Trends, GitHub, industry reports |
| Impact | At least one of: addressable market size, regulatory scope (number of jurisdictions), affected customer base estimate, or value chain disruption breadth | Industry reports, FCA/PRA registers, internal customer data |
| Maturity | Mapped to a defined readiness scale: number of live deployments in banking, regulatory framework status (none / consultation / enacted), or technology readiness level (TRL 1–9) | Case studies, regulatory pipeline, vendor landscape scans |
Scores that cannot be anchored to any external data point should be flagged with a confidence marker (Low / Medium / High). Over time, this creates a self-correcting system: low-confidence scores get prioritised for deeper research at the next monthly review.
Causal Layered Analysis
Drawing on Sohail Inayatullah's Causal Layered Analysis framework, each trend in the registry includes a depth assessment across four layers. This prevents the Foresight Engine from operating purely at the surface level of observable events — and forces us to interrogate the structural and ideological forces underneath.
| Layer | Question | Example (Stablecoin Payment Rails) |
|---|---|---|
| Litany | What is observable? What are the facts and events? | Visa-Bridge launches stablecoin cards in 100+ countries. Circle IPO valued at $9B. UK consults on stablecoin regulation. |
| Systemic causes | What social, economic, or political structures produce this? | Cross-border payment friction (3-5 days, 6% fees). Correspondent banking consolidation. Dollar shortage in emerging markets. Programmable money reducing settlement risk. |
| Worldview | What assumptions, values, or discourse enables or resists this? | The belief that money should be fast, programmable, and borderless — versus the incumbent view that trusted intermediaries are essential for financial stability. |
| Myth / metaphor | What deep narrative or cultural archetype is at play? | The "democratisation" narrative: technology as liberator from gatekeepers. Counterbalanced by the "too big to fail" narrative: systemic institutions as essential safety nets. |
Not every trend requires deep CLA analysis at first registration. But any trend scoring VIM Impact ≥ 4 should have CLA completed within one review cycle. The systemic and worldview layers are particularly valuable for scenario construction, because they reveal the fault lines along which futures diverge.
Registry Operations
The trend registry is maintained in a structured spreadsheet with monthly scoring reviews. Each trend record includes: a unique ID, trend name, description, primary lens, secondary lenses, VIM scores with anchor data (current and previous month), maturity stage, trajectory call (strengthening/stable/weakening), CLA depth assessment, customer archetype impacts, the date it was first identified, the signals that feed it, and strategic implications for the bank.
A monthly review cycle — ideally a 60-minute session with the innovation and strategy teams — recalibrates scores against anchor data, reviews CLA depth layers for high-impact trends, graduates new trends from the signal layer, retires trends that have reached "established" status or faded, and identifies convergences between trends that may warrant scenario exploration.
05 — Layer 3The Scenario Canvas
The Scenario Canvas is where foresight becomes strategic. It takes the strongest, most consequential trends from the registry and asks: if these forces play out together, what does the banking landscape look like in 2035?
This is not prediction. It is structured imagination — creating windows into plausible futures that challenge assumptions, reveal blind spots, and surface strategic questions the bank should be asking now.
Scenario Construction Method
The approach draws on CIFS's friction field model and the three horizons framework. For each strategic theme (e.g. "the future of payments" or "the future of financial advice"), the process follows four steps:
Scenario Design Principles
Good scenarios are not good news and bad news — they are genuinely different futures. Drawing from the CIFS methodology:
Plausibility over probability. We are not ranking likelihoods. Each scenario should be credible enough that a reasonable person could argue for it. The futures cone teaches us that the further out we look, the wider the outcome space. Our job is to populate that space usefully, not narrow it prematurely.
Challenge, don't comfort. At least one scenario should make the room uncomfortable. If every scenario validates current strategy, the exercise has failed. As CIFS notes, organisations should not engage in foresight to find certainty — they should engage to challenge the assumptions that create a false sense of certainty.
Name them memorably. Scenarios need to become part of the team's working vocabulary. A scenario called "Fragmented Trust" is more useful than "Scenario B" because it can be referenced in strategy discussions, product reviews, and risk assessments.
Connect back to signals. Each scenario should identify its leading indicators — specific signals from Layer 1 that would suggest this future is becoming more plausible. This creates a live connection between daily intelligence and long-term strategic thinking.
The Wild Card Scenario
The 2×2 matrix is a useful tool, but it has a known limitation: it only accommodates two variables and can produce scenarios that are too neat. To address this, every scenario set includes an explicit fifth scenario — the Wild Card — that breaks the matrix. This is the "what if the question itself is wrong?" scenario: an outcome that neither axis anticipated, driven by a force outside the current framing. Wild cards are drawn from the Left Field lens, from CLA myth-layer disruptions, or from cross-scenario convergences that the matrix misses.
The Wind Tunnel
Individual scenario stress tests are valuable, but the greatest strategic insight comes from testing current strategy against the full set simultaneously. The Wind Tunnel is a structured exercise run after each scenario set is completed:
1. Identify robust moves — strategic actions that are valuable across 4+ of the 5 scenarios (including the wild card). These are the highest-priority investments because they pay off regardless of which future materialises.
2. Identify fragile bets — strategic positions that only succeed in one or two scenarios. These are not necessarily wrong, but they are concentrated risk and should be acknowledged as such.
3. Identify option-creating moves — low-cost actions that preserve the ability to pivot if a specific scenario gains plausibility. These are the foresight equivalent of buying insurance.
4. Map the trigger points — for each fragile bet, identify the specific leading indicator that would signal it's time to pivot. This connects scenario planning directly to operational decision-making.
Customer Archetype Impact
Every scenario must include a persona impact section answering, for each of the five banking archetypes defined in Section 06: how does this future feel for this customer? What changes in their behaviour, needs, and relationship with the bank? This is what converts abstract foresight into something product and strategy teams can act on. A scenario that says "embedded finance disrupts distribution" is less useful than one that says "Sarah (Mass Retail) now gets her mortgage through her employer's benefits platform and has no reason to visit a bank website."
06 — Customer ArchetypesThe Human Layer
Foresight that cannot be translated into customer impact is foresight that will not be acted on. The Customer Impact Layer defines five banking archetypes that run through all three analytical layers — grounding signals, trends, and scenarios in the lived experience of real people.
These are not marketing personas. They are strategic archetypes — simplified representations of distinct banking relationships that differ in their needs, behaviours, risk profiles, and exposure to disruption. Each archetype responds differently to the same trend: autonomous AI agents might delight a digitally fluent retail customer while alarming a relationship-dependent wealth client.
The Five Archetypes
| Archetype | Profile | Disruption Exposure | Key Needs |
|---|---|---|---|
| Mass Retail "Sarah" |
Individual consumer. Current account, savings, mortgage, insurance. Digital-first, price-sensitive, convenience-driven. Increasingly expects platform-level experiences from banking. | High. Most exposed to embedded finance, AI-driven switching, neobank migration, and platform disintermediation. The archetype most likely to experience banking through a non-bank interface within 5 years. | Simplicity, speed, transparency, value. Wants banking to be invisible — something that works in the background rather than demanding attention. |
| SME / Business "James" |
Small-to-medium enterprise owner. Business account, working capital, payments, FX. Time-poor, relationship-dependent for complex needs, self-serve for routine transactions. Underserved by most banks. | Moderate-to-high. Exposed to fintech lending, accounting platform integration, cross-border payment disruption, and AI-powered financial management. The archetype most likely to unbundle banking relationships across specialist providers. | Cash flow visibility, speed of decisions, integrated tools, human support for complex moments. Wants the bank to understand their business, not just their balance. |
| Corporate / Institutional "Priya" |
CFO or treasury function of a mid-to-large corporate. Complex banking needs: syndicated lending, derivatives, cash management, trade finance. Multi-bank relationships. Regulated and risk-conscious. | Moderate. Exposed to DeFi treasury management, tokenised securities, real-time settlement, and AI-driven risk management. Slower to move but the stakes are higher. The archetype where regulatory change has the most direct impact. | Certainty, control, counterparty trust, bespoke solutions. Wants a banking partner that understands their sector and can structure solutions, not just execute transactions. |
| Wealth "David" |
High-net-worth or affluent individual. Investment portfolio, tax planning, estate management, philanthropy. Relationship-intensive, advice-dependent, generationally diverse (inheritors vs. creators). | Moderate. Exposed to robo-advisory, tokenised alternative assets, AI-powered financial planning, and intergenerational wealth transfer to digitally native heirs. The archetype where trust and personal relationships matter most — and where disruption feels most personal. | Trust, expertise, personalisation, discretion. Wants a human who knows them, supported by technology — not replaced by it. |
| Digitally Excluded "Margaret" |
Customers unable or unwilling to engage through digital channels. Elderly, low-income, rural, disability-affected, or simply preferring in-person interaction. Disproportionately reliant on branches and cash. Often invisible in innovation discussions. | Extreme — but inverted. Every trend towards digital, AI, and platform banking increases exclusion risk. The archetype that stress-tests whether innovation is genuinely inclusive or simply efficient. Regulatory and reputational exposure is significant. | Access, human contact, simplicity, dignity. Wants to be able to do basic banking without needing a smartphone, an app, or a password they cannot remember. |
How Archetypes Are Used
In the Signal Scanner (Layer 1): When a signal has particular relevance to one or more archetypes, this is noted in the daily briefing. A signal about "AI agents managing personal finance" is tagged to Mass Retail and Wealth. A signal about "branch closures accelerating" is tagged to Digitally Excluded.
In the Trend Registry (Layer 2): Each trend record includes a customer impact field mapping the trend's relevance and threat/opportunity profile against each archetype. This is reviewed monthly alongside VIM scores.
In the Scenario Canvas (Layer 3): Every scenario includes a persona narrative for each archetype — a short paragraph describing what this future feels like for Sarah, James, Priya, David, and Margaret. This is what makes scenarios actionable: a product manager reading "The Invisible Bank" scenario can immediately see that Sarah is delighted, David is anxious, and Margaret is locked out.
In the Quarterly Provocation: The provocation output specifically highlights which archetype is most at risk from the quarter's dominant trends — and asks whether the bank's current strategy adequately serves them.
07 — Operating CadenceHow the Engine Runs
The three layers operate at different speeds, but they feed each other continuously. The cadence is designed to be sustainable for a small team while building genuine institutional foresight over time.
Newsletters, influencer monitoring, prediction markets, verification. Produces the daily strategic briefing with Zeitgeist Scores and signal statuses across 12 lenses.
Cross-lens pattern detection, signal tracker updates, contrarian analysis. Produces the weekly synthesis. Flags signals for potential trend graduation.
60-minute team session. Recalibrate VIM scores, graduate new trends, retire fading ones, identify convergences. Update the registry spreadsheet.
Half-day workshop. Review existing scenarios against trend movements. Construct new scenarios for emerging strategic themes. Stress-test strategy.
The Signal-to-Scenario Pipeline
The following diagram illustrates how intelligence flows through the system:
The critical discipline is the feedback loop. Scenarios should change which signals we watch for. If a scenario posits a world where embedded finance has eliminated the branch network, the daily scan should be actively monitoring signals related to embedded finance adoption, branch footfall data, and regulatory attitudes to non-bank distribution. The scenarios set the watching brief; the signals test it.
08 — Data & SourcesWhat Else We Need to Track
The current scanning operation draws primarily from newsletters, influencer activity, and web research. To support the full three-layer methodology, the following additional data sources and metrics are recommended — organised by cost and effort.
Available Now (Free)
Build Internally (Proprietary Registry)
Low Investment Options
Future Consideration (Medium Investment)
Metrics We Are Not Yet Tracking (But Should)
Beyond the signal-level metrics introduced in Section 03, the following metrics would strengthen the system at the trend and scenario layers:
| Metric | Layer | Purpose |
|---|---|---|
| Patent velocity by theme | Trend | Tracks where innovation investment is concentrating. Rising patent activity in a theme = institutional conviction signal. |
| Funding trajectory | Trend | VC/PE investment volume and deal count by theme. Money follows conviction — this is a leading indicator of trend maturity. |
| Regulatory density | Trend | Count of consultations, proposals, and enacted regulations touching a trend. High density = trend is maturing and acquiring friction. |
| Scenario plausibility shift | Scenario | Quarterly reassessment: is this scenario more or less plausible than last quarter? Tracked directionally over time. |
| Strategic exposure score | Trend/Scenario | Which business lines are most exposed to this trend or scenario? Maps foresight to operational relevance. |
| Consumer sentiment index | Signal/Trend | Proxy measure using social listening, Google Trends, and survey data. Tracks whether a shift has reached public consciousness. |
| Cross-lens convergence index | Trend | Weighted count of how many lenses a trend touches, adjusted for signal strength. High convergence = systemic importance. |
09 — The HubDisruption Hub Architecture
The Disruption Hub operates as two structurally separated surfaces. This is a deliberate design choice: research consistently shows that organisations which don't separate tactical intelligence from strategic foresight end up with foresight colonised by the urgent. The daily signal is important, but it should not crowd out the long view.
Surface 1: Intelligence Hub (index.html)
The daily operational surface. This is where signal-level intelligence lives — the briefings, the Zeitgeist scores, the weekly synthesis, the data ticker. It is updated daily and optimised for current awareness. Its purpose is to answer: what happened and what does it mean this week?
Surface 2: Foresight Engine (foresight-engine.html)
The strategic surface. This houses the Trend Registry, the Scenario Canvas, the Customer Archetype impacts, and the Quarterly Provocations. It is updated monthly/quarterly and optimised for long-range strategic thinking. Its purpose is to answer: how might the world change, and what should we do about it?
The Intelligence Hub links to the Foresight Engine (and vice versa) but does not embed it. A compact teaser card on the hub provides at-a-glance Foresight Engine status — active trends, scenario count, latest provocation — and links through to the full foresight surface.
Combined Structure
| Section | Surface | Content | Update Frequency |
|---|---|---|---|
| Zeitgeist Dashboard | Intelligence Hub | 12-lens Zeitgeist grid with current scores, statuses, and rolling averages. Lead signal of the day. | Daily |
| Daily Briefings | Intelligence Hub | Latest briefing in hero position, recent in grid, archive table. HTML + PDF links. | Daily |
| Weekly Synthesis | Intelligence Hub | Latest weekly in prominent position. Convergence highlights, signal tracker, contrarian corner. | Weekly |
| Trend Registry | Foresight Engine | Full interactive table of all active trends with VIM scores, anchor data, CLA depth, trajectory calls, maturity stages, and archetype impacts. Sortable by any dimension. | Monthly |
| Scenario Canvas | Foresight Engine | Named scenarios with persona narratives, leading indicators, plausibility tracking, and wind tunnel results. Includes wild card scenario. | Quarterly |
| Customer Archetypes | Foresight Engine | Five archetype profiles with trend impact heatmap showing which trends affect which customers most. | Quarterly |
| Quarterly Provocation | Foresight Engine | One-page thought leadership piece designed to challenge current strategic assumptions. The uncomfortable question the organisation needs to hear. | Quarterly |
| Data Tracker | Intelligence Hub | Cumulative data points from daily briefings. Filterable by lens, date, trend. | Daily |
| Methodology | This document. The reference guide for the framework. | As needed |
10 — FoundationsStanding on Shoulders
The Foresight Engine draws on established academic and practitioner frameworks while adapting them for the specific context of a UK banking innovation function. The key intellectual debts are acknowledged here — both to give credit and to help team members who want to go deeper into the underlying thinking.
| Source | Contribution to the Engine |
|---|---|
| Copenhagen Institute for Futures Studies | Friction field model (drivers vs. turners/blockers), futures cone (possible/plausible/probable/preferable), Cynefin complexity framing, systems thinking approach to change |
| Future Today Institute (Amy Webb) | CIPHER signal classification framework, seven-step forecasting funnel, signal-to-trend graduation methodology, quantitative foresight rigour |
| Foresight Factory | Velocity/Impact/Maturity scoring model, three-ring trend hierarchy (macro → consumer → category), always-on commercial activity scanning approach, PESTLE macro driver framework |
| Bill Sharpe (Three Horizons) | Coexisting horizons framework — the insight that Horizon 3 elements are already present in Horizon 1 as "pockets of the future" |
| Pierre Wack (Shell) | The concept of reperception — using scenarios not to predict but to change how people think about the future |
| Voros (2003) | The futures cone taxonomy: possible, plausible, probable, preferable futures |
| Van Der Laan (2012) | The relationship between foresight and strategy — the framework for connecting foresight outputs to strategic decision-making |
| Sohail Inayatullah (Causal Layered Analysis) | Four-layer depth model (litany → systemic causes → worldview → myth/metaphor) for probing beyond surface-level trends. The insight that foresight operating only at the "litany" level reproduces existing assumptions rather than challenging them |
| Rafael Popper (Foresight Diamond) | Four knowledge sources for foresight (creativity, expertise, interaction, evidence). Methods Combination Matrix for selecting appropriate foresight techniques. The principle that robust foresight requires multiple evidence types, not just expert opinion |
| Peter Bishop (Framework Foresight) | Meta-method covering the full foresight lifecycle: framing → scanning → forecasting → visioning → planning → acting. The structured approach to connecting foresight outputs to organisational action |
11 — Proprietary EdgeWhat Makes This Ours
Frameworks are borrowed. Data is common. What creates proprietary value is the specific combination of lenses, the accumulated trend registry built through our daily scanning, and the institutional knowledge embedded in our scoring and scenario work over time.
The following elements are unique to this implementation and cannot be replicated by purchasing an off-the-shelf foresight platform:
Banking-specific lens architecture. The 12 lenses are calibrated for a UK bank's strategic concerns — not generic PESTLE categories, not consumer goods trend taxonomies. They reflect the specific intersection of technology, regulation, and consumer behaviour that defines our competitive landscape.
Cumulative trend registry. Every month of scoring adds a new data point to each trend's trajectory. After six months, we have a proprietary dataset showing how fast each force is moving, how our assessment has evolved, and where our early calls were right or wrong. This institutional memory is the compound interest of foresight work.
Signal-to-scenario traceability. Every scenario is traceable back through the trends that inform it to the daily signals that feed those trends. This creates accountability — scenarios are not speculation, they are built on evidence, and that evidence chain is documented.
Friction field analysis. Most scanning operations track drivers. We also systematically track blockers and turners — the regulatory pushback, the cultural resistance, the incumbent dynamics that slow or redirect change. This is where nuance lives, and it is almost entirely absent from commercial foresight platforms.
Temporal depth. The daily data tracker is already accumulating quantitative signals over time. Combined with the trend registry's monthly scoring history and the quarterly scenario plausibility shifts, we are building a longitudinal view of how the landscape is evolving — not snapshots, but a moving picture.
Customer archetype grounding. Most foresight operations stop at trends and scenarios. By running every output through five banking-specific archetypes, we create a translation layer that connects abstract futures to concrete customer impact. This is what makes foresight actionable — and it is absent from virtually every commercial foresight platform.
Causal depth. The CLA framework ensures we are not just cataloguing what is changing but interrogating why — the systemic causes, the enabling worldviews, the deep narratives that determine whether a trend accelerates or reverses. This is where strategic insight lives, and it cannot be automated or purchased.
Calibrated scoring. The VIM calibration protocol ties every score to external evidence, making the registry defensible and reproducible. Competitors relying on purely subjective scoring will find their registries drift towards institutional biases over time. Ours self-corrects.