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 Assumption Mapping |  Delivery RAID Log |  Architecture Views and Beyond |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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 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 | Medium | Low | Medium | High |
Timedifferent | 45-60 min | 30 min Setup, dann laufend | 1-3 Tage | 1-4 Wochen |
Participantsdifferent | 2-8 | 1-3 maintaining, briefing for everyone | 1-4 | 1-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Assumption map, Test backlog, Risk ranking | RAID Log, Status Report Source | Architecture Views, Cross-view Notes, Rationale | Experiment results, Decision log, Learning summary |
Tagsno overlap | AssumptionsRiskExperimentsValidation | RiskTrackingStakeholdersGovernance | DocumentationStakeholdersArchitecture | ExperimentsGrowthAnalyticsValidation |