View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Process MappingATAM (Architecture Tradeoff Analysis Method)LASR (Lightweight Approach for Software Reviews)Gemba Walk
| Criterion |  Operations Process Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture LASR (Lightweight Approach for Software Reviews) |  Operations Gemba Walk |
|---|---|---|---|---|
Purposedifferent | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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 there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 3–4 h for initial assessment; preparation and deeper analysis additional | 30-120 min |
Participantsdifferent | 3-10 | Evaluation team, architects, and relevant stakeholders | 1 or a small team; particularly suitable for 3–4 people | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | 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 | Observation Notes, Improvement Ideas |
Tagsno overlap | ProcessOperationsImprovement | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureQualityRiskAssessmentLean | LeanObservationProcessOperations |