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 Timeline Analysis |  Innovation SCAMPER |  Innovation Brainstorming |  Innovation Lotus Blossom |
|---|---|---|---|---|
Purposedifferent | For an incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable. | 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. | 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 | 60-180 min | 30-60 min | 30-60 min | 45-90 min |
Participantsdifferent | 3-10 | 2-10 | 4-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Incident Timeline, Evidence Log, Delay Analysis, Improvement Actions | SCAMPER Idea List, Concept Shortlist, Variation Notes | Idea pool, Theme clusters, Shortlist | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | IncidentTimelineSite Reliability Engineering | BrainstormingIdeationCreativityReframingInnovation | BrainstormingIdeationCreativityWorkshopDivergence | BrainstormingIdeationCreativityDivergenceWorkshop |