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
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Paper illustration for Flywheel.
Growth
Flywheel
Funnel Analysis workspace showing the question, observations, and next decision.
Growth
Funnel Analysis
Purposedifferent
When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold.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.Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-3 h1-3 h60-120 min1-3 h
Participantsdifferent
3-83-123-81-5
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopAsync
Outputdifferent
Context Canvas, Glossary, Integration NotesSystem Map, Dependencies, Leverage PointsFlywheel Map, Friction Points, Growth Levers, Experiment BacklogFunnel report, Drop-off analysis, Optimization hypotheses
Tagsno overlap
Domain-Driven DesignBoundariesModeling
Systems thinkingMappingBoundariesChange
GrowthRetentionConversion
AnalyticsConversionGrowth
Add more methods