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 |  Operations After-Action Review |  Agile Start Stop Continue |  Agile Mad Sad Glad |
|---|---|---|---|---|
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. | 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. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 1-2 h | 20-45 min | 30-60 min | 30-60 min |
Participantsdifferent | 2-8 | 3-12 | 3-12 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Lessons learned, Action items, Event summary | Start Stop Continue Board, Improvement Actions | Emotion Board, Themes, Action Items |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | LearningOperationsImprovement | RetrospectiveImprovementTeamReflection | RetrospectiveTeamReflection |