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 Expectation Mapping |  Architecture Views and Beyond |  Team Design Team API |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 45-90 min | 1-3 Tage | Half day initial, dann laufend | 1-2 h |
Participantsdifferent | 3-12 | 1-4 | Ein Team plus Stakeholder | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Architecture Views, Cross-view Notes, Rationale | Team API Document | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | AlignmentStakeholdersTeam | DocumentationStakeholdersArchitecture | TeamAlignmentCommunicationService | AlignmentStakeholdersStrategyFacilitation |