View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery MoSCoW | ![]() Facilitation Alignment Mapping | ![]() Decision Making Force Field Analysis | ![]() Business Strategy McKinsey 7S |
|---|---|---|---|---|
Purposedifferent | When a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved. | 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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 | Medium | Low | Medium |
Timedifferent | 30-90 min | 1-2 h | 45-90 min | 2-4 h |
Participantsdifferent | 3-12 | 4-12 | 3-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Prioritized Backlog, Release Scope, Tradeoff Notes | Alignment Map, Open Issues, Decision Questions | Force Field Map, Change Levers, Risk Notes | 7S Assessment, Alignment Gaps, Change Actions |
Tagsno overlap | PrioritizationScopeDecision | AlignmentStakeholdersStrategyFacilitation | ChangeDecisionStrategy | OrganizationStrategyAlignmentChange |



