View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Decision JamAssumption SurfacingARID (Active Reviews for Intermediate Designs)ATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Facilitation Decision Jam |  Decision Making Assumption Surfacing |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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. |
Complexitydifferent | Low | Low | Medium | High |
Timedifferent | 60-90 min | 45-90 min | 2–4 h review as a planning range; preparation and evaluation additional | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 4-10 | 2-8 | Designers, developers as users, and facilitation | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Problem Cluster, Prioritized Challenge, Experiment | Assumption List, Critical Assumptions, Learning Plan | 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 |
Tagsno overlap | FacilitationDecisionProblem solvingWorkshop | AssumptionsRiskDecisionDiscovery | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureQualityRiskTradeoffsStakeholders |