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 VRIO Framework with its method-specific working model.
Business Strategy
VRIO Framework
Paper illustration of a two-by-two Ansoff Matrix with four growth directions
Business Strategy
Ansoff Matrix
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 VRIO Framework rates resources and capabilities on whether they are Valuable, Rare, Inimitable, and Organized. It compares strengths, risks, market logic, and courses of action. The result is captured as a VRIO table and strategic actions.The Ansoff Matrix organizes growth options by market and product relation. It helps weigh expansion, diversification, and adaptation cleanly against each other.
Complexitydifferent
MediumHighMediumLow
Timedifferent
30-240 min1-4 Wochen90-180 min45-90 min
Participantsdifferent
1-61-63-62-8
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Hypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryExperiment results, Decision log, Learning summaryVRIO Table, Strategic ActionsAnsoff Matrix, Growth Options, Risk Notes
Tagsno overlap
TroubleshootingProblem solvingDiagnosis
ExperimentsGrowthAnalyticsValidation
StrategyDiagnosisBusiness modelCapability
GrowthStrategyMarketPortfolio
Add more methods