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 Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration for Weekly Review.
Operations
Weekly Review
Purposedifferent
For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.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.In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable.
Complexitydifferent
MediumMediumHighLow
Timedifferent
1-3 h1-2 h Setup, laufend2-6 h30-60 min
Participantsdifferent
2-813-101
Formatdifferent
WorkshopAsyncWorkshopAsync
Outputdifferent
Cause Tree, Evidence Notes, CountermeasuresAction Lists, Project List, Review RoutineFMEA Table, Risk Priority, Mitigation ActionsUpdated Task System, Weekly Focus, Next Actions
Tagsno overlap
Root causeTreeIncidentQuality
ProductivityPlanningTasksExecution
RiskQualityOperationsRoot cause
ProductivityExecutionPlanning
Add more methods