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 for Feynman Technique.
Knowledge Modeling
Feynman Technique
A paper-based illustration representing Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Purposedifferent
The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work.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 domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.
Complexitydifferent
LowLowMedium
Timedifferent
20-60 min1-2 h1-3 h
Participantsdifferent
12-83-10
Formatdifferent
AsyncWorkshopWorkshop
Outputdifferent
Plain-language Explanation, Knowledge Gaps, Study NotesDomain Story, Glossary Notes, Process NarrativeDomain Context Map, Boundary Notes, Ownership Map
Tagsno overlap
LearningKnowledgeUnderstanding
KnowledgeDomain-Driven DesignProcess
Domain-Driven DesignContextBoundaries
Add more methods

Often compared together

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

A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration for Teach-back.
Knowledge Modeling
Teach-back
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