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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Affinity Diagramming
UX Research
Affinity Diagramming
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
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 research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer.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 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 min Setup, dann laufend45–90 min30-60 min2-6 h
Participantsdifferent
1-3 maintaining, briefing for everyone3-102-83-10
Formatdifferent
AsyncWorkshopWorkshopWorkshop
Outputdifferent
RAID Log, Status Report SourceTheme clusters, Insight statements, Opportunity areasFishbone Diagram, Cause Categories, Investigation BacklogFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
RiskTrackingStakeholdersGovernance
SynthesisQualitativeRoot cause
Root causeQualityOperations
RiskQualityOperationsRoot cause
Add more methods