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 a two-by-two Ansoff Matrix with four growth directions
Business Strategy
Ansoff Matrix
Paper illustration of Business Model Stress Test with its method-specific working model.
Business Strategy
Business Model Stress 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.The Ansoff Matrix organizes growth options by market and product relation. It helps weigh expansion, diversification, and adaptation cleanly against each other.A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario.
Complexitydifferent
MediumHighLowHigh
Timedifferent
30-240 min1-4 Wochen45-90 minHalf day
Participantsdifferent
1-61-62-83-8
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
Hypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryExperiment results, Decision log, Learning summaryAnsoff Matrix, Growth Options, Risk NotesStress Test Report, Action Plan per Scenario
Tagsno overlap
TroubleshootingProblem solvingDiagnosis
ExperimentsGrowthAnalyticsValidation
GrowthStrategyMarketPortfolio
StrategyBusiness modelRiskDiagnosis
Add more methods