View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Standard Work Analysis |  Product Strategy ICE Scoring |  Agile WSJF |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | When the same task is done differently depending on the person, the method exposes the reliable core. It creates comparability without unnecessarily choking off needed latitude. | When ideas need sorting quickly, it condenses impact, confidence, and effort into one compact score. It connects customer value, product logic, and decision priorities. The result is captured as an ICE table and top-ideas list. | When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | 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 | Medium | Low | High | Medium |
Timedifferent | 1-3 h | 30-60 min | 45-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 2-6 | 2-8 | 3-10 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Standard Work Sheet, Deviation List, Improved Standard, Training Needs | ICE Table, Top Idea List | Ranked Backlog, Cost-of-Delay Assumptions | 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 | LeanProcessQuality | PrioritizationScoringGrowthDecision | LeanEconomicsSequencePrioritization | ArchitectureQualityRiskAssessmentLean |