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 SurfacingRisk StormingSoftware Architecture CanvasArchitecture Communication Canvas
| Criterion |  Decision Making Assumption Surfacing |  Architecture Risk Storming |  Architecture Software Architecture Canvas |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | 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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 45-90 min | 60-90 min | 1-2 h | 60-120 min |
Participantsdifferent | 2-8 | 4-12 | 3-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Assumption List, Critical Assumptions, Learning Plan | Annotated Diagram, Prioritized Risk List, Action Backlog | Architecture Canvas, Goals, Constraints, Quality Attributes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | AssumptionsRiskDecisionDiscovery | RiskArchitectureWorkshopValidation | CanvasArchitectureAlignmentWorkshop | ArchitectureCommunicationStakeholdersCanvas |