View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Systems Mapping |  Architecture Software Architecture Canvas |  Facilitation Consensus Workshop |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | 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 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 | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 1-2 h | 1-3 h | 60–90 min |
Participantsdifferent | 3-12 | 3-10 | 5-30 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | System Map, Dependencies, Leverage Points | Architecture Canvas, Goals, Constraints, Quality Attributes | Consensus Clusters, Theme Titles, Priority Areas | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | Systems thinkingMappingBoundariesChange | CanvasArchitectureAlignmentWorkshop | FacilitationConsensusWorkshopAlignment | StakeholdersAlignmentFacilitationChange |