View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Standard Work AnalysisARID (Active Reviews for Intermediate Designs)ATAM (Architecture Tradeoff Analysis Method)Assumption Mapping
| Criterion | ![]() Operations Standard Work Analysis | ![]() Architecture ARID (Active Reviews for Intermediate Designs) | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 1-3 h | 2–4 h review as a planning range; preparation and evaluation additional | Several meetings plus preparation and analysis; total effort depends on scope | 45-60 min |
Participantsdifferent | 2-6 | Designers, developers as users, and facilitation | Evaluation team, architects, and relevant stakeholders | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Standard Work Sheet, Deviation List, Improved Standard, Training Needs | 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 | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | LeanProcessQuality | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureQualityRiskTradeoffsStakeholders | AssumptionsRiskExperimentsValidation |



