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 of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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)
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
30-240 min15-45 min3–4 h for initial assessment; preparation and deeper analysis additional45-90 min
Participantsdifferent
1-61-31 or a small team; particularly suitable for 3–4 people2-5
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Hypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryADR File, Decision Log, RationaleLean 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 checksA3 Report, Action Plan, Root Cause Analysis
Tagsno overlap
TroubleshootingProblem solvingDiagnosis
ArchitectureRationaleDocumentationGovernance
ArchitectureQualityRiskAssessmentLean
LeanProblem solvingCoachingOperations
Add more methods