View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Expectation MappingStakeholder Salience ModelTeam Topologies Interaction ModesAlignment Mapping
| Criterion | ![]() Facilitation Expectation Mapping | ![]() Facilitation Stakeholder Salience Model | ![]() Team Design Team Topologies Interaction Modes | ![]() Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | When several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. | 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 | Low | Medium | Medium | Medium |
Timedifferent | 45-90 min | 60-90 min | Half day | 1-2 h |
Participantsdifferent | 3-12 | 3-6 | Team-Leads plus Architecture | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Salience Diagram, Strategy per Class | Interaction Heat Map, Agreements per Pair | Alignment Map, Open Issues, Decision Questions |
Tags1 shared | AlignmentStakeholdersTeam | StakeholdersFacilitationAlignmentGovernance | TeamAlignmentCollaborationOrganization | AlignmentStakeholdersStrategyFacilitation |



