Prospective Hindsight Prompt¶
Cognitive prompt — instantiates Premortem Calibration
Asks people to stand in an imagined future where the plan has already failed and explain, in hindsight, why it did.
The Prospective Hindsight Prompt is the single cognitive move that opens the whole archetype: the instruction that flips the grammar of the question from "could this fail?" to "it is next quarter, the plan failed — explain what happened." Its entire job is to install the assumed-failure frame and to fix the success expectation it is negating. It does not enumerate the causes and it does not rank them; it changes the tense and certainty of the conversation so that failure is treated as an accomplished fact to be explained rather than a possibility to be argued against. That subtle grammatical shift is what lowers the cost of dissent — you are no longer attacking a colleague's plan, you are narrating a fixed future — and it is the one thing this mechanism owns. Everything downstream feeds on the frame it sets; the prompt itself is a sentence.
Example¶
A retail bank is two weeks from a weekend cutover that will migrate forty years of accounts onto a new core banking platform. The steering group is upbeat — the vendor is confident, the dry runs passed. Before the go decision, the program lead writes two lines on the board. First she pins the success baseline everyone is quietly holding: "By Monday 9am, all accounts reconcile, branches open normally, and no customer notices anything changed." Then she delivers the prompt: "It is now the Monday after. The migration is a public disaster — it is in the news. You are being interviewed about what went wrong. Tell me, in past tense, what happened." The room's posture changes immediately. Nobody defends the platform; instead people narrate — reconciliation ran past the cutoff, the batch didn't complete, branches opened on stale balances, the call center melted. The prompt has produced no list yet and ranked nothing; it has simply made a dozen senior people willing to describe a failure they would not have volunteered as a "risk." That willingness is the deliverable it hands to the brainstorm that follows.
How it works¶
The prompt is almost entirely in the framing, and the framing has two load-bearing parts:
- Fix the baseline it will invert. State plainly what "success" was assumed to be — the outcome, timeline, and confidence — so that "it failed" has a definite thing to be the negation of.
- Assert failure as fact, in past tense. The wording matters: not "what might go wrong" but "it went wrong; explain why." Certainty, not possibility, is what unlocks candor.
- Bound the future. Give the imagined failure a horizon and a severity ("next Monday," "a public disaster") so the explanations are concrete rather than free-floating dread.
- Stop at the frame. The prompt deliberately does not solicit an organized list or a vote; handing off the raw, willing narration is its whole function.
Tuning parameters¶
- Horizon — how far into the future the failure is placed. A near horizon keeps causes concrete and operational; a distant one surfaces slow, structural failures but invites vaguer answers.
- Severity framing — "underwhelming" versus "catastrophic, in the press." Higher severity licenses bolder causes but can tip the room into lurid, low-probability storytelling.
- Vividness of the scene — a bare "assume it failed" versus a staged "you're being interviewed." Richer staging raises engagement at the risk of theatrical rather than realistic answers.
- Individual-first versus group-first — having people write their narration before speaking. Writing first protects independence; going straight to discussion is faster but anchors on the first voice.
When it helps, and when it misleads¶
Its strength is disproportionate to its size: a one-sentence reframe measurably loosens the tongue, because prospective hindsight — imagining an outcome as already certain — makes people generate more, and more specific, reasons than asking them to forecast possibilities does[1]. It is the cheapest, most portable piece of the archetype and can be deployed in ten seconds.
It misleads when it is mistaken for the whole exercise. On its own the prompt produces a burst of narration and nothing durable — no organized causes, no priorities, no plan change. A classic misuse is delivering the prompt, enjoying the candid stories, and adjourning; the frame was opened and never converted. The guarding discipline is to treat the prompt strictly as an opener that must hand off to generation and ranking, and to fix the success baseline first — an unbounded "imagine failure" with no stated expectation to negate tends to produce mood, not information.
How it implements the components¶
The prompt realizes only the archetype's frame-setting components:
assumed_failure_scenario— it creates the bounded counterfactual (horizon + severity, asserted as fact) that is the archetype's distinctive frame shift.success_assumption_baseline— it first pins the optimistic outcome and confidence the counterfactual negates, so the failure has a definite thing to contradict.
It does not build the failure_cause_list — that inventory belongs to Failure-Mode Brainstorm, the sibling it is most easily confused with — and it does not produce the vulnerability_ranking, which is Assumption Stress Test's; the prompt supplies the frame, and the others fill and prioritize it.
Related¶
- Instantiates: Premortem Calibration — the prompt is the archetype's opening cognitive move.
- Sibling mechanisms: Premortem Workshop · Failure-Mode Brainstorm · Assumption Stress Test · Red-Team Failure Review · Risk Register Update · Contingency Buffer Review · Failure Trigger Dashboard
Editorial Notes¶
Form Classification¶
Form family: Interface, Display & Cue
Rationale: Prospective Hindsight Prompt operates as a user-facing prompt, display, template, or perceptual cue that shapes attention and action at the point of use because it asks people to stand in an imagined future where the plan has already failed and explain, in hindsight, why it did.
Independent corroboration: The frozen evidence defines Prospective Hindsight Prompt as 'Asks people to stand in an imagined future where the plan has already failed and explain, in hindsight, why it did', so its operative form is Interface, Display & Cue.
Nearest alternative: Communication, Facilitation & Learning — Prospective Hindsight Prompt includes features of a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding, but its defining operation is a user-facing prompt, display, template, or perceptual cue that shapes attention and action at the point of use.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Psychology
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Prospective Hindsight Prompt is most plausibly rooted in the psychology tradition because its characteristic form depends on individual cognition, motivation, judgment, and behavior. The assignment tracks that formative lineage, not the many settings in which the mechanism can now be applied.
Related originating lineages:
- Organizational & Management Science — The organizational_management tradition materially shaped Prospective Hindsight Prompt through its own practice of the coordination, governance, learning, and redesign of organized work.
Review resolution: Both blind reviewers agree that psychology is the primary origin. Explicit reconciliation resolves origin mode disagreement. Formative alternate lineages are retained as organizational_management; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Review outcome: Reconciled after independent review; high confidence.
References¶
[1] Mitchell, D. J., Russo, J. E., & Pennington, N. "Back to the Future: Temporal Perspective in the Explanation of Events". Journal of Behavioral Decision Making 2(1), 25–38 (1989). Finds that treating a future outcome as certain generates more, more event-specific reasons than treating it as uncertain. registry ↩