View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Architecture Views and Beyond |  Product Discovery Smoke Test |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | 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. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. |
Complexitydifferent | Low | Medium | Low | High |
Timedifferent | 30 min Setup, dann laufend | 1-3 Tage | 1-5 Tage | 1-4 Wochen |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-4 | Nutzertraffic | 1-6 |
Formatdifferent | Async | Workshop + async | Async | Async |
Outputdifferent | RAID Log, Status Report Source | Architecture Views, Cross-view Notes, Rationale | Interest Metrics, Conversion Signal, Learning Note | Experiment results, Decision log, Learning summary |
Tagsno overlap | RiskTrackingStakeholdersGovernance | DocumentationStakeholdersArchitecture | ValidationExperimentsDemandGrowth | ExperimentsGrowthAnalyticsValidation |