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 RAPID |  Architecture Request for Comments |  Delivery Cost of Delay |
|---|---|---|---|---|
Purposedifferent | It separates true priorities from noise so it becomes clear what should be done now, scheduled, delegated, or dropped. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 15-30 min | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min |
Participantsdifferent | 1-6 | 3-12 | 3-20 Reviewer | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Eisenhower Matrix, Action List, Delegation Notes | RAPID Role Map, Recommendation, Decision Log | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | CoD Table, Prioritization Sequence |
Tagsno overlap | PrioritizationFocusTasks | DecisionRolesGovernance | ArchitectureDecisionAsyncGovernance | PrioritizationDeliveryEconomicsDecision |