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 the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time.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.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 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
1-3 h1-5 Tage1-2 h1-4 Wochen
Participantsdifferent
5-30Nutzertraffic3-101-6
Formatdifferent
WorkshopAsyncWorkshopAsync
Outputdifferent
Consensus Clusters, Theme Titles, Priority AreasInterest Metrics, Conversion Signal, Learning NoteArchitecture Canvas, Goals, Constraints, Quality AttributesExperiment results, Decision log, Learning summary
Tagsno overlap
FacilitationConsensusWorkshopAlignment
ValidationExperimentsDemandGrowth
CanvasArchitectureAlignmentWorkshop
ExperimentsGrowthAnalyticsValidation
Add more methods