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 |  Innovation Brainstorming |  Innovation Design Charrette |
|---|---|---|---|---|
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 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. | In a tightly timed design process with many participants, the method pools several lines of thinking in a short time. It brings parallel design energy without letting the discussion tip into endless coordination. This quickly produces solid directions for architecture or space. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 30–45 min | 1-2 h | 30-60 min | Halber Tag bis mehrere Tage |
Participantsdifferent | 1-10 | 3-10 | 4-12 | 10-50 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Architecture Canvas, Goals, Constraints, Quality Attributes | Idea pool, Theme clusters, Shortlist | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction |
Tagsno overlap | FramingOpportunityIdeationQuestions | CanvasArchitectureAlignmentWorkshop | BrainstormingIdeationCreativityWorkshopDivergence | BrainstormingWorkshopCollaborationIdeation |