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 fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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 Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
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.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 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
LowLowLowHigh
Timedifferent
30-60 min30 min Setup, dann laufend10-20 min daily2-6 h
Participantsdifferent
2-81-3 maintaining, briefing for everyone13-10
Formatdifferent
WorkshopAsyncAsyncWorkshop
Outputdifferent
Fishbone Diagram, Cause Categories, Investigation BacklogRAID Log, Status Report SourceDaily Plan, Time Estimates, Review NotesFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
Root causeQualityOperations
RiskTrackingStakeholdersGovernance
PlanningTime managementProductivityOperations
RiskQualityOperationsRoot cause
Add more methods