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 of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
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
Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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 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
LowMediumLowHigh
Timedifferent
45-90 minAs needed30-60 min2-8 h
Participantsdifferent
2-84-152-82-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Assumption List, Critical Assumptions, Learning PlanIncident Log, Action Tracker, Stakeholder UpdatesFishbone Diagram, Cause Categories, Investigation BacklogProblem Analysis, Decision Analysis, Risk Plan
Tagsno overlap
AssumptionsRiskDecisionDiscovery
IncidentOperationsReliability
Root causeQualityOperations
Problem solvingRoot causeDecisionOperations
Add more methods