View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Business Strategy Strategy Execution Loop | ![]() DevOps Game Day | ![]() Agile Mad Sad Glad |
|---|---|---|---|
Purposedifferent | The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning. | In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic. | 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 | High | High | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | Halber Tag | 30-60 min |
Participantsdifferent | 5-12 | 5-20 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Simulation Notes, Gaps List, Updated Runbooks | Emotion Board, Themes, Action Items |
Tagsno overlap | ExecutionCadenceLearningGovernance | ResilienceOperationsIncident | RetrospectiveTeamReflection |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






