methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration for Failure Scenario Analysis.
Engineering
Failure Scenario Analysis
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Purposedifferent
In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.
Complexitydifferent
LowMediumLowLow
Timedifferent
20–45 min1-3 h30 min Setup, dann laufend30-90 min
Participantsdifferent
Small cross-functional group3-81-3 maintaining, briefing for everyone2-8
Formatdifferent
WorkshopWorkshopAsyncWorkshop + async
Outputdifferent
Risk list, Mitigation plan, Assumption logFailure Scenarios, Risk Notes, Control Gaps, Test and Response ActionsRAID Log, Status Report SourceConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
RiskDecisionFailurePlanning
FailureResilienceRisk
RiskTrackingStakeholdersGovernance
ConstraintsDecisionPlanningOptions
Add more methods