View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Design Design Studio |  Delivery RAID Log |  Decision Making RAPID |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | When several designs need to be quickly put in relation to each other, it makes ideas visible and comparable. It encourages early variants instead of long upfront debates. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels. | 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 | Low | Medium | High |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-8 | 1-3 maintaining, briefing for everyone | 3-12 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Sketches, Concept Directions, Design Decisions | RAID Log, Status Report Source | RAPID Role Map, Recommendation, Decision Log | 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 | SketchingCollaborationIdeation | RiskTrackingStakeholdersGovernance | DecisionRolesGovernance | ArchitectureQualityRiskTradeoffsStakeholders |