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 Feynman Technique.
Knowledge Modeling
Feynman Technique
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.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
1-2 h1-3 h20-60 min
Participantsdifferent
2-83-101
Formatdifferent
WorkshopWorkshopAsync
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeProcess Map, Handoff List, Improvement BacklogPlain-language Explanation, Knowledge Gaps, Study Notes
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
ProcessOperationsImprovement
LearningKnowledgeUnderstanding
Add more methods

Often compared together

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

Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Paper illustration for Learning Review.
Operations
Learning Review
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective