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 Six Thinking Hats |  Facilitation Alignment Mapping |  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 topic gets stuck too quickly in the same thinking mode, Six Thinking Hats deliberately separates the perspectives. This means facts, risks, creativity, and emotional signals get worked through one after another instead of mixed together. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 60-90 min | 45-90 min | 1-2 h | 1-2 h |
Participantsdifferent | 4-12 | 4-12 | 4-12 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Perspective Notes, Decision Inputs, Action Items | Alignment Map, Open Issues, Decision Questions | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | RiskArchitectureWorkshopValidation | FacilitationOptionsDecision | AlignmentStakeholdersStrategyFacilitation | CanvasArchitectureAlignmentWorkshop |