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 |  Product Strategy Product Vision Board |  Architecture Software Architecture Canvas |  Facilitation Alignment 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 a product needs a shared direction, it connects target audience, benefit, and business picture in a clear vision. It makes the envisioned future legible for the team. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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 | Medium | Low | Low | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-2 h | 1-2 h | 1-2 h |
Participantsdifferent | 3-20 Reviewer | 2-8 | 3-10 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Product Vision Board, Vision Statement, Assumptions and Validation Questions | Architecture Canvas, Goals, Constraints, Quality Attributes | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | VisionCanvasStrategyAlignment | CanvasArchitectureAlignmentWorkshop | AlignmentStakeholdersStrategyFacilitation |