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 illustration for Weekly Review.
Operations
Weekly Review
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
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.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.For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.
Complexitydifferent
HighMediumLowMedium
Timedifferent
2-6 h1-2 h Setup, laufend30-60 min2-4 h
Participantsdifferent
3-8112-6
Formatdifferent
Workshop + asyncAsyncAsyncWorkshop + async
Outputdifferent
Fault Tree, Critical Paths, Cause Hypotheses, Control ActionsAction Lists, Project List, Review RoutineUpdated Task System, Weekly Focus, Next ActionsBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
RiskRoot causeSafety
ProductivityPlanningTasksExecution
ProductivityExecutionPlanning
Root causeSafetyIncident
Add more methods