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 Software Architecture Canvas |  Systems Thinking Intervention Mapping |  Facilitation Stakeholder Mapping |
|---|---|---|---|
Purposedifferent | 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. | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. | 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. |
Complexitydifferent | Low | High | Low |
Timedifferent | 1-2 h | 1-5 Tage | 60–90 min |
Participantsdifferent | 3-10 | 4-12 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Architecture Canvas, Goals, Constraints, Quality Attributes | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | CanvasArchitectureAlignmentWorkshop | ChangeSystems thinkingCapability | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
