View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Context CanvasRequest for CommentsQuality Attribute WorkshopArchitecture Communication Canvas
| Criterion |  Product Discovery Context Canvas |  Architecture Request for Comments |  Architecture Quality Attribute Workshop |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | When an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency. | 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. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 2-4 h | 60-120 min |
Participantsdifferent | 3-10 | 3-20 Reviewer | 5-15 | 2-8 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Context canvas, Open questions, Shared context notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Quality Scenarios, Priority List, Architecture Concerns | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ContextFramingRequirementsCanvas | ArchitectureDecisionAsyncGovernance | RequirementsArchitectureWorkshop | ArchitectureCommunicationStakeholdersCanvas |