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
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 for Hypothesis-Driven Troubleshooting.
Engineering
Hypothesis-Driven Troubleshooting
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Purposedifferent
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 systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional30-240 min60-120 min45-90 min
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people1-62-82-5
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Lean 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 checksHypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryCommunication Canvas, Stakeholder Messages, Architecture Communication PlanA3 Report, Action Plan, Root Cause Analysis
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
TroubleshootingProblem solvingDiagnosis
ArchitectureCommunicationStakeholdersCanvas
LeanProblem solvingCoachingOperations
Add more methods