View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Runbook |  Product Discovery Opportunity Solution Tree |  Operations ALPEN Method |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. | When discovery keeps swinging between goals, ideas, and learning loops, it creates clear steering logic. It connects the desired outcome, opportunities, and experiments into a legible structure. | With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time. | 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 | Medium | Low | Medium |
Timedifferent | 20-60 min | 1-2 h Setup, laufend | 10-20 min daily | 1-5 Tage |
Participantsdifferent | 1-4 | 2-6 | 1 | Nutzertraffic |
Formatdifferent | Async | Workshop + async | Async | Async |
Outputdifferent | Runbook, Checklist, Escalation Path | Opportunity Solution Tree, Experiment Backlog, Learning Log | Daily Plan, Time Estimates, Review Notes | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | OperationsReliabilityDocumentation | DiscoveryOutcomesExperimentsOpportunity | PlanningTime managementProductivityOperations | ValidationExperimentsDemandDiscovery |