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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
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.After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.
Complexitydifferent
LowMediumHighLow
Timedifferent
20-40 min initial, dann laufend30-90 min2-6 h15-30 min
Participantsdifferent
3-153-123-102-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
ROAM Board, Owner ListPostmortem Doc, Action Items, TimelineEvent Timeline, Causal Factor Chart, Cause List, Corrective ActionsRoot cause notes, Countermeasures
Tagsno overlap
RiskAgileTrackingAlignment
Site Reliability EngineeringIncidentLearningReliability
CausalityIncidentRoot causeTimeline
Root causeIncidentLeanProblem solving
Add more methods