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 Brainstorming |  Innovation Reverse 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 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30–45 min | 1-2 Tage | 30-60 min | 30-60 min |
Participantsdifferent | 1-10 | 1-4 | 4-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Architecture Document, Context View, Runtime View, Deployment View | Idea pool, Theme clusters, Shortlist | Reverse Ideas, Risk Themes, Solution Ideas |
Tagsno overlap | FramingOpportunityIdeationQuestions | ArchitectureDocumentationCommunication | BrainstormingIdeationCreativityWorkshopDivergence | BrainstormingIdeationCreativityRisk |