View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Dual-Track Agile |  Decision Making Pre-Mortem |  Architecture Request for Comments |  Decision Making Constraint Analysis |
|---|---|---|---|---|
Purposedifferent | When uncertainty and delivery run in parallel, it separates learning work from implementation while keeping both connected. It prevents unvalidated ideas from falling directly into the delivery stream. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | Laufend, Wochen bis Monate | 20–45 min | 1-3 Wochen vom Draft bis zur Entscheidung | 30-90 min |
Participantsdifferent | 4-10 | Small cross-functional group | 3-20 Reviewer | 2-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories | Risk list, Mitigation plan, Assumption log | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries |
Tagsno overlap | AgileDiscoveryDelivery | RiskDecisionFailurePlanning | ArchitectureDecisionAsyncGovernance | ConstraintsDecisionPlanningOptions |