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
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Purposedifferent
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.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.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.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.
Complexitydifferent
LowLowHighHigh
Timedifferent
15-30 min20-60 min2-6 h1-6 Wochen
Participantsdifferent
2-61-43-104-10
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Root cause notes, CountermeasuresRunbook, Checklist, Escalation PathFMEA Table, Risk Priority, Mitigation Actions8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan
Tagsno overlap
Root causeIncidentLeanProblem solving
OperationsReliabilityDocumentation
RiskQualityOperationsRoot cause
QualityProblem solvingRoot cause
Add more methods