Uncertainty Retrospective Prompt¶
Meeting prompt — instantiates Intellectual-Humility Narrative Integration
A recurring review question that asks, after the fact, which uncertainties the group named, which it hid, which it resolved, and which it mishandled.
An Uncertainty Retrospective Prompt is a standing, lightweight question inserted into a group's regular reviews that turns attention onto how the group handled its own uncertainty over the period just past. Its distinguishing move is that it is recurring, backward-looking, and diagnostic of the group's epistemic habits — not a deep dive into a single incident, but a routine question that keeps the certainty-versus-warrant pattern under continuous observation. It audits the norm; it does not investigate one event or forecast one plan.
Example¶
A venture-capital firm adds one recurring item to its monthly portfolio review: "For the decisions we made last month — where did we mark our uncertainty honestly, where did we paper over it with confidence, and where did a partner change their read?" The first few times it is awkward. Then a partner notes that the committee waved through a follow-on round on a "strong conviction" that, examined, rested on a single founder meeting. Another flags that a junior associate's doubt about a market-size number got steamrolled. None of this is a postmortem on a failed deal — the deals have not resolved. It is a diagnosis of the committee's habits: where confidence is performed rather than warranted, and whether dissent survives contact with seniority. Over quarters, the prompt makes the firm's own certainty patterns visible to itself.
How it works¶
- Recurring, attached to an existing review rather than convened specially.
- Backward-looking over the recent period, scanning many decisions rather than dissecting one.
- Targets the group's uncertainty handling, not any single outcome.
- A four-part scan — which uncertainties were named, hidden, resolved, mishandled.
- Lightweight — a prompt, not a protocol — so it keeps the norm salient and makes self-examination ordinary.
Tuning parameters¶
- Cadence — every meeting versus periodic. Frequent keeps the norm salient but risks rote answers.
- Scope — one decision versus the whole period. Broad diagnoses patterns; narrow goes deeper.
- Who answers — self-report versus facilitator-led. Facilitation surfaces the hidden ones self-report will not.
- Follow-through — diagnosis only versus routed onward to an owner or a postmortem. Routing gives it teeth; the prompt itself only surfaces, it does not fix.
- Framing — evaluative versus curious. A curious tone keeps it safe; an evaluative one reverts to blame.
When it helps, and when it misleads¶
Its strength is that it keeps the group's epistemic habits under standing observation, catching drift — creeping overconfidence, suppressed dissent — that no single-incident review would surface. By recurring, it also makes examining one's own certainty an ordinary part of belonging to the group. It guards against outcome bias by keeping the lens on the process of handling uncertainty rather than on whether a call happened to pan out.[n1]
Its failure mode is ritual decay: the prompt asked and answered by rote, producing comfortable non-answers; or a drift back into judging outcomes ("that call was right, so our confidence was fine"), which misses the overconfident calls that got lucky. The classic misuse is relitigating decisions by their results rather than examining how uncertainty was handled going in. The guarding discipline is to keep the lens on process and warrant at decision time, and to rotate who leads the prompt so it does not ossify.
How it implements the components¶
certainty_status_diagnosis— its four-part scan is a diagnosis of the group's certainty narrative: where confidence was performed, where uncertainty was hidden, whose doubt was overridden.humility_identity_frame— by recurring, it makes routine self-examination of uncertainty part of what the group takes itself to be, reinforcing the identity rather than treating humility as a one-off event.
It does not deep-dive one incident to build an error_learning_story_repository entry or commit a learning_transfer_marker change — that is the Learning-from-Error Postmortem; and unlike the prospective Premortem Unknowns Round, it looks backward at habits already exercised.
Related¶
- Instantiates: Intellectual-Humility Narrative Integration — keeps the humility norm salient by making the group audit its own uncertainty handling on a cadence.
- Sibling mechanisms: Learning-from-Error Postmortem · Premortem Unknowns Round · Confidence Update Log · Epistemic Status Labels · Humility Norm Onboarding Module · Leader "I Was Wrong" Story · Mistake-to-Principle Story Template · Public Assumption Revision Memo · Recognition for Belief Revision
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Uncertainty Retrospective Prompt operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it a recurring review question that asks, after the fact, which uncertainties the group named, which it hid, which it resolved, and which it mishandled.
Independent corroboration: The frozen evidence defines Uncertainty Retrospective Prompt as 'A recurring review question that asks, after the fact, which uncertainties the group named, which it hid, which it resolved, and which it mishandled', so its operative form is Assessment, Review & Assurance.
Nearest alternative: Interface, Display & Cue — Uncertainty Retrospective Prompt includes features of a user-facing prompt, display, template, or perceptual cue that shapes attention and action at the point of use, but its defining operation is a bounded evaluation of existing evidence or work that produces a finding or disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Reviewing which uncertainties were named, hidden, resolved, or mishandled is structured organizational learning after action. WHO defines AAR as a facilitated review of what happened, why, what worked less well, and how to improve; the prompt focuses that learning on uncertainty handling.
Related originating lineages:
- Data Science & Analytics — Data modeling, telemetry, and analytic monitoring supplies a distinct formative lineage for the mechanism's uncertainty retrospective prompt logic.
- Disaster Management & Risk Reduction — disaster_management contributes incident command, mass-casualty response, continuity, and emergency resource coordination to this mechanism's defining operation—A recurring review question that asks, after the fact, which uncertainties the group named, which it hid, which it resolved, and which it mishandled—without displacing the selected primary historical lineage.
- Futurism & Strategic Foresight — Strategic foresight, scenario planning, and anticipatory governance supplies a parallel or contributing lineage for the mechanism's defining operation: a recurring review question that asks, after the fact, which uncertainties the group named, which it hid, which it resolved, and which it mishandled.
- Psychology — Experimental, clinical, and behavioral psychology supplies a parallel or contributing lineage for the mechanism's defining operation: a recurring review question that asks, after the fact, which uncertainties the group named, which it hid, which it resolved, and which it mishandled.
- Statistics & Experimental Design — statistics_experimental_design contributes statistics, experimental design, and measurement theory to this mechanism's defining operation—A recurring review question that asks, after the fact, which uncertainties the group named, which it hid, which it resolved, and which it mishandled—without displacing the selected primary historical lineage.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: a recurring review question that asks, after the fact, which uncertainties the group named, which it hid, which it resolved, and which it mishandled.
Review resolution: The blind reviewers disagree on primary lineage (statistics_experimental_design versus organizational_management). Authoritative or primary research supports organizational_management as the best historical origin: Reviewing which uncertainties were named, hidden, resolved, or mishandled is structured organizational learning after action. WHO defines AAR as a facilitated review of what happened, why, what worked less well, and how to improve; the prompt focuses that learning on uncertainty handling. The cited World Health Organization, After Action Review directly supports the mechanism's defining operation. All independently supported contributing domains are retained without an arbitrary cap. origin_mode=cross_disciplinary_synthesis records lineage, while domain_reach=universal records later applicability separately from provenance.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
[n1] Outcome bias — the tendency (Baron & Hershey) to judge the quality of a decision by how it turned out rather than by the information and reasoning available when it was made; a sound uncertainty-handling review evaluates the process, not the result. ↩