Skip to content

Science fiction prototyping

A futures and design method that uses a science-fiction narrative to explore a proposed technology’s operation, users and social consequences before it exists.

Version
v1 · 2026-09-08 · History
Domain-specific #
6599
Origin domain
futures design
Subdomain
futures design
Aliases
SFP

Core Idea

The story is an exploratory prototype rather than a forecast, aesthetic plausibility does not validate technical feasibility and affected perspectives and unintended consequences must be deliberately represented. A current scientific or technological signal is extrapolated into a future artifact and context, characters experience its everyday benefits and failures and discussion translates narrative consequences into present design questions. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

Scope of Application

Science fiction prototyping belongs to futures design and is useful where the analyst can specify the typed futures design carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, then evaluate the focal technology and present evidence, future horizon and assumptions, prototype artifact or service, characters stakeholders and setting, use scenario, enabling social and technical system, intended and unintended consequences, narrative artifact and debrief into requirements risks or research questions are explicit.

Clarity

The abstraction clarifies a crowded vocabulary by making the focal technology and present evidence, future horizon and assumptions, prototype artifact or service, characters stakeholders and setting, use scenario, enabling social and technical system, intended and unintended consequences, narrative artifact and debrief into requirements risks or research questions are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test.

Manages Complexity

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Science fiction prototyping. Science fiction prototyping compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning

  1. Identify the carrier. State what the elements, states, objects, or observations are: the typed futures design carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express the focal technology and present evidence, future horizon and assumptions, prototype artifact or service, characters stakeholders and setting, use scenario, enabling social and technical system, intended and unintended consequences, narrative artifact and debrief into requirements risks or research questions are explicit independently of one notation or implementation.

Knowledge Transfer

Knowledge transfers strongly among subfields of futures design because they reuse the typed futures design carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, A current scientific or technological signal is extrapolated into a future artifact and context, characters experience its everyday benefits and failures and discussion translates narrative consequences into present design questions., and type the carrier, state every parameter and convention in the definition, test that the focal technology and present evidence, future horizon and assumptions, prototype artifact or service, characters stakeholders and setting, use scenario, enabling social and technical system, intended and unintended consequences, narrative artifact and debrief into requirements risks or research questions are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions

Local relationship map for Science fiction prototypingParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Science fictionprototypingDOMAINPrime abstraction: Scenario Planning — is a kind ofScenarioPlanningPRIME

Current abstraction Science fiction prototyping Domain-specific

Parents (1) — more general patterns this builds on

  • Science fiction prototyping is a kind of Scenario Planning Prime

    The proposed strict upward parent is prime:scenario_planning.

Hierarchy paths (2) — routes to 2 parentless roots

Neighborhood in Abstraction Space

Science fiction prototyping sits in a moderately populated region (50th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Engineering Design & Requirements (47 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08