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 Strategy Value Proposition Canvas |  Architecture Request for Comments |  Architecture arc42 |  Business Strategy Blue Ocean Strategy Canvas |
|---|---|---|---|---|
Purposedifferent | When the value proposition and customer expectation drift apart, it makes fit and mismatch legible. It shows where offering and need don't yet come together. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | The Blue Ocean Strategy Canvas shows how an offering is positioned relative to the market. Differentiation thereby becomes tangible in value factors instead of merely being claimed. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-2 h | 1-3 Wochen vom Draft bis zur Entscheidung | 1-2 Tage | 2-4 h |
Participantsdifferent | 2-8 | 3-20 Reviewer | 1-4 | 3-10 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Value Proposition Canvas, Fit Gaps, Hypotheses | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Architecture Document, Context View, Runtime View, Deployment View | Strategy Canvas, Value Curve, ERRC Actions |
Tagsno overlap | ValueNeedsStrategy | ArchitectureDecisionAsyncGovernance | ArchitectureDocumentationCommunication | StrategyPositioningInnovationValue |