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 PARA Method | ![]() Knowledge Modeling Domain Storytelling | ![]() Agile Starfish Retrospective | ![]() Agile Mad Sad Glad |
|---|---|---|---|---|
Purposedifferent | The PARA Method organizes knowledge into Projects, Areas, Resources, and Archives. It creates order when digital notes, files, and tasks no longer cleanly fit current work. | 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'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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h Setup, laufend | 1-2 h | 45-90 min | 30-60 min |
Participantsdifferent | 1 | 2-8 | 4-12 | 3-10 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Domain Story, Glossary Notes, Process Narrative | Starfish Board, Practice Changes, Experiments | Emotion Board, Themes, Action Items |
Tagsno overlap | KnowledgeProductivityOrganization | KnowledgeDomain-Driven DesignProcess | RetrospectiveImprovementExperimentsTeam | RetrospectiveTeamReflection |



