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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration for ALPEN Method
Operations
ALPEN Method
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.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 single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.
Complexitysame
LowLowLow
Timedifferent
20-60 min10-20 min daily15-30 min
Participantsdifferent
1-412-6
Formatdifferent
AsyncAsyncWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathDaily Plan, Time Estimates, Review NotesRoot cause notes, Countermeasures
Tagsno overlap
OperationsReliabilityDocumentation
PlanningTime managementProductivityOperations
Root causeIncidentLeanProblem solving
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis