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
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
Affinity Diagramming
UX Research
Affinity Diagramming
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.For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.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.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
LowHighLowHigh
Timedifferent
30 min Setup, dann laufend2-6 h45–90 min2-6 h
Participantsdifferent
1-3 maintaining, briefing for everyone3-83-103-10
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
RAID Log, Status Report SourceFault Tree, Critical Paths, Cause Hypotheses, Control ActionsTheme clusters, Insight statements, Opportunity areasFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
RiskTrackingStakeholdersGovernance
RiskRoot causeSafety
SynthesisQualitativeRoot cause
RiskQualityOperationsRoot cause
Add more methods