View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Waste AnalysisARID (Active Reviews for Intermediate Designs)Value Stream MappingLASR (Lightweight Approach for Software Reviews)
| Criterion |  Operations Waste Analysis |  Architecture ARID (Active Reviews for Intermediate Designs) |  Delivery Value Stream Mapping |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | 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 | Low | Medium | Medium | Medium |
Timedifferent | 45-120 min | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 h | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 2-8 | Designers, developers as users, and facilitation | 4-10 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Waste Map, Prioritized Waste, Improvement Backlog | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Current-state map, Future-state map, Bottleneck list | 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 | WasteLeanProcess improvement | ArchitectureEngineeringFeedbackValidationTasks | LeanFlowWasteDelivery | ArchitectureQualityRiskAssessmentLean |