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
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Paper illustration for Intervention Mapping.
Systems Thinking
Intervention Mapping
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Purposedifferent
For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
Ongoing1-5 Tage1-4 h1-3 h
Participantsdifferent
2-204-123-82-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Chat Transcript, Action Log, AutomationsLogic Model, Change Objectives, Intervention Components, Evaluation PlanProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanCause Tree, Evidence Notes, Countermeasures
Tagsno overlap
CollaborationEngineeringIncident
ChangeSystems thinkingCapability
Root causeProblem solvingQualityIncident
Root causeTreeIncidentQuality
Add more methods