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
Funnel Analysis workspace showing the question, observations, and next decision.
Growth
Funnel Analysis
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Purposedifferent
When many visitors or users drop off along the way, the reason behind the number often stays hidden. Funnel Analysis exposes these transitions and makes visible exactly where the path collapses.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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-3 h1-3 h45-90 min1-3 h
Participantsdifferent
1-53-102-82-8
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Funnel report, Drop-off analysis, Optimization hypothesesDomain Context Map, Boundary Notes, Ownership MapAssumption List, Critical Assumptions, Learning PlanContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
AnalyticsConversionGrowth
Domain-Driven DesignContextBoundaries
AssumptionsRiskDecisionDiscovery
Domain-Driven DesignBoundariesStrategy
Add more methods