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 |  DevOps Game Day |  Operations Process Mapping |  Operations After-Action Review |
|---|---|---|---|---|
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. | 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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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. |
Complexitydifferent | Low | High | Medium | Low |
Timedifferent | 30–45 min | Halber Tag | 1-3 h | 20-45 min |
Participantsdifferent | 1-10 | 5-20 | 3-10 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Simulation Notes, Gaps List, Updated Runbooks | Process Map, Handoff List, Improvement Backlog | Lessons learned, Action items, Event summary |
Tagsno overlap | FramingOpportunityIdeationQuestions | ResilienceOperationsIncident | ProcessOperationsImprovement | LearningOperationsImprovement |