View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Innovation Lean Startup |  Product Discovery Pretotyping |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. | Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data. | 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 | Low | Medium | Low | Low |
Timedifferent | 15-45 min | Wochen bis Monate je Lernzyklus | Stunden bis wenige Tage | 1-2 Tage |
Participantsdifferent | 1-3 | 2-8 | 1-4 | 1-4 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | LeanStartupValidationMVP | ValidationDemandMVP | ArchitectureDocumentationCommunication |