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
A paper-based illustration representing Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
Purposedifferent
Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected.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.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.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.
Complexitydifferent
LowLowHighHigh
Timedifferent
1-2 h30-60 min2-6 h2-6 h
Participantsdifferent
2-82-83-103-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeFishbone Diagram, Cause Categories, Investigation BacklogFMEA Table, Risk Priority, Mitigation ActionsFault Tree, Critical Paths, Cause Hypotheses, Control Actions
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
Root causeQualityOperations
RiskQualityOperationsRoot cause
RiskRoot causeSafety
Add more methods