View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Risk Storming |  Growth A/B Testing |  Innovation Reverse Brainstorming |  Innovation Lotus Blossom |
|---|---|---|---|---|
Purposedifferent | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. | 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 | Low | High | Low | Low |
Timedifferent | 60-90 min | 1-4 Wochen | 30-60 min | 45-90 min |
Participantsdifferent | 4-12 | 1-6 | 3-12 | 3-10 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Experiment results, Decision log, Learning summary | Reverse Ideas, Risk Themes, Solution Ideas | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | RiskArchitectureWorkshopValidation | ExperimentsGrowthAnalyticsValidation | BrainstormingIdeationCreativityRisk | BrainstormingIdeationCreativityDivergenceWorkshop |