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 Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Paper illustration for Incident Timeline Analysis.
DevOps
Incident Timeline Analysis
Paper illustration for Current Reality Tree
Systems Thinking
Current Reality Tree
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Purposedifferent
Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy.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.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.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
HighMediumHighMedium
Timedifferent
Half day60-180 min2-6 h2-4 h
Participantsdifferent
3-123-103-82-6
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Leverage Map, Action StrategyIncident Timeline, Evidence Log, Delay Analysis, Improvement ActionsCurrent Reality Tree, Core Problems, Intervention IdeasBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
Systems thinkingChangeStrategy
IncidentTimelineSite Reliability Engineering
Systems thinkingRoot causeConstraintsCausality
Root causeSafetyIncident
Add more methods