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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
A paper-based illustration representing Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
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.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.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.
Complexitydifferent
LowMediumLow
Timedifferent
20-60 min1-3 h1-2 h
Participantsdifferent
13-102-8
Formatdifferent
AsyncWorkshopWorkshop
Outputdifferent
Plain-language Explanation, Knowledge Gaps, Study NotesProcess Map, Handoff List, Improvement BacklogDomain Story, Glossary Notes, Process Narrative
Tagsno overlap
LearningKnowledgeUnderstanding
ProcessOperationsImprovement
KnowledgeDomain-Driven DesignProcess
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