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 Working Backwards |  Architecture Request for Comments |  Architecture Architecture Decision Record |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | When the target state and benefit need to be clear first, it thinks backward from the desired outcome into the product logic. It sharpens vision, objections, and value proposition before elaboration. | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 4-8 h, mehrere Iterationen | 1-3 Wochen vom Draft bis zur Entscheidung | 15-45 min | 1-2 Tage |
Participantsdifferent | 2-6 | 3-20 Reviewer | 1-3 | 1-4 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Future Press Release, FAQ, Vision Statement | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | VisionNarrativeAlignment | ArchitectureDecisionAsyncGovernance | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication |