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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration of Porter’s five competitive forces
Business Strategy
Porter Five Forces
Paper illustration for Domain Context Map
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.Porter Five Forces analyzes the forces that shape competitive pressure and profitability in a market. The view of market structure goes beyond individual competitors and reveals systemic pressure points.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
LowMediumMediumMedium
Timedifferent
30–45 min1-3 h1-3 h1-3 h
Participantsdifferent
1-102-82-83-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
HMW Questions, Challenge Framing, Idea PromptsContext Map, Integration Patterns, Boundary NotesFive Forces Analysis, Competitive Risks, Strategic OptionsDomain Context Map, Boundary Notes, Ownership Map
Tagsno overlap
FramingOpportunityIdeationQuestions
Domain-Driven DesignBoundariesStrategy
StrategyCompetitionMarket
Domain-Driven DesignContextBoundaries
Add more methods