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 | ![]() Agile Mad Sad Glad | ![]() Agile Start Stop Continue | ![]() Team Design Spotify Model Mapping |
|---|---|---|---|---|
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. | 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 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 landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h Setup, laufend | 30-60 min | 30-60 min | 90-180 min |
Participantsdifferent | 1 | 3-10 | 3-12 | 5-15 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Emotion Board, Themes, Action Items | Start Stop Continue Board, Improvement Actions | Spotify Model Map, Action List |
Tagsno overlap | KnowledgeProductivityOrganization | RetrospectiveTeamReflection | RetrospectiveImprovementTeamReflection | TeamOrganizationAlignmentDiagnosis |



