View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Agile Example Mapping | ![]() Business Strategy McKinsey 7S | ![]() Facilitation Stakeholder Mapping |
|---|---|---|---|
Purposedifferent | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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 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 | Low | Medium | Low |
Timedifferent | 30-60 min | 2-4 h | 60–90 min |
Participantsdifferent | 3-7 | 3-12 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | 7S Assessment, Alignment Gaps, Change Actions | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | OrganizationStrategyAlignmentChange | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






