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 for Hypothesis-Driven Troubleshooting.
Engineering
Hypothesis-Driven Troubleshooting
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration of Value Chain Analysis with its method-specific working model.
Business Strategy
Value Chain Analysis
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Purposedifferent
When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable.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.Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever 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.
Complexitydifferent
MediumHighHighLow
Timedifferent
30-240 min1-4 WochenHalf day1-5 Tage
Participantsdifferent
1-61-63-8Nutzertraffic
Formatdifferent
Workshop + asyncAsyncWorkshopAsync
Outputdifferent
Hypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryExperiment results, Decision log, Learning summaryValue Chain Map, Lever ListInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
TroubleshootingProblem solvingDiagnosis
ExperimentsGrowthAnalyticsValidation
StrategyBusiness modelDiagnosisAnalysis
ValidationExperimentsDemandGrowth
Add more methods