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 of MORT Analysis with its method-specific working model.
Operations
MORT Analysis
Affinity Diagramming
UX Research
Affinity Diagramming
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree 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 safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps.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 critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.
Complexitydifferent
LowHighLowHigh
Timedifferent
30 min Setup, dann laufendMehrere Tage bis Wochen45–90 min2-6 h
Participantsdifferent
1-3 maintaining, briefing for everyone2-63-103-8
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
RAID Log, Status Report SourceMORT Worksheets, Findings per Branch, Corrective Actions, Systemic RecommendationsTheme clusters, Insight statements, Opportunity areasFault Tree, Critical Paths, Cause Hypotheses, Control Actions
Tagsno overlap
RiskTrackingStakeholdersGovernance
Root causeSafetySystemicIncident
SynthesisQualitativeRoot cause
RiskRoot causeSafety
Add more methods