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 |  Agile Example Mapping |  Architecture Architecture Decision Record |  Product Discovery Context 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. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30–45 min | 30-60 min | 15-45 min | 45-90 min |
Participantsdifferent | 1-10 | 3-7 | 1-3 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Example Map, Acceptance Criteria, Open Questions | ADR File, Decision Log, Rationale | Context canvas, Open questions, Shared context notes |
Tagsno overlap | FramingOpportunityIdeationQuestions | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ArchitectureRationaleDocumentationGovernance | ContextFramingRequirementsCanvas |