methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Intervention Mapping.
Systems Thinking
Intervention Mapping
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Stakeholder 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 a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time.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
LowHighMediumLow
Timedifferent
1-2 h1-5 Tage1-3 h60–90 min
Participantsdifferent
3-104-125-302-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesLogic Model, Change Objectives, Intervention Components, Evaluation PlanConsensus Clusters, Theme Titles, Priority AreasStakeholder Map, Engagement Plan, Risk Notes
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
ChangeSystems thinkingCapability
FacilitationConsensusWorkshopAlignment
StakeholdersAlignmentFacilitationChange
Add more methods