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 Risk Matrix | ![]() Decision Making Assumption Surfacing | ![]() Architecture Request for Comments | ![]() Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 30-60 min | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 45-60 min |
Participantsdifferent | 3-10 | 2-8 | 3-20 Reviewer | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Risk Matrix, Top Risk List | Assumption List, Critical Assumptions, Learning Plan | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | RiskDecisionPrioritizationAssessment | AssumptionsRiskDecisionDiscovery | ArchitectureDecisionAsyncGovernance | AssumptionsRiskExperimentsValidation |



