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 Argument Mapping
Decision Making
Argument Mapping
Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe
Paper illustration for Root Cause Analysis.
Operations
Root Cause 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.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations.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.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
Ongoing1-3 h2-8 h1-4 h
Participantsdifferent
2-201-82-83-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Chat Transcript, Action Log, AutomationsArgument Map, Evidence Gaps, Decision RationaleProblem Analysis, Decision Analysis, Risk PlanProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
CollaborationEngineeringIncident
SensemakingDecisionRationale
Problem solvingRoot causeDecisionOperations
Root causeProblem solvingQualityIncident
Add more methods