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 Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for Reverse Brainstorming
Innovation
Reverse Brainstorming
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 problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.For persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer.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
MediumLowMediumLow
Timedifferent
1-4 h30-60 min3–4 h for initial assessment; preparation and deeper analysis additional15-30 min
Participantsdifferent
3-83-121 or a small team; particularly suitable for 3–4 people2-6
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Problem Statement, Cause Hypotheses, Confirmed Causes, Action PlanReverse Ideas, Risk Themes, Solution IdeasLean 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
Root causeProblem solvingQualityIncident
BrainstormingIdeationCreativityRisk
ArchitectureQualityRiskAssessmentLean
Root causeIncidentLeanProblem solving
Add more methods