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 illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
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
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.Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly.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.
Complexitydifferent
LowMediumLowHigh
Timedifferent
1-2 h1-2 h30-60 min2-6 h
Participantsdifferent
2-81-82-83-10
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeConcept Map, Relationship Labels, Knowledge GapsFishbone Diagram, Cause Categories, Investigation BacklogFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
KnowledgeConceptsMappingSensemaking
Root causeQualityOperations
RiskQualityOperationsRoot cause
Add more methods