View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Request for CommentsArchitecture Communication CanvasExpectation MappingDecision Rights Mapping
| Criterion |  Architecture Request for Comments |  Architecture Architecture Communication Canvas |  Facilitation Expectation Mapping |  Decision Making Decision Rights 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. | 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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 60-120 min | 45-90 min | 90-180 min |
Participantsdifferent | 3-20 Reviewer | 2-8 | 3-12 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Expectation Map, Alignment Notes, Agreements | Decision Rights Matrix, Agreement |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | ArchitectureCommunicationStakeholdersCanvas | AlignmentStakeholdersTeam | DecisionGovernanceAlignmentResponsibility |