View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  DevOps Game Day |  Innovation SCAMPER |  Innovation Brainstorming |
|---|---|---|---|
Purposedifferent | 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. | For an existing solution under pressure to change, the method deliberately opens space for systematic variants. It directs attention to rebuilding, combining, and repurposing rather than only new basic ideas. This produces concrete evolution paths for products, offerings, or workflows. | When a team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. |
Complexitydifferent | High | Low | Low |
Timedifferent | Halber Tag | 30-60 min | 30-60 min |
Participantsdifferent | 5-20 | 2-10 | 4-12 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | SCAMPER Idea List, Concept Shortlist, Variation Notes | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | ResilienceOperationsIncident | BrainstormingIdeationCreativityReframingInnovation | BrainstormingIdeationCreativityWorkshopDivergence |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
