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