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 fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Communication Plan
Delivery
Communication Plan
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
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.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.When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost.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.
Complexitydifferent
LowLowLowHigh
Timedifferent
30-60 min30 min Setup, dann laufend45-90 min2-6 h
Participantsdifferent
2-81-3 maintaining, briefing for everyone2-63-10
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop
Outputdifferent
Fishbone Diagram, Cause Categories, Investigation BacklogRAID Log, Status Report SourceCommunication Plan, Channel Matrix, Message CadenceFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
Root causeQualityOperations
RiskTrackingStakeholdersGovernance
CommunicationStakeholdersDeliveryPlanning
RiskQualityOperationsRoot cause
Add more methods