View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy 5-Minuten VC-Check |  Architecture arc42 |  Architecture Request for Comments |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | The 5-Minute VC Check clarifies opportunities and strategic options at the earliest idea stage. It compares problem quality, customer willingness to pay, alternatives, differentiation, and market potential, and captures the result as a VC-check note, go/sharpen/park decision, and risk list. | 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. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 5-15 min | 1-2 Tage | 1-3 Wochen vom Draft bis zur Entscheidung | 15-45 min |
Participantsdifferent | 1-5 | 1-4 | 3-20 Reviewer | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Async | Async |
Outputdifferent | VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step | Architecture Document, Context View, Runtime View, Deployment View | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | ADR File, Decision Log, Rationale |
Tagsno overlap | StartupValidationCompetition | ArchitectureDocumentationCommunication | ArchitectureDecisionAsyncGovernance | ArchitectureRationaleDocumentationGovernance |