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 for Current Reality Tree
Systems Thinking
Current Reality Tree
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Incident Timeline Analysis.
DevOps
Incident Timeline Analysis
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Purposedifferent
A Current Reality Tree condenses many symptoms into a few causal chains. The method makes visible which core problems drive several negative effects at once.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 incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable.For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.
Complexitydifferent
HighMediumMediumMedium
Timedifferent
2-6 h30-90 min60-180 min2-4 h
Participantsdifferent
3-83-123-102-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Current Reality Tree, Core Problems, Intervention IdeasPostmortem Doc, Action Items, TimelineIncident Timeline, Evidence Log, Delay Analysis, Improvement ActionsBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
Systems thinkingRoot causeConstraintsCausality
Site Reliability EngineeringIncidentLearningReliability
IncidentTimelineSite Reliability Engineering
Root causeSafetyIncident
Add more methods