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 |  Decision Making Constraint Analysis |  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. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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 | Low | Low |
Timedifferent | 1-2 h | 1-3 Wochen vom Draft bis zur Entscheidung | 30-90 min | 15-45 min |
Participantsdifferent | 2-10 | 3-20 Reviewer | 2-8 | 1-3 |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Radar Map, Capability Scores, Action Areas | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | ADR File, Decision Log, Rationale |
Tagsno overlap | AssessmentPortfolioCapability | ArchitectureDecisionAsyncGovernance | ConstraintsDecisionPlanningOptions | ArchitectureRationaleDocumentationGovernance |