View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Standard Work AnalysisDouble DiamondDesign ThinkingLASR (Lightweight Approach for Software Reviews)
| Criterion | ![]() Operations Standard Work Analysis | ![]() Innovation Double Diamond | ![]() Innovation Design Thinking | ![]() 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. | For complex problems with a fuzzy situation, the method cleanly separates search space and decision. It first creates breadth in understanding and then focus in elaboration. This brings open questions, problem definition, and solution path into a traceable movement. | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. | 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 | Medium | High | Medium |
Timedifferent | 1-3 h | Wochen bis Monate | 1 Tag bis mehrere Wochen | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 2-6 | 3-12 | 4-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 | Problem Statement, Solution Options, Prototypes, Deliverables per Phase | Problem Statement, Prototype, Test Learnings | 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 | ProcessDivergenceInnovation | InnovationPrototypeResearch | ArchitectureQualityRiskAssessmentLean |



