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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Iceberg Model method illustration showing its working structure
Systems Thinking
Iceberg Model
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.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.The Iceberg Model separates visible events from patterns, structures, and mental models. This turns a single observation into a deeper understanding of why a problem keeps recurring.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
HighMediumLowMedium
Timedifferent
Half day30-90 min30-60 min2-4 h
Participantsdifferent
3-123-122-102-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Leverage Map, Action StrategyPostmortem Doc, Action Items, TimelineIceberg Worksheet, Pattern Notes, Intervention IdeasBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
Systems thinkingChangeStrategy
Site Reliability EngineeringIncidentLearningReliability
Systems thinkingRoot causePatterns
Root causeSafetyIncident
Add more methods