View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Context Canvas |  Architecture Request for Comments |  Architecture Quality Attribute Workshop |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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 | Medium | Low |
Timedifferent | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 2-4 h | 15-45 min |
Participantsdifferent | 3-10 | 3-20 Reviewer | 5-15 | 1-3 |
Formatdifferent | Workshop | Async | 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 | ADR File, Decision Log, Rationale |
Tagsno overlap | ContextFramingRequirementsCanvas | ArchitectureDecisionAsyncGovernance | RequirementsArchitectureWorkshop | ArchitectureRationaleDocumentationGovernance |