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 Morphological Analysis |  DevOps Game Day |  DevOps Blameless Postmortem |  Innovation SCAMPER |
|---|---|---|---|---|
Purposedifferent | For a search for solutions with many degrees of freedom, a grid emerges for systematic combinations. The method separates features, variants, and exclusion criteria, so the space gets explored deliberately. | 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. | After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures. | 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. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 1-3 h | Halber Tag | 30-90 min | 30-60 min |
Participantsdifferent | 2-8 | 5-20 | 3-12 | 2-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Morphological Box, Concept Combinations, Idea Shortlist | Simulation Notes, Gaps List, Updated Runbooks | Postmortem Doc, Action Items, Timeline | SCAMPER Idea List, Concept Shortlist, Variation Notes |
Tagsno overlap | IdeationInnovationCreativity | ResilienceOperationsIncident | Site Reliability EngineeringIncidentLearningReliability | BrainstormingIdeationCreativityReframingInnovation |