Risk Register Update¶
Documentation artifact — instantiates Premortem Calibration
Records the ranked vulnerabilities and the changes they triggered in a living, dated ledger so the premortem's findings outlast the meeting.
The Risk Register Update is the archetype's memory. Its defining function is durability: it takes the ranked vulnerabilities and — critically — the record of what changed because of them, and commits both to a living, dated, versioned document that survives past the room and the mood. What separates it from its neighboring artifacts is that it neither sizes reserves nor watches for warning signs; it keeps the ledger. Its most important column is not the list of risks but the trace of decisions: for each priority vulnerability, what safeguard, scope change, or explicit acceptance it produced, and when. That decision-revision trace is precisely the thing whose absence turns a premortem into theater — a register that logs risks but records no changes is the artifact-substitution failure the archetype warns about. The register's job is to make the changes auditable, not to make them.
Example¶
A construction manager on a large stadium build finishes a premortem before the steel-erection phase and walks out with a whiteboard full of ranked failure modes. By the next morning that would normally evaporate. Instead she updates the project risk register. She transcribes the ranked vulnerabilities in priority order — crane availability during the tight winter window, a fabrication-shop delay on the roof trusses, a below-grade utility conflict — each with its plausibility and impact. Then she fills the column that matters: the decision trace. Against the crane risk: "Booked second crane on standby; sequence revised — logged 14 Mar, approved by PM." Against the truss risk: "Accepted as residual; supplier penalty clause added." Against the utility conflict: "No change yet — awaiting survey." Six weeks later, when leadership asks why the schedule shifted, the answer is not a memory but a dated line. The register did not decide anything; it made every decision traceable, and it made the absence of a decision on the utility conflict impossible to quietly forget.
How it works¶
- Persist the ranked list, don't re-rank it. The register imports the vulnerability order from the analysis; its contribution is durable, structured storage, not fresh prioritization.
- Record the decision against each risk. For every priority item, log what changed — safeguard, scope, acceptance, or "none yet" — with a date and an author.
- Version, don't overwrite. Updates are appended and dated so the trace shows how the plan's risk posture evolved, not just its current state.
- Expose the gaps. By forcing a decision column, the register makes the unaddressed vulnerability visibly blank rather than silently absent.
Tuning parameters¶
- Trace granularity — a single "mitigated/accepted" flag versus a full narrative of what changed and why. Richer traces are audit-proof but heavier to maintain, and heaviness is what kills registers.
- Update cadence — one-shot after the premortem versus a standing document revisited at each gate. A living register catches drift; a frozen one is a snapshot that ages.
- Field discipline — free-text notes versus enforced fields (owner-reference, decision, date, status). Structure enables rollups and queries but raises the entry cost.
- Scope of entry — every raised risk versus only the priority-ranked ones. Logging everything is complete but buries the decision-relevant few; logging only top risks is lean but loses the audit trail.
When it helps, and when it misleads¶
Its strength is institutional memory: the register is what lets a decision be revisited and defended months later, and what makes an ignored vulnerability leave a visible, dated hole rather than vanishing. The living risk register is the standard project-management artifact for exactly this purpose[n1].
Its failure mode is the one the archetype names most sharply: artifact substitution, where updating the register feels like managing the risk and quietly replaces actually doing anything about it. A beautifully maintained register with an empty decision column is the performative premortem in filing-cabinet form. The guarding discipline is to treat the decision-trace column, not the risk list, as the point — and to review the register for entries that have been "open" too long, because a risk logged and never acted on is worse than one never written down.
How it implements the components¶
The register realizes the archetype's record-keeping components:
decision_revision_trace— its core: it records what changed because of the exercise — safeguard, scope, or explicit acceptance — dated and attributed, so the premortem cannot become symbolic.vulnerability_ranking— it persists the prioritized vulnerabilities as a living, versioned ledger; where the analysis produced the order, the register keeps it inspectable over time.
It does not perform safeguard_revision — turning vulnerabilities into buffers and plan changes is Contingency Buffer Review — nor does it own the early_warning_indicator_set or contingency_owner_assignment that drive Failure Trigger Dashboard; the register records the decisions those mechanisms make, it does not make them.
Related¶
- Instantiates: Premortem Calibration — the register is the durable record that keeps the calibration from being symbolic.
- Consumes: Assumption Stress Test supplies the ranked vulnerabilities the register persists.
- Sibling mechanisms: Premortem Workshop · Prospective Hindsight Prompt · Failure-Mode Brainstorm · Assumption Stress Test · Red-Team Failure Review · Contingency Buffer Review · Failure Trigger Dashboard
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Risk Register Update operates as a persistent ledger, log, register, or case record that preserves history and traceability because it records the ranked vulnerabilities and the changes they triggered in a living, dated ledger so the premortem's findings outlast the meeting.
Independent corroboration: The frozen evidence defines Risk Register Update as 'Records the ranked vulnerabilities and the changes they triggered in a living, dated ledger so the premortem's findings outlast the meeting', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Convergent development
Present-day reach: Universal
Rationale: Maintaining dated risk entries and decisions is a canonical organizational risk-management practice.
Related originating lineages:
- Engineering & Design — Configuration-controlled hazard logs materially contribute traceable updates.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: records the ranked vulnerabilities and the changes they triggered in a living, dated ledger so the premortem's findings outlast the meeting.
Review resolution: Both blind reviewers agree that organizational_management is the primary historical origin. Explicit reconciliation of alternate origin disagreement, origin mode disagreement, domain reach disagreement starts from reviewer_a’s mechanism-specific evidence: Maintaining dated risk entries and decisions is a canonical organizational risk-management practice. Reviewer A proposed alternates=engineering_design, origin_mode=convergent, domain_reach=universal, and encyclopedia_synthesis=true; reviewer B proposed alternates=systems_cybernetics, origin_mode=single_lineage, domain_reach=multi_domain, and encyclopedia_synthesis=true. The final record retains every independently supported alternate from either review (engineering_design, systems_cybernetics) without an arbitrary cap, selects origin_mode=convergent to represent the combined lineage evidence, and keeps domain_reach=universal and encyclopedia_synthesis=true from the more mechanism-specific assessment. Present-day transfer is recorded as reach and is not treated as proof of historical origin.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] A risk register is the standard living document in project and program management that records identified risks, their assessed priority, the response decided for each, and its owner and status. Its value in this archetype is the decision-and-status trace, which is what distinguishes a calibrated response from a list of worries. ↩