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 Starfish Retrospective |  Agile Sailboat Retrospective |  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. | 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. | 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 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 | 45-90 min | 45-90 min | 30-60 min |
Participantsdifferent | 2-8 | 4-12 | 4-12 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Starfish Board, Practice Changes, Experiments | Sailboat Board, Risks, Improvement Actions | Emotion Board, Themes, Action Items |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | RetrospectiveImprovementExperimentsTeam | RetrospectiveTeamImprovement | RetrospectiveTeamReflection |