View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy Strategy Map |  Architecture arc42 |  Facilitation Alignment Mapping |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | A Strategy Map translates strategy into a few connected objectives across perspectives such as finance, customers, processes, and learning. This makes visible which capabilities and activities are meant to drive which results. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | 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 | 2-4 h workshop plus review | 1-2 Tage | 1-2 h | 60–90 min |
Participantsdifferent | 4-10 | 1-4 | 4-12 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Strategy Map, Objective Set, Cause-Effect Hypotheses | Architecture Document, Context View, Runtime View, Deployment View | Alignment Map, Open Issues, Decision Questions | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | AlignmentExecutionGoalsCausality | ArchitectureDocumentationCommunication | AlignmentStakeholdersStrategyFacilitation | StakeholdersAlignmentFacilitationChange |