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
A paper-based illustration representing Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
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
Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected.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.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
LowMediumHighMedium
Timedifferent
1-2 h30-90 min2-6 h2-4 h
Participantsdifferent
2-83-123-82-6
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativePostmortem Doc, Action Items, TimelineCurrent Reality Tree, Core Problems, Intervention IdeasBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
Site Reliability EngineeringIncidentLearningReliability
Systems thinkingRoot causeConstraintsCausality
Root causeSafetyIncident
Add more methods