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
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy.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.When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.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
HighMediumLowHigh
Timedifferent
Half day1-3 h1-5 Tage1-4 Wochen
Participantsdifferent
3-122-8Nutzertraffic1-6
Formatdifferent
WorkshopWorkshop + asyncAsyncAsync
Outputdifferent
Leverage Map, Action StrategyContext Map, Integration Patterns, Boundary NotesInterest Metrics, Conversion Signal, Learning NoteExperiment results, Decision log, Learning summary
Tagsno overlap
Systems thinkingChangeStrategy
Domain-Driven DesignBoundariesStrategy
ValidationExperimentsDemandGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods