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
Paper illustration for ALPEN Method
Operations
ALPEN Method
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
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.With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.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
MediumLowMediumHigh
Timedifferent
30-240 min10-20 min daily1-3 hHalf day
Participantsdifferent
1-612-83-8
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
Hypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryDaily Plan, Time Estimates, Review NotesGap Matrix, Action Plan, Risk NotesStress Test Report, Action Plan per Scenario
Tagsno overlap
TroubleshootingProblem solvingDiagnosis
PlanningTime managementProductivityOperations
StrategyAnalysisPlanning
StrategyBusiness modelRiskDiagnosis
Add more methods