View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Strategy Execution LoopRisk MatrixRequest for CommentsLASR (Lightweight Approach for Software Reviews)
| Criterion |  Business Strategy Strategy Execution Loop |  Decision Making Risk Matrix |  Architecture Request for Comments |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning. | When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List. | 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 | High | Low | Medium | Medium |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 30-60 min | 1-3 Wochen vom Draft bis zur Entscheidung | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 5-12 | 3-10 | 3-20 Reviewer | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Risk Matrix, Top Risk List | 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 | ExecutionCadenceLearningGovernance | RiskDecisionPrioritizationAssessment | ArchitectureDecisionAsyncGovernance | ArchitectureQualityRiskAssessmentLean |