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 Architecture Decision Record |  Delivery RAID Log |  Decision Making Pre-Mortem |
|---|---|---|---|---|
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 ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30-90 min | 15-45 min | 30 min Setup, dann laufend | 20–45 min |
Participantsdifferent | 2-8 | 1-3 | 1-3 maintaining, briefing for everyone | Small cross-functional group |
Formatdifferent | Workshop + async | Async | Async | Workshop |
Outputdifferent | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | ADR File, Decision Log, Rationale | RAID Log, Status Report Source | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | ConstraintsDecisionPlanningOptions | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance | RiskDecisionFailurePlanning |