View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Fault Tree Analysis | ![]() Innovation Brainstorming | ![]() Innovation Lotus Blossom | ![]() Innovation Reverse Brainstorming |
|---|---|---|---|---|
Purposedifferent | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to 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. | 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. | 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. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | 2-6 h | 30-60 min | 45-90 min | 30-60 min |
Participantsdifferent | 3-8 | 4-12 | 3-10 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Idea pool, Theme clusters, Shortlist | Lotus Diagram, Idea Themes, Shortlist | Reverse Ideas, Risk Themes, Solution Ideas |
Tagsno overlap | RiskRoot causeSafety | BrainstormingIdeationCreativityWorkshopDivergence | BrainstormingIdeationCreativityDivergenceWorkshop | BrainstormingIdeationCreativityRisk |



