Validation & Idea Testing
Learn how to identify customer needs: the main types, six practical ways to find them, and how to rank and test what you learn before you build.

You identify customer needs by collecting evidence of what people are trying to get done and sorting it into a few need types. Then you rank each one by how often it shows up and what it costs people today. The result is a short, ranked list you can build an offer around and test before you spend money on a product.
The work fits in a week or two, and most of the sources are free. What it asks for is discipline: writing down what people say and do, and resisting the urge to fill gaps with your own guesses.
Customer needs are the problems, goals and conditions that lead a person to look for a product or service. A need describes the progress someone wants to make. A product is one of several ways they might get there.
That distinction matters because people rarely describe needs directly. They describe complaints, workarounds and feature requests. A salon owner who asks for "a better spreadsheet" may need to stop losing Sunday evenings to bookkeeping. The spreadsheet is her current solution; the lost evening is the need.
Three terms get mixed up here:
Requests are useful clues. Needs are what you build a business on, because they outlast any one product.
Sorting needs into types helps you notice what you would otherwise miss. Founders tend to hear the practical needs and skip the rest.
The Christensen Institute's Jobs to Be Done theory names three dimensions behind every purchase: functional, social and emotional.
Its best-known example comes from a Detroit-area condo builder. Buyers kept bringing up one thing: what to do with their dining room table. The table stood for family, and deciding its fate was the real barrier to moving.
Focus groups had pointed to bay windows. The builder answered the real need instead, with larger dining rooms, moving services and storage.
Here is how the three dimensions look in practice:
| Type | What it sounds like | Example |
|---|---|---|
| Functional | "I need to get this done" | Send invoices on time |
| Emotional | "I want to feel" or "stop feeling" | Stop worrying about a tax letter |
| Social | "I want to be seen as" | Look professional to a bigger client |
Within the functional layer, most purchases turn on a handful of practical needs:
Bain's research on the elements of value goes further, listing 30 elements in four categories: functional, emotional, life changing and social impact. You do not need all 30. Use the list as a prompt when your notes are full of functional needs and nothing else.
Most of these methods take a few hours. Use at least three, because a need that appears in several sources is far more trustworthy than one that appears in a single conversation.
Talk to people who have the problem and ask them to walk you through the most recent time it came up. What did they do first? What did it cost them? What did they try that did not work?
Past behavior is harder to embellish than opinions about the future. For question design, sample sizes and how to recruit, see the full guide to primary research methods.
If you already sell something, your inbox is a needs log. Tag every question, complaint and cancellation reason for a month. If you are pre-launch, ask a business in your space whether you can read anonymized support requests or sit in on customer calls.
Reviews are customers explaining, unprompted, what they hoped a product would do. Three-star reviews are especially useful because they name what works and what is still missing. Review mining across a few competitors can surface the same two or three unmet needs.
Search queries show needs in the customer's own words, before any salesperson shapes them. Type your topic into a search bar and note the autocomplete suggestions and the related questions. Read forum threads where people ask for help. If you have a website, the queries dimension of the Search Console Performance report groups your traffic by the search query people typed.
People leave out steps when they describe their own work, because the steps feel too obvious to mention. Watching someone do the task, at a counter, on a call, at their desk, shows you the workarounds: the sticky notes, the second spreadsheet, the phone call to check a number.
Turn raw notes into job statements in this form: "When [situation], I want to [progress], so I can [outcome]." For example: "When a client pays late, I want a reminder to go out without me writing it, so I can avoid an awkward conversation." The format forces you to capture the situation and the emotional outcome, which a plain feature list drops.
A pile of notes is not yet a decision. These four steps turn it into one.
| Criterion | Question to ask | Score 3 when |
|---|---|---|
| Frequency | How many sources mention it? | It shows up in three or more methods |
| Intensity | What does it cost people today? | They lose money, time or sleep over it |
| Workaround | Are they already trying to solve it? | They pay for or build a fix now |
| Fit | Could you serve it well? | It matches your skills and budget |
A need with a high workaround score deserves extra attention. People who already spend money or effort on a clumsy fix have shown you the need is real, and they have a budget line you can compete for.
Needs also differ by group. Freelancers and small agencies may share a problem but rank it differently, so score each group separately once you know how to segment your market.
A ranked list is still a set of hypotheses. Testing it is quick, and it saves you from building around the wrong need.
Set your pass mark before you start, such as a number of signups from a set number of people who see the offer. Deciding the bar in advance keeps you honest when the results come in.
Day one, write down who you are serving and the situation you think they are in. Days two and three, read rival reviews and search queries. Days four and five, run five conversations about the last time the problem came up.
Day six, write job statements and group them. Day seven, score the themes and choose the need you will test first.
EntraPath, EntraWorld's optional seven-phase founder roadmap, places Discover and Validate before Design and Build, and this list is the bridge between them. When you are ready to turn your top need into an offer and a plan, join EntraWorld free and build it with AI business tools and a founder network in one place.
Start free. The first 5,000 Premium memberships include a full year of every tool.
Join EntraWorld free →