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 Fault Tree Analysis.
Operations
Fault Tree Analysis
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration for Weekly Review.
Operations
Weekly Review
Purposedifferent
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.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.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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
HighMediumLowLow
Timedifferent
2-6 h1-2 h Setup, laufend30-60 min30-60 min
Participantsdifferent
3-812-81
Formatdifferent
Workshop + asyncAsyncWorkshopAsync
Outputdifferent
Fault Tree, Critical Paths, Cause Hypotheses, Control ActionsAction Lists, Project List, Review RoutineFishbone Diagram, Cause Categories, Investigation BacklogUpdated Task System, Weekly Focus, Next Actions
Tagsno overlap
RiskRoot causeSafety
ProductivityPlanningTasksExecution
Root causeQualityOperations
ProductivityExecutionPlanning
Add more methods