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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper matrix with six colored hat cards for information, feeling, value, caution, ideas and process control.
Facilitation
Six Thinking Hats
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Purposedifferent
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.When a topic gets stuck too quickly in the same thinking mode, Six Thinking Hats deliberately separates the perspectives. This means facts, risks, creativity, and emotional signals get worked through one after another instead of mixed together.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.
Complexitydifferent
LowMediumMediumLow
Timedifferent
20-60 min45-90 minAs needed30-90 min
Participantsdifferent
1-44-124-152-8
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathPerspective Notes, Decision Inputs, Action ItemsIncident Log, Action Tracker, Stakeholder UpdatesConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
OperationsReliabilityDocumentation
FacilitationOptionsDecision
IncidentOperationsReliability
ConstraintsDecisionPlanningOptions
Add more methods