View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Gemba WalkARID (Active Reviews for Intermediate Designs)ATAM (Architecture Tradeoff Analysis Method)Standard Work Analysis
| Criterion |  Operations Gemba Walk |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Standard Work Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | 30-120 min | 2–4 h review as a planning range; preparation and evaluation additional | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 h |
Participantsdifferent | 2-6 | Designers, developers as users, and facilitation | Evaluation team, architects, and relevant stakeholders | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Observation Notes, Improvement Ideas | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Standard Work Sheet, Deviation List, Improved Standard, Training Needs |
Tagsno overlap | LeanObservationProcessOperations | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureQualityRiskTradeoffsStakeholders | LeanProcessQuality |