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 Blameless Postmortem |  Innovation SCAMPER |  Innovation Rolestorming |
|---|---|---|---|
Purposedifferent | 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. | When a search for ideas stalls, switching roles helps people step outside their own perspective and activate new logics of action. The method reduces habit because contributions arise from a different stance. This brings unfamiliar, often fitting solution approaches into play. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 30-90 min | 30-60 min | 30-60 min |
Participantsdifferent | 3-12 | 2-10 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | SCAMPER Idea List, Concept Shortlist, Variation Notes | Rollenkarten, Ideenpool pro Rolle, Konsolidierte Shortlist |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | BrainstormingIdeationCreativityReframingInnovation | BrainstormingIdeationCreativity |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
