View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Radar |  Architecture Request for Comments |  Delivery Cost of Delay |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | When capabilities, maturity levels, or market positions need to be compared across several dimensions, overview is easily lost. Radar brings different characteristics into a shared picture and shows patterns faster than tables do. | 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. | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 1-2 h | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min | 15-45 min |
Participantsdifferent | 2-10 | 3-20 Reviewer | 3-8 | 1-3 |
Formatdifferent | Workshop + async | Async | Workshop | Async |
Outputdifferent | Radar Map, Capability Scores, Action Areas | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | CoD Table, Prioritization Sequence | ADR File, Decision Log, Rationale |
Tagsno overlap | AssessmentPortfolioCapability | ArchitectureDecisionAsyncGovernance | PrioritizationDeliveryEconomicsDecision | ArchitectureRationaleDocumentationGovernance |