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 Team API with its method-specific working model.
Team Design
Team API
Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Purposedifferent
When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document.In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.
Complexitydifferent
LowMediumHighLow
Timedifferent
Half day initial, dann laufend90-180 min1-4 Wochen1-5 Tage
Participantsdifferent
Ein Team plus Stakeholder4-121-6Nutzertraffic
Formatdifferent
Workshop + asyncWorkshopAsyncAsync
Outputdifferent
Team API DocumentDecision Rights Matrix, AgreementExperiment results, Decision log, Learning summaryInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
TeamAlignmentCommunicationService
DecisionGovernanceAlignmentResponsibility
ExperimentsGrowthAnalyticsValidation
ValidationExperimentsDemandGrowth
Add more methods