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 Pretotyping |  Architecture Architecture Decision Record |  Delivery RAID Log |  Architecture Views and Beyond |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | Stunden bis wenige Tage | 15-45 min | 30 min Setup, dann laufend | 1-3 Tage |
Participantsdifferent | 1-4 | 1-3 | 1-3 maintaining, briefing for everyone | 1-4 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | ADR File, Decision Log, Rationale | RAID Log, Status Report Source | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | ValidationDemandMVP | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance | DocumentationStakeholdersArchitecture |