View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Team Design Team Topologies Interaction Modes | ![]() Facilitation Stakeholder Salience Model | ![]() Facilitation Expectation Mapping |
|---|---|---|---|
Purposedifferent | 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 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 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. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | Half day | 60-90 min | 45-90 min |
Participantsdifferent | Team-Leads plus Architecture | 3-6 | 3-12 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | Salience Diagram, Strategy per Class | Expectation Map, Alignment Notes, Agreements |
Tags1 shared | TeamAlignmentCollaborationOrganization | StakeholdersFacilitationAlignmentGovernance | AlignmentStakeholdersTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






