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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.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.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.
Complexitydifferent
LowMediumHighLow
Timedifferent
1-2 h1-3 h2-6 h30-60 min
Participantsdifferent
2-83-103-102-8
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeProcess Map, Handoff List, Improvement BacklogFMEA Table, Risk Priority, Mitigation ActionsFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
ProcessOperationsImprovement
RiskQualityOperationsRoot cause
Root causeQualityOperations
Add more methods