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 Double Diamond with its method-specific working model.
Innovation
Double Diamond
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
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
For complex problems with a fuzzy situation, the method cleanly separates search space and decision. It first creates breadth in understanding and then focus in elaboration. This brings open questions, problem definition, and solution path into a traceable movement.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 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
MediumLowLowHigh
Timedifferent
Wochen bis Monate1-2 h1-5 Tage1-4 Wochen
Participantsdifferent
3-123-10Nutzertraffic1-6
Formatdifferent
Workshop + asyncWorkshopAsyncAsync
Outputdifferent
Problem Statement, Solution Options, Prototypes, Deliverables per PhaseArchitecture Canvas, Goals, Constraints, Quality AttributesInterest Metrics, Conversion Signal, Learning NoteExperiment results, Decision log, Learning summary
Tagsno overlap
ProcessDivergenceInnovation
CanvasArchitectureAlignmentWorkshop
ValidationExperimentsDemandGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods