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 Mad Sad Glad | ![]() Operations Learning Review | ![]() Agile Start Stop Continue |
|---|---|---|---|---|
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'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. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 1-2 h | 30-60 min | 1-3 h | 30-60 min |
Participantsdifferent | 2-8 | 3-10 | 3-10 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Emotion Board, Themes, Action Items | Learning Review Notes, System Factors, Improvement Actions | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | RetrospectiveTeamReflection | LearningRetrospectiveIncidentOperations | RetrospectiveImprovementTeamReflection |



