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 |  Architecture Software Architecture Canvas |  Architecture Risk Storming |  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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30-60 min | 1-2 h | 60-90 min | 45-90 min |
Participantsdifferent | 3-12 | 3-10 | 4-12 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Reverse Ideas, Risk Themes, Solution Ideas | Architecture Canvas, Goals, Constraints, Quality Attributes | Annotated Diagram, Prioritized Risk List, Action Backlog | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | BrainstormingIdeationCreativityRisk | CanvasArchitectureAlignmentWorkshop | RiskArchitectureWorkshopValidation | BrainstormingIdeationCreativityDivergenceWorkshop |