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 McKinsey 7S |  Agile Specification by Example |  Facilitation Stakeholder Mapping |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 2-4 h | 60-90 min pro Feature | 60–90 min | 1-2 h |
Participantsdifferent | 3-12 | 3-6 | 2-8 | 4-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | 7S Assessment, Alignment Gaps, Change Actions | Example Table, Acceptance Tests | Stakeholder Map, Engagement Plan, Risk Notes | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | OrganizationStrategyAlignmentChange | AgileRequirementsExamplesBehavior-Driven Development | StakeholdersAlignmentFacilitationChange | AlignmentStakeholdersStrategyFacilitation |