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 Alignment Mapping |  Facilitation Stakeholder 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 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. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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 | Low | Low |
Timedifferent | 60-90 min | 1-2 h | 60–90 min | 1-2 h |
Participantsdifferent | 4-12 | 4-12 | 2-8 | 3-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Alignment Map, Open Issues, Decision Questions | Stakeholder Map, Engagement Plan, Risk Notes | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | RiskArchitectureWorkshopValidation | AlignmentStakeholdersStrategyFacilitation | StakeholdersAlignmentFacilitationChange | CanvasArchitectureAlignmentWorkshop |