{"id":83558,"date":"2025-01-31T14:53:04","date_gmt":"2025-01-31T14:53:04","guid":{"rendered":"https:\/\/www.prodpad.com\/?post_type=pp_glossary&p=83558"},"modified":"2025-01-31T14:53:10","modified_gmt":"2025-01-31T14:53:10","slug":"needfinding","status":"publish","type":"pp_glossary","link":"https:\/\/www.prodpad.com\/glossary\/needfinding\/","title":{"rendered":"Needfinding"},"content":{"rendered":"\n
\n
\n
<\/div>\n\n\n\n
\n

What is needfinding?<\/h2>\n\n\n\n

Needfinding is the art of uncovering unmet user needs before the product development process begins. It’s the crucial first step towards building something truly valuable: before a single feature is planned, before a roadmap is drawn, and certainly before any code is written.\u00a0<\/p>\n\n\n\n

Essentially, needfinding is about understanding the problems that your users face, so that your product can address them meaningfully. <\/p>\n\n\n\n

Okay, so far this sounds like your typical customer research – what\u2019s the catch? <\/p>\n\n\n\n

Well, instead of figuring out what customers demand and then doing that, needfinding is all about figuring out why <\/em>they want what they want so that you can create something that addresses that why<\/em>. <\/p>\n\n\n\n

Rooted in design thinking<\/a>, needfinding goes beyond surface-level requests to discover the root of what\u2019s being asked for. While users can tell you what they want, often these desires are informed by solutions they already know. <\/p>\n\n\n\n

What\u2019s truly valuable is uncovering needs that users may not be able to express directly. By prioritizing these insights, product teams ensure they\u2019re not just building a product, but solving a real problem in a meaningful way.<\/p>\n\n\n\n

Done well, needfinding aligns innovation with actual user behavior and expectations, setting the foundation for products that resonate, differentiate, and succeed in the market.<\/p>\n\n\n\n

Needs vs. wants<\/h3>\n\n\n\n

In the 1970s, Stanford professor Robert McKim laid the groundwork for needfinding, distinguishing it from other product research<\/a> methodologies by prioritizing customer needs<\/em> over wants<\/em>. <\/p>\n\n\n\n

While many approaches take customer desires at face value (the customer knows best after all) needfinding digs deeper, focusing on the fundamental problems that require solving.<\/p>\n\n\n\n

But what\u2019s the difference?<\/p>\n\n\n\n

A want<\/em> is a specific feature or solution that a customer believes will improve their experience, often shaped by personal preferences or familiarity with existing options. A need<\/em>, on the other hand, is the core problem that requires solving, whether the customer recognizes it or not. It\u2019s the gap between the current reality and an ideal solution.<\/p>\n\n\n\n

Henry Ford famously illustrated this distinction:<\/p>\n\n\n\n

\n

\u201cIf I had asked people what they wanted, they would have said faster horses.\u201d<\/em><\/strong><\/p>\n<\/blockquote>\n\n\n\n

A faster horse was the want<\/em>. A solution customers could envision based on their experience. But their need<\/em> was more fundamental: faster, more efficient transportation. Ford\u2019s success came not from delivering what people asked for but from solving their deeper problems. What was leading them to ask for faster horses?<\/p>\n\n\n\n

This is why needfinding is such a powerful tool for Product Managers. By focusing on needs<\/em> rather than simply fulfilling wants<\/em>, product teams can break free from incremental improvements and uncover game-changing innovations. Rather than building something that looks like what the competition already offers, needfinding enables teams to identify opportunities for radical product improvement that will benefit their customers.<\/p>\n<\/div>\n\n\n\n

<\/div>\n<\/div>\n\n\n
\n
\"Table<\/figure>\n<\/div>\n\n\n
\n
<\/div>\n\n\n\n
\n

Why is needfinding important?<\/h2>\n\n\n\n

Needfinding is the foundation of user-centric product development. Without it, teams risk building solutions that miss the mark, and focus on output over outcome, like a feature factory<\/a>. This can lead to you wasting time, money, and effort on products no one truly needs. Here\u2019s why it\u2019s essential:<\/p>\n\n\n\n

    \n
  1. Prevents costly mistakes
    <\/strong>Developing a product is not cheap. Without a clear understanding of unmet needs, teams may invest in features or solutions that fail to resonate with users. If you don\u2019t identify the core problem early on, you risk spending time building features that no one will use. By prioritizing needfinding as part of your product discovery, companies can focus their resources on solving real problems, increasing the likelihood of success and minimizing costly mistakes.
    <\/li>\n\n\n\n
  2. Goes beyond what customers say
    <\/strong>Listening to customer requests provides only part of the picture. People often express what they want, but their deeper needs may remain hidden. True needfinding involves observing users in their natural environments, uncovering pain points they may not even articulate. This is where traditional surveys and feedback forms often fall short. Observing users\u2019 behaviors in their own environments allows you to understand the unspoken challenges they face. You can then design solutions that address the root problem – not just the symptoms.
    <\/li>\n\n\n\n
  3. Informs the product roadmap
    <\/strong>Needfinding ensures that every feature and decision on the roadmap is grounded in real user needs. Instead of relying on assumptions or internal guesses, product teams gather qualitative insights through focus groups, interviews, and firsthand observations. This     data-driven Product Management<\/a> approach aligns product strategy with actual market demand, leading to higher adoption rates<\/a> and long-term success. The result? Products that users truly want to use, not just products that you think they need.<\/li>\n<\/ol>\n\n\n\n

    In short, needfinding isn\u2019t just another research step: it\u2019s the key to building products that matter. By understanding what users truly need (not just what they say they want), companies can innovate in ways that create real impact.<\/p>\n\n\n\n

    How do you do needfinding?<\/h2>\n\n\n\n

    Needfinding is hard. It requires blending techniques like observation, questioning, and interpretation to uncover what users truly need. <\/p>\n\n\n\n

    It\u2019s tempting to take requests at face value, but that rarely leads to the best solutions. Think of it like dealing with a toddler who can\u2019t quite express themselves yet. They might beg for an ice cream cone at the beach, so you get them one – only for them to demand a slushy next. You oblige again, but soon enough, they\u2019re still unhappy.<\/p>\n\n\n\n

    Why? Because the real problem isn\u2019t a lack of treats: it\u2019s that they\u2019re overheating. If you take a step back and look deeper, you realize the best solution isn\u2019t ice cream; it\u2019s a shady spot under a parasol and a cool hat. Problem solved.<\/p>\n\n\n\n

    So how do you do the equivalent of this for your customers as a Product Manager? Well, there\u2019s a few methods.<\/p>\n\n\n\n

    Key methods of needfinding<\/h3>\n\n\n\n