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 Request for Comments |  Architecture Views and Beyond |
|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 Tage |
Participantsdifferent | 3-12 | 3-20 Reviewer | 1-4 |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | AlignmentStakeholdersTeam | ArchitectureDecisionAsyncGovernance | DocumentationStakeholdersArchitecture |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
