View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Working Agreements |  Team Design Team Topologies Interaction Modes |  Knowledge Modeling Concept Mapping |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | When collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. | 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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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 | Low | Medium | Medium | Low |
Timedifferent | 45-90 min | Half day | 1-2 h | 45-90 min |
Participantsdifferent | 3-12 | Team-Leads plus Architecture | 1-8 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | Interaction Heat Map, Agreements per Pair | Concept Map, Relationship Labels, Knowledge Gaps | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | TeamCollaborationAgile | TeamAlignmentCollaborationOrganization | KnowledgeConceptsMappingSensemaking | AlignmentStakeholdersTeam |