methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
How Might We
Innovation
How Might We
Paper illustration of a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
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 goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures.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.GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
30–45 min45-90 min1-3 h1-3 h
Participantsdifferent
1-103-82-82-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
HMW Questions, Challenge Framing, Idea PromptsImpact Map, Outcome Hypotheses, Delivery OptionsContext Map, Integration Patterns, Boundary NotesGap Matrix, Action Plan, Risk Notes
Tagsno overlap
FramingOpportunityIdeationQuestions
OutcomesStrategyBehaviorPlanning
Domain-Driven DesignBoundariesStrategy
StrategyAnalysisPlanning
Add more methods