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 for Flywheel.
Growth
Flywheel
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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
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.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 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
MediumLowHighHigh
Timedifferent
60-120 min30 min Setup, dann laufend2-6 h2-6 h
Participantsdifferent
3-81-3 maintaining, briefing for everyone3-103-8
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Flywheel Map, Friction Points, Growth Levers, Experiment BacklogRAID Log, Status Report SourceFMEA Table, Risk Priority, Mitigation ActionsFault Tree, Critical Paths, Cause Hypotheses, Control Actions
Tagsno overlap
GrowthRetentionConversion
RiskTrackingStakeholdersGovernance
RiskQualityOperationsRoot cause
RiskRoot causeSafety
Add more methods