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 |  Delivery RAID Log |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 1-3 Tage | 30 min Setup, dann laufend | 15-45 min |
Participantsdifferent | 3-12 | 1-4 | 1-3 maintaining, briefing for everyone | 1-3 |
Formatdifferent | Workshop | Workshop + async | Async | Async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Architecture Views, Cross-view Notes, Rationale | RAID Log, Status Report Source | ADR File, Decision Log, Rationale |
Tagsno overlap | AlignmentStakeholdersTeam | DocumentationStakeholdersArchitecture | RiskTrackingStakeholdersGovernance | ArchitectureRationaleDocumentationGovernance |