--- title: "Product Discovery for Founders: Watch One User Complete the Task" source: https://iaastha.com/insights/blog/product-discovery-for-founders/ type: Post date_published: 2026-10-12 date_modified: 2026-10-12 author: Sarah description: "Product discovery for founders means learning what users really struggle with before you build. The fastest way to start is to sit with one potential user, ask them…" publisher: iAastha Research & Consulting --- # Product Discovery for Founders: Watch One User Complete the Task Product discovery for founders means learning what users really struggle with before you build. The fastest way to start is to sit with one potential user, ask them to do the task you want to improve, stay quiet, and write down every moment they hesitate, backtrack or open another tool. This guide shows you how, with a session checklist and a friction log you can use on this page. ## **What is product discovery for founders?** Product discovery is the work you do before and alongside building. You are trying to answer two questions: is this problem worth solving, and does our solution actually solve it for the people who have it? Many early teams treat discovery as a phase that ends once the first version ships. In practice it never ends. Every new feature is a guess about user behavior, and every guess can be checked cheaply if you look before you build. That is why we say founders should observe users before building features, not after. Discovery is not the same as market research, which tells you how big a market is. It is also not the same as a survey, which tells you what people say. Discovery is about what people do, and why they do it. ## Why watching beats asking People are poor reporters of their own habits. They forget the workaround they built last month, they describe the process as cleaner than it is, and they politely tell you your idea sounds great. Watching removes that filter. Steve Blank, who shaped modern customer development, told founders to get out of the building and test their assumptions with real customers. Steve Blank, The Four Steps to the Epiphany The same thread runs through Y Combinator’s founding advice, which Paul Graham has repeated for years: make something people want. You cannot know what people want from inside your own head, so you have to go and see. Teresa Torres, author of Continuous Discovery Habits, makes the case that product teams should talk to customers every week, not once per quarter. Small, regular contact beats one big research project because it keeps your assumptions honest. ## **How to do user research for a startup: the one-user method** You do not need a lab, a budget or a research team. You need one person, one task and about forty-five minutes. 1. Pick one task. Choose the specific job you want to improve, such as booking a demo, creating an invoice or finding a past order. Vague goals produce vague findings. 2. Find a real user. Ideally someone who does this task today, with or without your product. Friends who are polite are less useful than strangers who are busy. 3. Ask them to show you. Say: “Show me how you do this right now.” Let them use their own tools, tabs and shortcuts. 4. Stay quiet. Resist the urge to help or explain. Silence is uncomfortable, and it is where the truth comes out. 5. Note friction, not opinions. Write down where they pause, reread, backtrack, ask a question or leave for another tool. 6. Debrief with two questions. Ask what was frustrating, and what they would change first. This is one of the simplest user research techniques for startups because it needs almost no setup, and the output is concrete: a short list of moments where your product, or the current workflow, loses people. ## **Customer discovery interviews: questions that work** Observation tells you what happens. [Customer discovery](https://iaastha.com/) interviews tell you the story around it. The best guidance here comes from Rob Fitzpatrick, author of The Mom Test, who argues that you should ask about people’s real past behavior instead of asking whether they would like your idea. Opinions about the future are cheap and often wrong. Specific stories about last week are expensive to invent. ### **Usability testing questions to ask during or after the task** - What were you trying to get done just now? - What did you expect to happen when you clicked that? - Walk me through the last time you did this before today. - What do you do when this goes wrong? - What did you try before this, and why did you stop? ### **Questions to avoid** Avoid “Would you use this?”, “Do you like this design?” and “Do you think this is a good idea?” They invite polite agreement and tell you nothing about behaviour. Replace them with questions about what the person already does.** **** ****How friction becomes a product decision?** After a session you will have a handful of notes. Do not try to fix them all. Rank them by how badly they block the task, then ask whether the cause is in your product, your onboarding or the user’s existing habits. A good rule: if two different users hit the same friction point, treat it as a pattern. If only one did, treat it as a hypothesis and watch the next user with that moment in mind. Over a few weeks this habit changes your roadmap from a list of ideas into a list of verified problems. It also protects you from building the wrong thing. A feature that no observed user struggled to live without is a feature you can safely delay. ## **What is product market fit, and how does discovery relate to it?** Marc Andreessen popularized the term when he described product market fit as being in a good market with a product that can satisfy that market. In plain words, it means people want what you built badly enough to keep using it, pay for it and tell others. Discovery is how you get there. Each observed session either confirms that you are solving a painful problem or shows you where you are not. You do not wait for a magic moment of fit. You move toward it one verified problem at a time. ### A useful product market fit question Ask active users how they would feel if they could no longer use your product. If a large share would be very disappointed, you are closer to fit. If most would shrug, go back to observation and find out what job users actually hire you to do. **Common mistakes founders make in discovery** - Leading the user. Helping them click the right button erases the very friction you came to see. - Only talking to friends. Friends protect your feelings. Strangers protect their time. - Collecting opinions instead of behavior. What people say they will do and what they do are different data. - Testing too late. Waiting until launch means paying the full price of every wrong assumption. - Not writing it down. Memory edits stories. Notes keep them honest. ## ******Frequently asked questions** **What is product discovery for founders?** It is the ongoing work of finding out which problems are worth solving and whether your solution works, before committing time to build. For founders, it centers on observing real users and testing small ideas first. **How many users should I observe?** Start with one. A single session usually reveals at least one friction point. Then repeat each week and look for patterns across five or more sessions. **What is the difference between usability testing and customer discovery?** Usability testing checks whether people can complete a task with a specific design. Customer discovery checks whether the problem exists and matters. Founders need both, and the one-user method gives you a taste of each. **Do I need special tools?** No. A screen share or a chair next to the user, plus a notepad, is enough to begin. Tools help later when you run many sessions. **What is product market fit?** It is the point where your product satisfies a real need in a market, shown by users who return, pay and recommend it without being pushed. ## **Your next step** Before you add another feature, sit with a potential user and watch the task you want to improve. Ask what they do today and where they get stuck. Then ask yourself: what surprised you in your last user conversation? --- Cite as: "Product Discovery for Founders: Watch One User Complete the Task" — iAastha Research & Consulting, https://iaastha.com/insights/blog/product-discovery-for-founders/ Site index for AI: https://iaastha.com/llms.txt