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
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration of Riskiest Assumption Test with a method-specific labelled workspace.
Product Discovery
Riskiest Assumption 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.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.When an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report.
Complexitysame
MediumMediumMedium
Timedifferent
30-240 min3–4 h for initial assessment; preparation and deeper analysis additional1-2 Wochen pro Iteration
Participantsdifferent
1-61 or a small team; particularly suitable for 3–4 people2-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Hypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checksPrioritized Assumption List, Test Plan, Results Report
Tagsno overlap
TroubleshootingProblem solvingDiagnosis
ArchitectureQualityRiskAssessmentLean
ExperimentsValidationDiscoveryAssumptions
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Experiment Canvas with a method-specific labelled workspace.
Product Discovery
Experiment Canvas