View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Scatter Diagram |  Decision Making Assumption Surfacing |  Architecture LASR (Lightweight Approach for Software Reviews) |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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 | Low | Low | Medium | Low |
Timedifferent | 30-90 min | 45-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 15-30 min |
Participantsdifferent | 1-4 | 2-8 | 1 or a small team; particularly suitable for 3–4 people | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Scatter Plot, Korrelationsnotiz, Hypothesenliste | Assumption List, Critical Assumptions, Learning Plan | 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 checks | Root cause notes, Countermeasures |
Tagsno overlap | Root causeQualityVisualization | AssumptionsRiskDecisionDiscovery | ArchitectureQualityRiskAssessmentLean | Root causeIncidentLeanProblem solving |