View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Intervention MappingSoftware Architecture CanvasStakeholder MappingArchitecture Inception Canvas
| Criterion | ![]() Systems Thinking Intervention Mapping | ![]() Architecture Software Architecture Canvas | ![]() Facilitation Stakeholder Mapping | ![]() Architecture Architecture Inception Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 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. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | 1-5 Tage | 1-2 h | 60–90 min | 1-2 h |
Participantsdifferent | 4-12 | 3-10 | 2-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Architecture Canvas, Goals, Constraints, Quality Attributes | Stakeholder Map, Engagement Plan, Risk Notes | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | ChangeSystems thinkingCapability | CanvasArchitectureAlignmentWorkshop | StakeholdersAlignmentFacilitationChange | AlignmentArchitectureCanvas |



