View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Assumption SurfacingArchitecture Inception CanvasArchitecture Decision RecordRequest for Comments
| Criterion | ![]() Decision Making Assumption Surfacing | ![]() Architecture Architecture Inception Canvas | ![]() Architecture Architecture Decision Record | ![]() Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | 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. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. | 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. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 45-90 min | 1-2 h | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 2-8 | 3-8 | 1-3 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop | Async | Async |
Outputdifferent | Assumption List, Critical Assumptions, Learning Plan | Inception Canvas, Risks, Goal List, Open Questions | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | AssumptionsRiskDecisionDiscovery | AlignmentArchitectureCanvas | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance |



