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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
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)
Purposedifferent
During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List.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.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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
As needed30-60 min45-90 min3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
4-153-102-51 or a small team; particularly suitable for 3–4 people
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Incident Log, Action Tracker, Stakeholder UpdatesRisk Matrix, Top Risk ListA3 Report, Action Plan, Root Cause AnalysisLean 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 checks
Tagsno overlap
IncidentOperationsReliability
RiskDecisionPrioritizationAssessment
LeanProblem solvingCoachingOperations
ArchitectureQualityRiskAssessmentLean
Add more methods