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 Constraint Analysis |  Architecture Request for Comments |  Decision Making Pre-Mortem |  Decision Making Decision Rights Mapping |
|---|---|---|---|---|
Purposedifferent | 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 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. | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 30-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 20–45 min | 90-180 min |
Participantsdifferent | 2-8 | 3-20 Reviewer | Small cross-functional group | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Risk list, Mitigation plan, Assumption log | Decision Rights Matrix, Agreement |
Tags1 shared | ConstraintsDecisionPlanningOptions | ArchitectureDecisionAsyncGovernance | RiskDecisionFailurePlanning | DecisionGovernanceAlignmentResponsibility |