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 How Might We |  Architecture arc42 |  Innovation Lotus Blossom |  Innovation Brainstorming |
|---|---|---|---|---|
Purposedifferent | With a stuck problem carrying many implicit assumptions, the method translates observations into open, workable questions. It sharpens the problem frame without pre-thinking the solution, turning frustration or fuzziness into a search space with clear direction. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30–45 min | 1-2 Tage | 45-90 min | 30-60 min |
Participantsdifferent | 1-10 | 1-4 | 3-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Architecture Document, Context View, Runtime View, Deployment View | Lotus Diagram, Idea Themes, Shortlist | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | FramingOpportunityIdeationQuestions | ArchitectureDocumentationCommunication | BrainstormingIdeationCreativityDivergenceWorkshop | BrainstormingIdeationCreativityWorkshopDivergence |