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 |  Domain Modeling Context Map |  Facilitation Stakeholder Mapping |
|---|---|---|---|
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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 30–45 min | 1-3 h | 60–90 min |
Participantsdifferent | 1-10 | 2-8 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Context Map, Integration Patterns, Boundary Notes | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | FramingOpportunityIdeationQuestions | Domain-Driven DesignBoundariesStrategy | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
