Institutional Memory and Long-Horizon Technology Watch

Quantum computing changes quickly, but organizations forget quickly too. The dangerous pattern is repeated enthusiasm: a team runs a promising pilot, loses the lessons, changes staff, and restarts the same pilot two years later under a different name.

A mature quantum organization preserves institutional memory and runs a disciplined technology-watch process. The objective is not to predict the future perfectly. It is to detect when assumptions change and to update strategy without thrash.

Diagram loads as you read

Institutional Memory and Long-Horizon Technology Watch · Figure 1

View diagram source

flowchart LR
    Signal[External signal] --> Triage[Triage]
    Triage --> Assumption[Assumption impacted]
    Assumption --> Decision[Decision record]
    Decision --> Roadmap[Roadmap update]
    Roadmap --> Review[Next review]

The assumption ledger

Every quantum roadmap rests on assumptions:

physical error rates improve at a given pace;
logical-qubit overhead declines;
compiler maturity improves;
cloud access remains available;
a vendor maintains a roadmap;
a use case remains economically relevant;
post-quantum migration deadlines hold;
internal talent remains available.

Make these assumptions explicit.

Diagram loads as you read

The assumption ledger · Figure 2

View diagram source

flowchart TB
    Ledger[Assumption ledger] --> Hardware[Hardware assumptions]
    Ledger --> Software[Software assumptions]
    Ledger --> Market[Market assumptions]
    Ledger --> Security[Security assumptions]
    Ledger --> Talent[Talent assumptions]
    Ledger --> Cost[Cost assumptions]

Example:

Illustrative listing · yaml

assumption:
  id: A-FT-001
  statement: logical qubit service access becomes commercially useful for chemistry screening before 2030
  confidence: medium
  leading_indicators:
    - logical error rate trend
    - resource estimate trend
    - vendor access model
    - classical baseline movement
  decision_dependency: chemistry portfolio phase 2
  review_cadence: quarterly

Signal taxonomy

Diagram loads as you read

Signal taxonomy · Figure 3

View diagram source

flowchart TB
    Signals[Signals] --> Technical[Technical]
    Signals --> Commercial[Commercial]
    Signals --> Regulatory[Regulatory]
    Signals --> Ecosystem[Ecosystem]
    Signals --> Internal[Internal]

    Technical --> T1[error correction result]
    Technical --> T2[new hardware modality]
    Commercial --> C1[pricing change]
    Commercial --> C2[availability change]
    Regulatory --> R1[PQC mandate]
    Regulatory --> R2[export control]
    Ecosystem --> E1[standard update]
    Ecosystem --> E2[SDK deprecation]
    Internal --> I1[talent gap]
    Internal --> I2[portfolio result]

Signals are only useful if mapped to decisions.

Technology-watch pipeline

Diagram loads as you read

Technology-watch pipeline · Figure 4

View diagram source

stateDiagram-v2
    [*] --> Captured
    Captured --> Screened
    Screened --> Relevant: impacts assumption
    Screened --> Archived: no decision impact
    Relevant --> Analyzed
    Analyzed --> Actionable
    Analyzed --> Monitor
    Actionable --> DecisionRecord
    Monitor --> Captured

Do not treat every arXiv paper as a strategy change. Most signals should be archived or monitored.

Decision records

Institutional memory requires concise records.

Diagram loads as you read

Decision records · Figure 5

View diagram source

flowchart LR
    Question[Decision question] --> Options[Options]
    Options --> Evidence[Evidence]
    Evidence --> Decision[Decision]
    Decision --> Consequence[Consequences]
    Consequence --> Review[Review trigger]

A decision record should capture:

decision date;
owner;
options considered;
evidence used;
uncertainty;
decision;
consequences;
review trigger.

Roadmap review cadence

Diagram loads as you read

Roadmap review cadence · Figure 6

View diagram source

gantt
    title Annual Quantum Strategy Cadence
    dateFormat  YYYY-MM-DD
    section Quarterly
    Assumption review Q1 :a1, 2026-01-15, 3d
    Assumption review Q2 :a2, 2026-04-15, 3d
    Assumption review Q3 :a3, 2026-07-15, 3d
    Assumption review Q4 :a4, 2026-10-15, 3d
    section Annual
    Portfolio reset :b1, 2026-11-01, 10d
    Budget decision :b2, after b1, 5d

Quarterly reviews should update assumptions. Annual reviews should update budget and portfolio.

Knowledge base design

Diagram loads as you read

Knowledge base design · Figure 7

View diagram source

flowchart TB
    KB[Quantum knowledge base] --> Decisions[Decision records]
    KB --> Incidents[Incident reviews]
    KB --> Benchmarks[Benchmark history]
    KB --> Vendors[Vendor evaluations]
    KB --> Assumptions[Assumption ledger]
    KB --> Training[Training materials]
    KB --> Claims[Claim registry]

The knowledge base must be searchable by use case, vendor, artifact, decision, and claim. Store links to evidence, not screenshots of dashboards.

Avoid cargo-cult strategy

Common failure modes:

Diagram loads as you read

Avoid cargo-cult strategy · Figure 8

View diagram source

flowchart TB
    Failure[Strategy failure modes] --> Hype[Hype chasing]
    Failure --> Stale[Stale assumptions]
    Failure --> Amnesia[Organizational amnesia]
    Failure --> VendorLock[Unexamined vendor lock]
    Failure --> PilotLoop[Repeating pilots]

Countermeasures:

Failure	Countermeasure
hype chasing	assumption ledger and review cadence
stale roadmap	leading indicators
repeated pilots	searchable decision records
vendor lock-in	portability tests and exit plans
overclaiming	claim registry and review board

Leading indicators

Diagram loads as you read

Leading indicators · Figure 9

View diagram source

flowchart LR
    Indicator[Leading indicator] --> Threshold{Threshold crossed?}
    Threshold -- no --> Monitor[Continue monitoring]
    Threshold -- yes --> Review[Trigger strategic review]
    Review --> Update[Update roadmap or assumption]

Examples:

logical error rates improve beyond a defined threshold;
target availability falls below SLO;
benchmark suite shows repeatable advantage on a narrow workload;
provider pricing changes materially;
regulatory deadline changes;
critical SDK deprecates an interface.

Operating rule

A quantum roadmap is not a slide deck. It is a living set of assumptions, decisions, evidence, and review triggers.