View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Double DiamondRequest for CommentsArchitecture Communication CanvasATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Innovation Double Diamond |  Architecture Request for Comments |  Architecture Architecture Communication Canvas |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | For complex problems with a fuzzy situation, the method cleanly separates search space and decision. It first creates breadth in understanding and then focus in elaboration. This brings open questions, problem definition, and solution path into a traceable movement. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | Medium | High |
Timedifferent | Wochen bis Monate | 1-3 Wochen vom Draft bis zur Entscheidung | 60-120 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-12 | 3-20 Reviewer | 2-8 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Problem Statement, Solution Options, Prototypes, Deliverables per Phase | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | 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 | ProcessDivergenceInnovation | ArchitectureDecisionAsyncGovernance | ArchitectureCommunicationStakeholdersCanvas | ArchitectureQualityRiskTradeoffsStakeholders |