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 |  Product Discovery Pretotyping |  Architecture C4 Model |  Innovation Lean Startup |
|---|---|---|---|---|
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. | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 15-45 min | Stunden bis wenige Tage | 1-4 h | Wochen bis Monate je Lernzyklus |
Participantsdifferent | 1-3 | 1-4 | 1-5 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Context Diagram, Container Diagram, Component Diagram | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ValidationDemandMVP | ArchitectureCommunicationVisualization | LeanStartupValidationMVP |