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 Views and Beyond |  Facilitation Stakeholder Mapping |  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. | 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. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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 | Medium | Low | Low |
Timedifferent | 2-4 h | 1-3 Tage | 60–90 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 Views, Cross-view Notes, Rationale | Stakeholder Map, Engagement Plan, Risk Notes | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | TeamAlignmentCollaboration | DocumentationStakeholdersArchitecture | StakeholdersAlignmentFacilitationChange | AlignmentStakeholdersTeam |