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 |  Product Discovery Smoke Test |  Architecture LASR (Lightweight Approach for Software Reviews) |  Product Discovery Fake Door Test |
|---|---|---|---|---|
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. | 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. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. | When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 30 min Setup, dann laufend | 1-5 Tage | 3–4 h for initial assessment; preparation and deeper analysis additional | 1-5 Tage |
Participantsdifferent | 1-3 maintaining, briefing for everyone | Nutzertraffic | 1 or a small team; particularly suitable for 3–4 people | Nutzertraffic |
Formatdifferent | Async | Async | Workshop + async | Async |
Outputdifferent | RAID Log, Status Report Source | Interest Metrics, Conversion Signal, Learning Note | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ValidationExperimentsDemandGrowth | ArchitectureQualityRiskAssessmentLean | ValidationExperimentsDemandDiscovery |