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 Starfish Retrospective |  Operations Process Mapping |
|---|---|---|---|---|
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 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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 1-2 h | 45-90 min | 45-90 min | 1-3 h |
Participantsdifferent | 2-8 | 4-12 | 4-12 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments | Process Map, Handoff List, Improvement Backlog |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam | ProcessOperationsImprovement |