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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe
Purposedifferent
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.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.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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.
Complexitydifferent
MediumLowLowHigh
Timedifferent
As needed30-90 min30-60 min2-8 h
Participantsdifferent
4-152-82-82-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Incident Log, Action Tracker, Stakeholder UpdatesConstraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesFishbone Diagram, Cause Categories, Investigation BacklogProblem Analysis, Decision Analysis, Risk Plan
Tagsno overlap
IncidentOperationsReliability
ConstraintsDecisionPlanningOptions
Root causeQualityOperations
Problem solvingRoot causeDecisionOperations
Add more methods