View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Mad Sad Glad |  Knowledge Modeling Feynman Technique |  DevOps Incident Command |  Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | 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. | The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work. | During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once. | 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 | 30-60 min | 20-60 min | As needed | 30-60 min |
Participantsdifferent | 3-10 | 1 | 4-15 | 3-12 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Emotion Board, Themes, Action Items | Plain-language Explanation, Knowledge Gaps, Study Notes | Incident Log, Action Tracker, Stakeholder Updates | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | RetrospectiveTeamReflection | LearningKnowledgeUnderstanding | IncidentOperationsReliability | RetrospectiveImprovementTeamReflection |