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 Risk Storming |  Facilitation Problem Framing Workshop |  Architecture Software Architecture Canvas |
|---|---|---|---|
Purposedifferent | 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. | When a team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 60-90 min | 60-120 min | 1-2 h |
Participantsdifferent | 4-12 | 4-10 | 3-10 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | RiskArchitectureWorkshopValidation | FacilitationAlignmentDiscovery | CanvasArchitectureAlignmentWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
