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 of ICE Scoring with its method-specific working model.
Product Strategy
ICE Scoring
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
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.When ideas need sorting quickly, it condenses impact, confidence, and effort into one compact score. It connects customer value, product logic, and decision priorities. The result is captured as an ICE table and top-ideas list.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
LowLowLowHigh
Timedifferent
1-2 h30-60 min1-5 Tage1-4 Wochen
Participantsdifferent
3-102-8Nutzertraffic1-6
Formatdifferent
WorkshopWorkshop + asyncAsyncAsync
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesICE Table, Top Idea ListInterest Metrics, Conversion Signal, Learning NoteExperiment results, Decision log, Learning summary
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
PrioritizationScoringGrowthDecision
ValidationExperimentsDemandGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods