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 | ![]() Agile Sailboat 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. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. |
Complexitysame | Low | Low | Low |
Timedifferent | 1-2 h | 5-20 min | 45-90 min |
Participantsdifferent | 2-8 | 2-8 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Understanding Check, Clarification Notes, Learning Gaps | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | LearningUnderstandingCommunication | RetrospectiveTeamImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






