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 Assumption Surfacing |  Architecture Software Architecture Canvas |  Architecture Request for Comments |  Architecture Risk Storming |
|---|---|---|---|---|
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 Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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. | 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 | Low | Low | Medium | Low |
Timedifferent | 45-90 min | 1-2 h | 1-3 Wochen vom Draft bis zur Entscheidung | 60-90 min |
Participantsdifferent | 2-8 | 3-10 | 3-20 Reviewer | 4-12 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Assumption List, Critical Assumptions, Learning Plan | Architecture Canvas, Goals, Constraints, Quality Attributes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | AssumptionsRiskDecisionDiscovery | CanvasArchitectureAlignmentWorkshop | ArchitectureDecisionAsyncGovernance | RiskArchitectureWorkshopValidation |