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 |  Agile ROAM Board |  Facilitation Stakeholder Salience Model |
|---|---|---|---|
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 work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | Half day | 20-40 min initial, dann laufend | 60-90 min |
Participantsdifferent | Team-Leads plus Architecture | 3-15 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | ROAM Board, Owner List | Salience Diagram, Strategy per Class |
Tags1 shared | TeamAlignmentCollaborationOrganization | RiskAgileTrackingAlignment | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
