SlideServe
Menu
Préférences
© SlideServe · v2026

Determining What People Really Want!

leighton-ace avatar
23 diapositives · 387 Views · Nov 09, 2014

In the ever-evolving market, understanding what customers truly want is crucial for successful product development. Prof. Albert L. Page from the University of Illinois Chicago highlights that 60% of new products fail due to a lack of perceived need by users. This presentation offers qualitative techniques to identify customer problems through immersive methods such as being your own customer, critically observing, and voice of customer interviews. By focusing on their challenges, businesses can better align their products with real needs, ultimately increasing success rates in new product launches.

Determining What People Really Want! - slide 1
01 / 23Determining What People Really Want!
1 / 17

Télécharger la présentation

Determining What People Really Want!
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation
  1. Determining What PeopleReally Want! by Prof. Albert L. Page University of Illinois Chicago

  2. People will always need new products which solve their emerging and evolving problems! Therefore you need to find out their problems.

  3. Reality check Remember, only 60% of new products are successful; the rest fail! Absence of a perceived need by the user is the #1 cause of new product failure (Crawford). Thus learning customers’ problems can increase your chances of successful new products.

  4. The Problem People are not accustomed to thinking and talking about their wants and needs. It is much easier for them to talk about their problems, especially their problems with the products they use.

  5. This presentation’s focus: • An overview of qualitative techniques which can be used to identify customers’ problems

  6. Three market research methods to learn customers’ needs • Be your customers • Live with and critically observe your customers • Talk to your customers - Voice of the Customer

  7. The objectives of these techniques: • Provide rich information about your customer’s problems • A deep understanding by the development “doers” • Breadth of understanding across the development team

  8. What is tacit knowledge? • It is knowledge about problems that a person has but cannot articulate • The consumer/user may not perceive problems well enough to verbalize them We must surface and capture this knowledge!

  9. 1. Be your own customers -do what they do • Learn from doing what they do • Experience first hand the issues that are involved in product design trade-offs • Use your own and your competitor’s products • Experience “everyday” and “extraordinary” situations

  10. Be your own customers • Strengths: • Depth of knowledge gained • Ability to capture tacit knowledge • Weaknesses: • Hard to transfer experience to others • Time, expense and access

  11. 2. Critically observe customers • Critically observe, not just watch - ask why! • See both “normal” and “abnormal” • Actions unfold slowly in real time • Gain process and work flow knowledge

  12. Critically observe customers • Strengths: • Capture process and work flow knowledge • Capture tacit knowledge if you ask why • Weaknesses: • Have to translate observations into words • Time and expense

  13. 3. Talk to your customers • People can’t evaluate that with which they are not familiar • They can tell you about product excellences and short-comings in their specific context • Situational in-depth interviews lead people through their problems • Specific questions elicit specific details • Why is as important as what

  14. Buried in the conversations with people are the nuggets of information detailing their problems and thus their needs for solutions

  15. Example - POS systems - clerks • How do you ring up a purchase? • Describe your worst spill • What do you do when the price doesn’t register? • Tell me about the last time your register broke • What is the biggest problem you ever had? • How do you start up/check into the system? • What do you like best/least about the system?

  16. POS systems - store managers • Describe the last report you generated • What happened the last time the system crashed? • How do you close at the end of the month? • What do you want the system to do that it can’t? • What was your last major problem? • What is the system’s best feature? • What is the system’s worst feature?

  17. Another example: Please tell me about the most recent time you experienced a problem with a delivery on pallets.

  18. Generic probing questions: • Why did you mention that feature? • Why is that feature important to you? • What does that feature let you do? • Does that feature cause you problems? • What works well about that feature? • What doesn’t work well about that feature?

  19. Talking to customers • Strengths: • Provides richness of details & contextual information • Faster • Weakness: • Difficult to obtain tacit, work flow and process knowledge

  20. In business-to-business situations being your customer, observing your customer and in-depth personal interviews with them can best be conducted through a program of customer site visits by the multi-functional new product development team.

  21. How do you do it? • Who interacts with customers? Research professionals versus Design team Note: There is a trade-off between professionalism and team exposure and understanding. Teams can be trained to do most qualitative research.

  22. How do you do it? Differences between customers and non-customers or users and non-users • Non-users have the need, may not buy • Customers already buy • Note: You need to talk to both!

  23. In closing, remember these methods will start you along the process to successful new product development by enabling you to determine what consumers really want (ie. solutions to their problems)!