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 |  Agile Sailboat Retrospective |  Agile Sprint Retrospective |  Operations After-Action Review |
|---|---|---|---|---|
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. | 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. | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 1-2 h | 45-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 20-45 min |
Participantsdifferent | 2-8 | 4-12 | Scrum Team | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Sailboat Board, Risks, Improvement Actions | Improvement actions, Team agreements | Lessons learned, Action items, Event summary |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | RetrospectiveTeamImprovement | RetrospectiveImprovementLearning | LearningOperationsImprovement |