View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Request for Comments |  Product Discovery Assumption Mapping |  Decision Making Pre-Mortem |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45-60 min | 20–45 min | 60-90 min |
Participantsdifferent | 3-20 Reviewer | 2-8 | Small cross-functional group | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Assumption map, Test backlog, Risk ranking | Risk list, Mitigation plan, Assumption log | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | AssumptionsRiskExperimentsValidation | RiskDecisionFailurePlanning | RiskArchitectureWorkshopValidation |