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 RecordArchitecture Communication CanvasExpectation Mapping
| Criterion |  Facilitation Team Charter |  Architecture Architecture Decision Record |  Architecture Architecture Communication Canvas |  Facilitation Expectation Mapping |
|---|---|---|---|---|
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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | Medium | Low | Medium | Low |
Timedifferent | 2-4 h | 15-45 min | 60-120 min | 45-90 min |
Participantsdifferent | 3-12 | 1-3 | 2-8 | 3-12 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | ADR File, Decision Log, Rationale | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | TeamAlignmentCollaboration | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationStakeholdersCanvas | AlignmentStakeholdersTeam |