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 Teach-back.
Knowledge Modeling
Teach-back
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration for Feynman Technique.
Knowledge Modeling
Feynman Technique
Purposedifferent
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.Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.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.
Complexitydifferent
LowMediumLow
Timedifferent
5-20 min2-6 h20-60 min
Participantsdifferent
2-82-81
Formatdifferent
Workshop + asyncWorkshop + asyncAsync
Outputdifferent
Understanding Check, Clarification Notes, Learning GapsEvent Model, UI Flow, Commands, Read ModelsPlain-language Explanation, Knowledge Gaps, Study Notes
Tagsno overlap
LearningUnderstandingCommunication
EventsBlueprintDomain-Driven DesignBehavior
LearningKnowledgeUnderstanding
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 Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
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
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review