View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Domain Storytelling |  Knowledge Modeling Teach-back |  Knowledge Modeling Knowledge Mapping |  Agile 4Ls Retrospective |
|---|---|---|---|---|
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. | 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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 1-2 h | 5-20 min | 1-3 h | 45–75 min |
Participantsdifferent | 2-8 | 2-8 | 3-12 | Team members involved |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Understanding Check, Clarification Notes, Learning Gaps | Knowledge Map, Critical Knowledge Areas, Transfer Plan | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | LearningUnderstandingCommunication | KnowledgeMappingRisk | RetrospectiveLearningReflectionTeam |