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 Start Stop Continue |  Agile Mad Sad Glad |  Agile Starfish 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. | 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. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 1-2 h | 30-60 min | 30-60 min | 45-90 min |
Participantsdifferent | 2-8 | 3-12 | 3-10 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Start Stop Continue Board, Improvement Actions | Emotion Board, Themes, Action Items | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | RetrospectiveImprovementTeamReflection | RetrospectiveTeamReflection | RetrospectiveImprovementExperimentsTeam |