View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Architecture Request for Comments |  Decision Making Constraint Analysis |  Decision Making Pre-Mortem |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30 min Setup, dann laufend | 1-3 Wochen vom Draft bis zur Entscheidung | 30-90 min | 20–45 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-20 Reviewer | 2-8 | Small cross-functional group |
Formatdifferent | Async | Async | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureDecisionAsyncGovernance | ConstraintsDecisionPlanningOptions | RiskDecisionFailurePlanning |