View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Constraint Analysis |  Architecture LASR (Lightweight Approach for Software Reviews) |  Operations Kepner-Tregoe |
|---|---|---|---|
Purposedifferent | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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 disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. |
Complexitydifferent | Low | Medium | High |
Timedifferent | 30-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 2-8 h |
Participantsdifferent | 2-8 | 1 or a small team; particularly suitable for 3–4 people | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | 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 | Problem Analysis, Decision Analysis, Risk Plan |
Tagsno overlap | ConstraintsDecisionPlanningOptions | ArchitectureQualityRiskAssessmentLean | Problem solvingRoot causeDecisionOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
