Institutional Governance and Scenario Planning

Quantum programs operate under deep uncertainty: hardware modalities evolve, roadmaps slip, standards mature, security timelines change, and business cases move. Governance should not try to predict one future. It should preserve decision quality across plausible futures.

This chapter defines a governance and scenario-planning discipline for quantum institutions.

Diagram loads as you read

Institutional Governance and Scenario Planning · Figure 1

View diagram source

flowchart LR
    Signals[External signals] --> Scenarios[Scenarios]
    Scenarios --> Options[Strategic options]
    Options --> Portfolio[Portfolio decisions]
    Portfolio --> OperatingPlan[Operating plan]
    OperatingPlan --> Review[Review cadence]
    Review --> Signals

Governance layers

A mature quantum program separates scientific review, platform operations, security governance, financial governance, and executive strategy. One committee should not do everything.

Diagram loads as you read

Governance layers · Figure 2

View diagram source

flowchart TB
    Exec[Executive steering] --> Portfolio[Portfolio board]
    Portfolio --> Science[Scientific review]
    Portfolio --> Platform[Platform operations]
    Portfolio --> Risk[Risk and compliance]
    Platform --> Change[Change advisory]
    Science --> Claims[Claims review]
    Risk --> Policy[Policy authority]

Body	Decision rights
executive steering	funding, strategic direction, risk appetite
portfolio board	use-case selection, kill criteria, scaling decisions
scientific review	method validity, evidence standards
platform operations	target readiness, change approval, incident response
risk and compliance	access, residency, export, security controls
claims review	publication, marketing, customer-facing assertions

Scenario planning

A scenario is not a forecast. It is a stress test for strategy.

Diagram loads as you read

Scenario planning · Figure 3

View diagram source

quadrantChart
    title Quantum scenario space
    x-axis Slow hardware progress --> Fast hardware progress
    y-axis Low market pull --> High market pull
    quadrant-1 Scale bottleneck
    quadrant-2 Research winter
    quadrant-3 Maintain options
    quadrant-4 Capability race
    Slow adoption: [0.25, 0.25]
    Enterprise demand spike: [0.45, 0.85]
    Hardware breakthrough: [0.85, 0.55]
    Standards-first market: [0.55, 0.65]

Each scenario should answer:

What would make this scenario observable?
Which investments become more valuable?
Which investments become wasteful?
Which capabilities are robust across scenarios?
Which decisions should be delayed, accelerated, or abandoned?

Signal registers

A signal register tracks external and internal changes that may shift strategy.

Diagram loads as you read

Signal registers · Figure 4

View diagram source

flowchart LR
    Signal[Signal] --> Source[Source]
    Source --> Interpretation[Interpretation]
    Interpretation --> Impact[Portfolio impact]
    Impact --> Decision[Decision or watch]

Signal categories:

Signal	Examples
hardware	logical error-rate trend, modality maturity, supply constraints
software	runtime abstraction, compiler stability, IR adoption
standards	PQC deadlines, export controls, audit expectations
market	customer pull, procurement behavior, competitor claims
internal	evidence quality, staff capability, cost trend

Decision cadence

A governance system fails if every decision waits for a quarterly meeting. The cadence should match decision half-life.

Diagram loads as you read

Decision cadence · Figure 5

View diagram source

flowchart TB
    Daily[Daily operations] --> Weekly[Weekly change and incident review]
    Weekly --> Monthly[Monthly portfolio review]
    Monthly --> Quarterly[Quarterly strategy review]
    Quarterly --> Annual[Annual architecture and funding reset]

Cadence	Typical decisions
daily	target availability, incident triage, job routing
weekly	change approvals, postmortem closure, canary updates
monthly	use-case gates, budget variance, vendor issues
quarterly	scenario review, roadmap reweighting, workforce plan
annual	architecture refresh, funding, strategic risk appetite

Institutional memory

Quantum programs lose capability when decisions are not preserved. The record should include not only what was decided, but why alternatives were rejected.

Diagram loads as you read

Institutional memory · Figure 6

View diagram source

flowchart LR
    Decision[Decision] --> Context[Context]
    Context --> Alternatives[Alternatives]
    Alternatives --> Rationale[Rationale]
    Rationale --> Evidence[Evidence]
    Evidence --> ReviewDate[Review date]

Institutional memory artifacts include:

architecture decision records
experiment review records
claim review records
incident postmortems
portfolio gate decisions
provider evaluations
scenario updates

Strategy under uncertainty

The healthiest quantum strategies combine focus and optionality. Focus prevents scattered demos. Optionality prevents premature commitment to a single modality, provider, or use case.

Diagram loads as you read

Strategy under uncertainty · Figure 7

View diagram source

flowchart TD
    Strategy[Strategy] --> Focus[Focused operating thesis]
    Strategy --> Options[Option portfolio]
    Focus --> Build[Build core platform capability]
    Options --> Watch[Watch emerging modalities]
    Options --> Drill[Run portability drills]
    Options --> Learn[Small learning bets]
    Build --> Review[Periodic review]
    Watch --> Review
    Drill --> Review
    Learn --> Review

Operating rule

Governance is not a brake. For quantum programs, governance is the mechanism that keeps evidence, investment, risk, and public claims aligned as the technology changes.