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 LoopLASR (Lightweight Approach for Software Reviews)Sailboat Retrospective
| Criterion |  Business Strategy Strategy Execution Loop |  Architecture LASR (Lightweight Approach for Software Reviews) |  Agile Sailboat Retrospective |
|---|---|---|---|
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. | 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. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. |
Complexitydifferent | High | Medium | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 3–4 h for initial assessment; preparation and deeper analysis additional | 45-90 min |
Participantsdifferent | 5-12 | 1 or a small team; particularly suitable for 3–4 people | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | 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 | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | ExecutionCadenceLearningGovernance | ArchitectureQualityRiskAssessmentLean | RetrospectiveTeamImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
