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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Flywheel.
Growth
Flywheel
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
A paper-based illustration representing North Star Metric with its core stages and visible working result.
Growth
North Star Metric
Purposedifferent
The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.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 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.When product teams track many metrics, the view of the actual customer outcome easily gets lost. A North Star Metric bundles growth, usage, and value contribution into one signal that makes the system's direction visible.
Complexitydifferent
LowMediumHighMedium
Timedifferent
1-2 h60-120 min1-4 Wochen1-2 h
Participantsdifferent
3-103-81-63-8
Formatdifferent
WorkshopWorkshopAsyncWorkshop + async
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesFlywheel Map, Friction Points, Growth Levers, Experiment BacklogExperiment results, Decision log, Learning summaryNorth Star metric, Input metric tree, Measurement cadence
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
GrowthRetentionConversion
ExperimentsGrowthAnalyticsValidation
GrowthMetricsAlignmentRetention
Add more methods