Start here: why most products fail before launch
Most products do not fail at launch. They fail at the decision to build.
Here is the number that changed how I work. 80% of features in the average software product are rarely or never used after release. Not buggy. Not late. Unused. Somebody decided to build them, a team built them well, and nobody needed them.
The second number: developers spend roughly half their time on avoidable rework. That is the cost of finding out you were wrong after building instead of before.
Product discovery exists to move that finding-out earlier. Done properly it lowers the risk of product failure by about 75%. That is the whole course in one sentence: learn what is true before you commit money to it.
The product death cycle
It looks like this. Nobody uses the product. So you ask customers what features they want. They tell you. You build the features. Nobody uses the product. Repeat until the money runs out.
The cycle is not caused by lazy teams. It is caused by asking the wrong question. Customers are bad at predicting what they need and good at reacting to things that exist. Ask them what to build and you get a list. Watch what they do and you get a problem.
Four risks, one at a time
Every product idea carries four risks. Value: will anyone choose to use it or pay for it? Usability: can they figure out how to use it? Feasibility: can you actually build it with the time, skills and technology you have? Viability: does it work for the business, legally, financially, operationally?
Value risk kills the most startups and gets the least attention, because the other three feel like real work and value feels like a belief. This course spends most of its time on value risk on purpose.
- Value risk: nobody needs it. Modules 1 to 4.
- Usability risk: they cannot use it. Module 7.
- Feasibility risk: you cannot build it. Modules 5 and 6.
- Viability risk: it does not work as a business. Modules 5 and 6, then the Business Modeling course.
Discovery is not a phase. It is the other half of the job.
Delivery is deciding how to build. Discovery is deciding what to build. Good teams run both at once, every week, not discovery for a month and then delivery forever. In a startup the founder is the whole product trio, product, design and engineering, until the first hires arrive. That means you own all four risks personally.
Three stages, roughly. Idea to problem-solution fit usually takes 3 to 6 months, one or two 90-day cycles. Problem-solution fit to product-market fit takes 12 to 18 months. This course covers the first stage and sets you up to measure the second.
How this played out at FOUND
Two founders with 20 years of recruitment experience wanted to build a recruitment platform in Switzerland. They had no product or startup background, so they brought me in. Day one, we did not open Figma. We defined a beachhead: product managers in Zurich with 5+ years of experience looking for a leadership role. Then we went and talked to them.
That decision, made before a line of code, is why FOUND reached product-market fit and most recruitment platforms do not. Everything in this course is a version of that day one.
Name your riskiest risk
Before any method, be honest about where your idea is most likely to die. Write it down. You will check it against evidence in Module 5.
Tick only what is true. Nobody is grading this. The next module assumes it.