View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Stakeholder Mapping |  Architecture arc42 |  Facilitation Alignment Mapping |  Business Strategy McKinsey 7S |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | McKinsey 7S checks whether Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff fit together. Organizational misalignments become visible across multiple levers as a result. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 60–90 min | 1-2 Tage | 1-2 h | 2-4 h |
Participantsdifferent | 2-8 | 1-4 | 4-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Stakeholder Map, Engagement Plan, Risk Notes | Architecture Document, Context View, Runtime View, Deployment View | Alignment Map, Open Issues, Decision Questions | 7S Assessment, Alignment Gaps, Change Actions |
Tagsno overlap | StakeholdersAlignmentFacilitationChange | ArchitectureDocumentationCommunication | AlignmentStakeholdersStrategyFacilitation | OrganizationStrategyAlignmentChange |