View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:How Might WeSoftware Architecture CanvasArchitecture Decision RecordArchitecture Communication Canvas
| Criterion |  Innovation How Might We |  Architecture Software Architecture Canvas |  Architecture Architecture Decision Record |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 30–45 min | 1-2 h | 15-45 min | 60-120 min |
Participantsdifferent | 1-10 | 3-10 | 1-3 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Architecture Canvas, Goals, Constraints, Quality Attributes | ADR File, Decision Log, Rationale | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | FramingOpportunityIdeationQuestions | CanvasArchitectureAlignmentWorkshop | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationStakeholdersCanvas |