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 |  Business Strategy PESTLE Analysis |  Domain Modeling Domain Context Map |
|---|---|---|---|---|
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. | PESTLE Analysis makes political, economic, social, technological, legal, and environmental influences visible. The environment of an initiative is thereby read systematically instead of through isolated trends. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 30–45 min | 1-3 h | 1-3 h | 1-3 h |
Participantsdifferent | 1-10 | 2-8 | 2-10 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Context Map, Integration Patterns, Boundary Notes | PESTLE Map, External Risks, Strategic Questions | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | FramingOpportunityIdeationQuestions | Domain-Driven DesignBoundariesStrategy | StrategyMarketAnalysis | Domain-Driven DesignContextBoundaries |