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 Flywheel.
Growth
Flywheel
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
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.Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth.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.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
LowMediumHighHigh
Timedifferent
30 min Setup, dann laufend60-120 min2-6 h2-6 h
Participantsdifferent
1-3 maintaining, briefing for everyone3-83-103-8
Formatdifferent
AsyncWorkshopWorkshopWorkshop + async
Outputdifferent
RAID Log, Status Report SourceFlywheel Map, Friction Points, Growth Levers, Experiment BacklogFMEA Table, Risk Priority, Mitigation ActionsFault Tree, Critical Paths, Cause Hypotheses, Control Actions
Tagsno overlap
RiskTrackingStakeholdersGovernance
GrowthRetentionConversion
RiskQualityOperationsRoot cause
RiskRoot causeSafety
Add more methods