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 the Morphological Analysis working structure.
Innovation
Morphological Analysis
Paper illustration for Incident Timeline Analysis.
DevOps
Incident Timeline Analysis
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
For a search for solutions with many degrees of freedom, a grid emerges for systematic combinations. The method separates features, variants, and exclusion criteria, so the space gets explored deliberately.For an incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable.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.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.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
1-3 h60-180 min2-4 h15-30 min
Participantsdifferent
2-83-102-62-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Morphological Box, Concept Combinations, Idea ShortlistIncident Timeline, Evidence Log, Delay Analysis, Improvement ActionsBarrier Inventory, Failure Analysis per Barrier, Action BacklogRoot cause notes, Countermeasures
Tagsno overlap
IdeationInnovationCreativity
IncidentTimelineSite Reliability Engineering
Root causeSafetyIncident
Root causeIncidentLeanProblem solving
Add more methods