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 of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
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)
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
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.When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer.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 single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.
Complexitydifferent
LowLowMediumLow
Timedifferent
30-60 min60-90 min3–4 h for initial assessment; preparation and deeper analysis additional15-30 min
Participantsdifferent
3-104-101 or a small team; particularly suitable for 3–4 people2-6
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Risk Matrix, Top Risk ListProblem Cluster, Prioritized Challenge, ExperimentLean 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 checksRoot cause notes, Countermeasures
Tagsno overlap
RiskDecisionPrioritizationAssessment
FacilitationDecisionProblem solvingWorkshop
ArchitectureQualityRiskAssessmentLean
Root causeIncidentLeanProblem solving
Add more methods