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 of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for ALPEN Method
Operations
ALPEN Method
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
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.With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.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.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.
Complexitydifferent
LowLowHighHigh
Timedifferent
30 min Setup, dann laufend10-20 min daily2-6 h2-6 h
Participantsdifferent
1-3 maintaining, briefing for everyone13-83-10
Formatdifferent
AsyncAsyncWorkshop + asyncWorkshop
Outputdifferent
RAID Log, Status Report SourceDaily Plan, Time Estimates, Review NotesFault Tree, Critical Paths, Cause Hypotheses, Control ActionsFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
RiskTrackingStakeholdersGovernance
PlanningTime managementProductivityOperations
RiskRoot causeSafety
RiskQualityOperationsRoot cause
Add more methods