Lotte V.
Sample The discovery sprint is great
Ran the five day format with my trio. Friday's decision meeting was the clearest we have had.
Product discovery: validate ideas before you build them
Map assumptions, run customer interviews and cheap experiments, and decide with evidence which ideas deserve engineering time
Created by Yasmin Farouk
- Updated September 2026
- English
- Intermediate
What you will learn
- Identify the main risks behind a product idea
- Map assumptions and prioritise the riskiest to test
- Run story based customer interviews on a weekly cadence
- Design small experiments with clear success criteria
- Interpret qualitative and quantitative evidence without fooling yourself
- Run discovery alongside delivery as a product trio
- Facilitate a one week discovery sprint
Course content
Discovery as a team habit
Learning from customers every week
- Article: Continuous interviewing 10 min
- Article: Story based interviewing 11 min
- Article: Interview snapshots 8 min
- Article: From stories to opportunities 9 min
Designing experiments
- Article: Fake door tests 9 min
- Article: Concierge and Wizard of Oz tests 10 min
- Article: Prototype tests 9 min
- Article: Smoke tests and landing pages 8 min
- Article: Writing a good experiment card 8 min
Reading results honestly
- Article: Qualitative and quantitative signals 9 min
- Article: Small samples and false confidence 8 min
- Article: Bias in discovery 9 min
- Article: Persevere, change or stop 9 min
Discovery alongside delivery
- Article: Dual track working 9 min
- Article: Bringing engineers into discovery 8 min
- Article: Sharing what you learn 8 min
Putting it into practice
- Article: A one week discovery sprint 11 min
- Article: Documenting decisions and evidence 7 min
- Article: Ethics in experiments 8 min
- Quiz: Final check 6 min
Requirements
- Basic familiarity with product development and roadmaps
- Access to customers or users you can talk to is helpful
Description
Most product ideas do not work as expected. Some solve a problem customers do not have, some are too hard to use, and some cost more to build than they return. Product discovery is the work of finding this out cheaply, before the team spends months building. This course teaches discovery as a weekly habit for product trios: a product manager, a designer and an engineer working together.
What you will practise
You will run discovery for a realistic product, a team expense tool whose leadership wants to add a corporate card feature. Instead of debating opinions, you will map assumptions, talk to customers and run small experiments.
- Identify value, usability, feasibility and viability risks
- Map assumptions and pick the riskiest one to test first
- Run continuous, story based customer interviews
- Design fake door, concierge, prototype and smoke tests
- Set success criteria before running an experiment
- Read results honestly and decide whether to continue, change or stop
How the course is structured
Section 1 lays the foundations. Later sections cover interviewing, experiment design, interpreting results and fitting discovery alongside delivery so it does not become a separate phase that slows everything down. The final section walks through a one week discovery sprint from start to finish.
You should already know the basics of product work, such as what a roadmap and a user story are. The course suits product managers, product designers and engineers who want a say in what gets built, not only how.
Who this course is for
- Product managers who want evidence for their decisions
- Product designers involved in early stage work
- Engineers and tech leads in empowered product teams
Instructor
Yasmin Farouk
UX researcher teaching interviews, usability testing and discovery that changes product decisions
- 4.3 instructor rating
- 15 reviews
- 3,980 students
- 2 courses
- Sample
I have spent most of my career as a user researcher on small product teams, where research has to be fast, cheap and directly tied to a decision. I plan studies, recruit participants, run interviews and moderated usability tests, and turn messy notes into findings that a team can act on the same week.
My courses focus on the practical middle of research work: writing a discussion guide that avoids leading questions, choosing between an interview and a test, synthesising with affinity mapping, and presenting results without a forty page deck. I also teach discovery habits for product teams that do not have a dedicated researcher.
Every lesson comes with templates I actually use, and the exercises are built around a realistic product so you can practise on something that feels like work.
Student reviews
Rebecca A.
Sample Assumption mapping changed our roadmap
We mapped assumptions for our biggest planned feature and found the core one had no evidence. Two weeks of tests saved us a quarter.
Mia S.
Sample Honest about evidence
The small sample lesson helped me present findings to leadership without overselling them.
Noah P.
Sample Story based interviews work
My interviews used to be full of opinions. Asking for the story of a specific event made them far more useful.
Ewa Z.
Sample Practical experiments I could run
Experiment cards and pre set criteria are now a team habit. The concierge test example was excellent.
Kwabena T.
Sample Good for engineers too
As a tech lead I liked how the course positions engineers in discovery. I joined my first interviews after this.
Arash G.
Sample Wanted more B2C examples
The expense tool case is detailed, but our consumer app needed different experiment types. Still useful overall.
Keep exploring
All Product Management courses
More in Product Management
$69.99
Enroll now