View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation How Might We |  Facilitation Delegation Poker |  Operations Learning Review |  DevOps Game Day |
|---|---|---|---|---|
Purposedifferent | With a stuck problem carrying many implicit assumptions, the method translates observations into open, workable questions. It sharpens the problem frame without pre-thinking the solution, turning frustration or fuzziness into a search space with clear direction. | When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice. | 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. | 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. |
Complexitydifferent | Low | Low | Medium | High |
Timedifferent | 30–45 min | 45-90 min | 1-3 h | Halber Tag |
Participantsdifferent | 1-10 | 3-10 | 3-10 | 5-20 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Delegation Board, Decision Boundaries, Role Agreements | Learning Review Notes, System Factors, Improvement Actions | Simulation Notes, Gaps List, Updated Runbooks |
Tagsno overlap | FramingOpportunityIdeationQuestions | AutonomyRolesTeam | LearningRetrospectiveIncidentOperations | ResilienceOperationsIncident |