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 Request for Comments |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|
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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 30-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 2-8 | 3-20 Reviewer | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | 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 |
Tagsno overlap | ConstraintsDecisionPlanningOptions | ArchitectureDecisionAsyncGovernance | ArchitectureQualityRiskAssessmentLean |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
