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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
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 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.Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
1-3 h1-3 h1-3 h1-4 Wochen
Participantsdifferent
1-52-83-121-6
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Funnel report, Drop-off analysis, Optimization hypothesesContext Map, Integration Patterns, Boundary NotesSystem Map, Dependencies, Leverage PointsExperiment results, Decision log, Learning summary
Tagsno overlap
AnalyticsConversionGrowth
Domain-Driven DesignBoundariesStrategy
Systems thinkingMappingBoundariesChange
ExperimentsGrowthAnalyticsValidation
Add more methods