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 |  Delivery RAID Log |  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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 | 30 min Setup, dann laufend | 60-90 min |
Participantsdifferent | Team-Leads plus Architecture | 1-3 maintaining, briefing for everyone | 3-6 |
Formatdifferent | Workshop | Async | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | RAID Log, Status Report Source | Salience Diagram, Strategy per Class |
Tagsno overlap | TeamAlignmentCollaborationOrganization | RiskTrackingStakeholdersGovernance | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
