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 Request for Comments |  Team Design Team API |  Architecture Architecture Communication Canvas |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. | 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 | 1-3 Wochen vom Draft bis zur Entscheidung | Half day initial, dann laufend | 60-120 min | 45-90 min |
Participantsdifferent | 3-20 Reviewer | Ein Team plus Stakeholder | 2-8 | 3-12 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Team API Document | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | TeamAlignmentCommunicationService | ArchitectureCommunicationStakeholdersCanvas | AlignmentStakeholdersTeam |