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 illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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 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.
Complexitydifferent
LowLowHighLow
Timedifferent
20-60 min30 min Setup, dann laufend2-6 h30-60 min
Participantsdifferent
1-41-3 maintaining, briefing for everyone3-102-8
Formatdifferent
AsyncAsyncWorkshopWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathRAID Log, Status Report SourceFMEA Table, Risk Priority, Mitigation ActionsFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
OperationsReliabilityDocumentation
RiskTrackingStakeholdersGovernance
RiskQualityOperationsRoot cause
Root causeQualityOperations
Add more methods