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
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Purposedifferent
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.When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.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.
Complexitysame
LowLowLowLow
Timedifferent
30 min Setup, dann laufend30-90 min20-40 min initial, dann laufend20–45 min
Participantsdifferent
1-3 maintaining, briefing for everyone2-83-15Small cross-functional group
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
RAID Log, Status Report SourceConstraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesROAM Board, Owner ListRisk list, Mitigation plan, Assumption log
Tagsno overlap
RiskTrackingStakeholdersGovernance
ConstraintsDecisionPlanningOptions
RiskAgileTrackingAlignment
RiskDecisionFailurePlanning
Add more methods