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 |  Architecture C4 Model |  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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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 | 1-4 h | 30-60 min |
Participantsdifferent | 1-10 | 3-10 | 1-5 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Architecture Canvas, Goals, Constraints, Quality Attributes | Context Diagram, Container Diagram, Component Diagram | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | FramingOpportunityIdeationQuestions | CanvasArchitectureAlignmentWorkshop | ArchitectureCommunicationVisualization | BrainstormingIdeationCreativityWorkshopDivergence |