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 |  Operations Learning Review |  Operations After-Action 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. | 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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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 | Medium | Low | High |
Timedifferent | 30–45 min | 1-3 h | 20-45 min | Halber Tag |
Participantsdifferent | 1-10 | 3-10 | 3-12 | 5-20 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Learning Review Notes, System Factors, Improvement Actions | Lessons learned, Action items, Event summary | Simulation Notes, Gaps List, Updated Runbooks |
Tagsno overlap | FramingOpportunityIdeationQuestions | LearningRetrospectiveIncidentOperations | LearningOperationsImprovement | ResilienceOperationsIncident |