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
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
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
In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.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
Halber TagAs needed2-6 h2-4 h
Participantsdifferent
5-204-153-82-6
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Simulation Notes, Gaps List, Updated RunbooksIncident Log, Action Tracker, Stakeholder UpdatesCurrent Reality Tree, Core Problems, Intervention IdeasBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
ResilienceOperationsIncident
IncidentOperationsReliability
Systems thinkingRoot causeConstraintsCausality
Root causeSafetyIncident
Add more methods