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 arc42 |  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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | 1-2 Tage | 60-120 min | 45-90 min |
Participantsdifferent | 3-12 | 1-4 | 2-8 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | Architecture Document, Context View, Runtime View, Deployment View | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | TeamAlignmentCollaboration | ArchitectureDocumentationCommunication | ArchitectureCommunicationStakeholdersCanvas | AlignmentStakeholdersTeam |