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 Eisenhower Matrix |  Decision Making Risk Matrix |  Architecture Architecture Decision Record |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | It separates true priorities from noise so it becomes clear what should be done now, scheduled, delegated, or dropped. | When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List. | 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. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 15-30 min | 30-60 min | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-6 | 3-10 | 1-3 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop + async | Async | Async |
Outputdifferent | Eisenhower Matrix, Action List, Delegation Notes | Risk Matrix, Top Risk List | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | PrioritizationFocusTasks | RiskDecisionPrioritizationAssessment | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance |