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 Incident Command |  Innovation SCAMPER |  Innovation Reverse Brainstorming |  Innovation Lotus Blossom |
|---|---|---|---|---|
Purposedifferent | During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once. | 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. | For persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer. | When a central question feels too large, the method breaks it into neighboring topic fields with their own depth of ideation. It holds structure and openness at the same time, so adjacent perspectives don't get lost. This grows an idea space out of a core problem. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | As needed | 30-60 min | 30-60 min | 45-90 min |
Participantsdifferent | 4-15 | 2-10 | 3-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Incident Log, Action Tracker, Stakeholder Updates | SCAMPER Idea List, Concept Shortlist, Variation Notes | Reverse Ideas, Risk Themes, Solution Ideas | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | IncidentOperationsReliability | BrainstormingIdeationCreativityReframingInnovation | BrainstormingIdeationCreativityRisk | BrainstormingIdeationCreativityDivergenceWorkshop |