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
A paper-based illustration representing WSJF with its core stages and visible working result.
Agile
WSJF
Paper illustration of MORT Analysis with its method-specific working model.
Operations
MORT Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration of Family Tree Analysis with its method-specific working model.
Operations
Family Tree Analysis
Purposedifferent
When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together.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.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring.
Complexitydifferent
HighHighLowMedium
Timedifferent
45-90 minMehrere Tage bis Wochen15-30 min2-4 h
Participantsdifferent
3-102-62-62-6
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Ranked Backlog, Cost-of-Delay AssumptionsMORT Worksheets, Findings per Branch, Corrective Actions, Systemic RecommendationsRoot cause notes, CountermeasuresFamily Tree Diagram, Pattern Notes, Systemic Measures
Tagsno overlap
LeanEconomicsSequencePrioritization
Root causeSafetySystemicIncident
Root causeIncidentLeanProblem solving
Root causePatternsIncidentSystemic
Add more methods