View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Innovation Reverse Brainstorming | ![]() Operations Family Tree Analysis | ![]() Operations MORT Analysis | ![]() Innovation Lotus Blossom |
|---|---|---|---|---|
Purposedifferent | 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. | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. | For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | 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 | Low | Medium | High | Low |
Timedifferent | 30-60 min | 2-4 h | Mehrere Tage bis Wochen | 45-90 min |
Participantsdifferent | 3-12 | 2-6 | 2-6 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Reverse Ideas, Risk Themes, Solution Ideas | Family Tree Diagram, Pattern Notes, Systemic Measures | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | BrainstormingIdeationCreativityRisk | Root causePatternsIncidentSystemic | Root causeSafetySystemicIncident | BrainstormingIdeationCreativityDivergenceWorkshop |



