View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Team CharterArchitecture Decision RecordExpectation MappingTeam Topologies Interaction Modes
| Criterion |  Facilitation Team Charter |  Architecture Architecture Decision Record |  Facilitation Expectation Mapping |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
Purposedifferent | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 2-4 h | 15-45 min | 45-90 min | Half day |
Participantsdifferent | 3-12 | 1-3 | 3-12 | Team-Leads plus Architecture |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | ADR File, Decision Log, Rationale | Expectation Map, Alignment Notes, Agreements | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | TeamAlignmentCollaboration | ArchitectureRationaleDocumentationGovernance | AlignmentStakeholdersTeam | TeamAlignmentCollaborationOrganization |