View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Team Charter |  Architecture Architecture Decision Record |  Facilitation Expectation Mapping |  Architecture Views and Beyond |
|---|---|---|---|---|
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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 2-4 h | 15-45 min | 45-90 min | 1-3 Tage |
Participantsdifferent | 3-12 | 1-3 | 3-12 | 1-4 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Team Charter, Working Norms, Role Notes | ADR File, Decision Log, Rationale | Expectation Map, Alignment Notes, Agreements | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | TeamAlignmentCollaboration | ArchitectureRationaleDocumentationGovernance | AlignmentStakeholdersTeam | DocumentationStakeholdersArchitecture |