View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Failure Scenario Analysis |  Innovation Brainstorming |  Innovation SCAMPER |  Innovation Lotus Blossom |
|---|---|---|---|---|
Purposedifferent | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | 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. | 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 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 | 1-3 h | 30-60 min | 30-60 min | 45-90 min |
Participantsdifferent | 3-8 | 4-12 | 2-10 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Idea pool, Theme clusters, Shortlist | SCAMPER Idea List, Concept Shortlist, Variation Notes | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | FailureResilienceRisk | BrainstormingIdeationCreativityWorkshopDivergence | BrainstormingIdeationCreativityReframingInnovation | BrainstormingIdeationCreativityDivergenceWorkshop |