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
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Current Reality Tree
Systems Thinking
Current Reality Tree
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.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 single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.
Complexitydifferent
LowMediumHighLow
Timedifferent
30-90 minAs needed2-6 h15-30 min
Participantsdifferent
2-84-153-82-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Constraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesIncident Log, Action Tracker, Stakeholder UpdatesCurrent Reality Tree, Core Problems, Intervention IdeasRoot cause notes, Countermeasures
Tagsno overlap
ConstraintsDecisionPlanningOptions
IncidentOperationsReliability
Systems thinkingRoot causeConstraintsCausality
Root causeIncidentLeanProblem solving
Add more methods