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
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Paper illustration for Teach-back.
Knowledge Modeling
Teach-back
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 business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold.Teach-back checks whether an explanation actually got through to the other person. The method makes misunderstandings visible early and strengthens shared understanding in advisory and learning situations.
Complexitydifferent
LowMediumLow
Timedifferent
1-2 h1-3 h5-20 min
Participantsdifferent
2-83-82-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeContext Canvas, Glossary, Integration NotesUnderstanding Check, Clarification Notes, Learning Gaps
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
Domain-Driven DesignBoundariesModeling
LearningUnderstandingCommunication
Add more methods

Often compared together

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

Paper illustration for Feynman Technique.
Knowledge Modeling
Feynman Technique
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective