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 |  UX Design Design Studio |  Architecture Software Architecture Canvas |  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. | When several designs need to be quickly put in relation to each other, it makes ideas visible and comparable. It encourages early variants instead of long upfront debates. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30–45 min | 1-3 h | 1-2 h | 30-60 min |
Participantsdifferent | 1-10 | 3-8 | 3-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Sketches, Concept Directions, Design Decisions | Architecture Canvas, Goals, Constraints, Quality Attributes | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | FramingOpportunityIdeationQuestions | SketchingCollaborationIdeation | CanvasArchitectureAlignmentWorkshop | BrainstormingIdeationCreativityWorkshopDivergence |