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 |  Agile Mad Sad Glad |  Facilitation Responsibility Poker |  Agile Start Stop Continue |
|---|---|---|---|---|
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. | 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 it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | 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 | High | Low | Low | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 30-60 min | 45-90 min | 30-60 min |
Participantsdifferent | 5-12 | 3-10 | 3-10 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Emotion Board, Themes, Action Items | Responsibility Map, Role Agreements, Open Questions | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | ExecutionCadenceLearningGovernance | RetrospectiveTeamReflection | RolesResponsibilityTeamFacilitation | RetrospectiveImprovementTeamReflection |