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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Purposedifferent
When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins.For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events.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
MediumMediumHighMedium
Timedifferent
1-3 h1-3 h2-6 h2-4 h
Participantsdifferent
2-83-123-102-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Context Map, Integration Patterns, Boundary NotesSystem Map, Dependencies, Leverage PointsEvent Timeline, Causal Factor Chart, Cause List, Corrective ActionsBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
Systems thinkingMappingBoundariesChange
CausalityIncidentRoot causeTimeline
Root causeSafetyIncident
Add more methods