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 Software Architecture Canvas |  Product Discovery Context 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. | 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 an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency. | 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 h | 45-90 min | 30-60 min |
Participantsdifferent | 1-10 | 3-10 | 3-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Architecture Canvas, Goals, Constraints, Quality Attributes | Context canvas, Open questions, Shared context notes | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | FramingOpportunityIdeationQuestions | CanvasArchitectureAlignmentWorkshop | ContextFramingRequirementsCanvas | BrainstormingIdeationCreativityWorkshopDivergence |