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 Team Charter |
|---|---|---|---|
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 a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | Half day | 30 min Setup, dann laufend | 2-4 h |
Participantsdifferent | Team-Leads plus Architecture | 1-3 maintaining, briefing for everyone | 3-12 |
Formatdifferent | Workshop | Async | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | RAID Log, Status Report Source | Team Charter, Working Norms, Role Notes |
Tagsno overlap | TeamAlignmentCollaborationOrganization | RiskTrackingStakeholdersGovernance | TeamAlignmentCollaboration |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






