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 illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.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
LowMediumHighMedium
Timedifferent
45-90 minAs needed2-6 h1-4 h
Participantsdifferent
2-84-153-103-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Assumption List, Critical Assumptions, Learning PlanIncident Log, Action Tracker, Stakeholder UpdatesFMEA Table, Risk Priority, Mitigation ActionsProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
AssumptionsRiskDecisionDiscovery
IncidentOperationsReliability
RiskQualityOperationsRoot cause
Root causeProblem solvingQualityIncident
Add more methods