View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture C4 Model |  Team Design Team API |  Facilitation Expectation Mapping |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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 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. | 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 | Low | Low | Medium |
Timedifferent | 1-4 h | Half day initial, dann laufend | 45-90 min | 1-2 h |
Participantsdifferent | 1-5 | Ein Team plus Stakeholder | 3-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Team API Document | Expectation Map, Alignment Notes, Agreements | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | ArchitectureCommunicationVisualization | TeamAlignmentCommunicationService | AlignmentStakeholdersTeam | AlignmentStakeholdersStrategyFacilitation |