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 Architecture Inception Canvas |  Facilitation Storytelling |  Facilitation Stakeholder Mapping |  Architecture Software Architecture Canvas |
|---|---|---|---|---|
Purposedifferent | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. | When an insight needs to have an effect, storytelling translates dry facts into a comprehensible development. It combines context, tension, and consequence into a form that people remember and pass on more easily. | 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 | 1-2 h | 45-120 min | 60–90 min | 1-2 h |
Participantsdifferent | 3-8 | 1-6 | 2-8 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Inception Canvas, Risks, Goal List, Open Questions | Narrative Outline, Key Message, Story Arc | Stakeholder Map, Engagement Plan, Risk Notes | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | AlignmentArchitectureCanvas | CommunicationNarrativeStakeholdersFacilitation | StakeholdersAlignmentFacilitationChange | CanvasArchitectureAlignmentWorkshop |