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 Waste Analysis |  Architecture LASR (Lightweight Approach for Software Reviews) |  Knowledge Modeling Concept Mapping |
|---|---|---|---|
Purposedifferent | For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. | 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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 45-120 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 1-2 h |
Participantsdifferent | 2-8 | 1 or a small team; particularly suitable for 3–4 people | 1-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Waste Map, Prioritized Waste, Improvement Backlog | 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 | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | WasteLeanProcess improvement | ArchitectureQualityRiskAssessmentLean | KnowledgeConceptsMappingSensemaking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
