View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy Scenario Planning |  Architecture LASR (Lightweight Approach for Software Reviews) |  Operations A3 Problem Solving |
|---|---|---|---|
Purposedifferent | Scenario Planning opens the view to several plausible futures instead of a single forecast. The method protects strategies from depending on too narrow an expected path. | 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 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. |
Complexitydifferent | High | Medium | Medium |
Timedifferent | 0.5-2 Tage | 3–4 h for initial assessment; preparation and deeper analysis additional | 45-90 min |
Participantsdifferent | 4-12 | 1 or a small team; particularly suitable for 3–4 people | 2-5 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Scenario Set, Strategic Implications, Robust Options | 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 | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | StrategyUncertaintyPlanning | ArchitectureQualityRiskAssessmentLean | LeanProblem solvingCoachingOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
