View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Concept Mapping |  Facilitation Expectation Mapping |  Team Design Team API |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-2 h | 45-90 min | Half day initial, dann laufend | 60-120 min |
Participantsdifferent | 1-8 | 3-12 | Ein Team plus Stakeholder | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Expectation Map, Alignment Notes, Agreements | Team API Document | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | AlignmentStakeholdersTeam | TeamAlignmentCommunicationService | ArchitectureCommunicationStakeholdersCanvas |