What do you think?
Rate this book
Validating Product Ideas: Through Lean User Research
Want to know what your users are thinking? If you’re a product manager or developer, this book will help you learn the techniques for finding the answers to your most burning questions about your customers. With step-by-step guidance, Validating Product Ideas shows you how to tackle the research to build the best possible product.
345 pages, Kindle Edition
Published January 19, 2016
209 people are currently reading
1762 people want to read
About the author
Tomer Sharon
4 books52 followersTomer is Head of User Experience at WeWork in New York City leading a team that designs work and living spaces, communities, and services around the world. Formerly a senior user experience researcher at Google Search, Tomer is the author of the book, Validating Product Ideas through Lean User Research (2016) and author of, It’s Our Research: Getting stakeholder buy-in for user experience research projects (2012). He founded and led The Israeli Chapter of the User Experience Professionals’ Association and has been preaching and teaching UX at Google’s LaunchPad program, a bootcamp for early-stage startups around the world, in conferences, and at Treehouse and General Assembly. Tomer holds a master’s degree in Human Factors in Information Design from Bentley University in Waltham, MA. He is @tsharon on Twitter and Instagram.
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 28 of 28 reviews
January 11, 2018
I love books which go straight to the point and explain you how you can do something step-by-step. And Validating Product Ideas is just like that. It's devided based on problems you're solving during product creating and it suggest you one research technique how you can get feedback from your users. And it describes research techniques really deeply. Only think I wasn't satisfied with was picking the regular research methods, because from the value proposition of the book I expected some new, more guerrilla approach, so if you already know, how to do Usability Study, AB testing, In-depth interviews, Tree Testing, Ethnography this book is not already for you. I would suggest it to Product Owners that never heard about getting feedback from their users and Designers on the beginning of their career.
November 14, 2016
I love how this book structures each chapter around a key user research question and an ideal method to answer it. For example, there's a chapter to answer "How do people currently solve a problem?" which Sharon addresses by explaining how to set up and run an observation study.
The book is immediately applicable to practice; I found myself referencing earlier chapters in my daily work before I'd even finished reading. (Although I say "finished reading," and I *did* find it worthwhile to read cover-to-cover, the book's introduction says it's not intended to be read cover-to-cover; rather it's structured so that one chapter guides you through the steps of any particular research project.)
The breakdown in the "who are the users?" chapter of common categories of problems with the phrasing of user interview questions is the best guide I've yet encountered for crafting questions that lead to actionable insights. I'm in the process of using the chapters on "What do the users need?" and "What is the user's workflow?" to set up an experience sampling study and diary studies. The final chapter outlines a process for recruiting participants via social media; I'm looking forward to trying it out as a way of finding participants who aren't already familiar with my organization.
The book is immediately applicable to practice; I found myself referencing earlier chapters in my daily work before I'd even finished reading. (Although I say "finished reading," and I *did* find it worthwhile to read cover-to-cover, the book's introduction says it's not intended to be read cover-to-cover; rather it's structured so that one chapter guides you through the steps of any particular research project.)
The breakdown in the "who are the users?" chapter of common categories of problems with the phrasing of user interview questions is the best guide I've yet encountered for crafting questions that lead to actionable insights. I'm in the process of using the chapters on "What do the users need?" and "What is the user's workflow?" to set up an experience sampling study and diary studies. The final chapter outlines a process for recruiting participants via social media; I'm looking forward to trying it out as a way of finding participants who aren't already familiar with my organization.
June 20, 2019
Super practical, great quotes. It inspired one of my Medium articles :)
February 14, 2022
I will definitely recommend this book to everyone who wants to get more into the research side of things. Very clear introduction guide to most popular methods, with examples and all the usual caveats like finding participants, getting informed consent, and so on. One of those books you should just have on your bookshelf and look into if you need some inspiration or reminder of certain tools.
January 2, 2023
Excellent practical guide for getting started and going through the processes that lead to the launching and running of new products. It's a great one to come back to the chapter you need as you do your research.
October 30, 2018
A light yet dense nice book that covers lean user research technique to answer some questions you might ask on product development phase. the book walks you through several user research techniques to answer questions such as What do people need?, Who are the user?, Can people use the product?.
Author provides step-by-step guide to do each research technique correctly and effectively. I found some repetition on the steps on different techniques, but i supposed it had to be said haha. The book also provides some examples for the tools/documentation that are being used in each research techniques.
The book will be suitable for product people who want to build a product.
Author provides step-by-step guide to do each research technique correctly and effectively. I found some repetition on the steps on different techniques, but i supposed it had to be said haha. The book also provides some examples for the tools/documentation that are being used in each research techniques.
The book will be suitable for product people who want to build a product.
September 5, 2016
When I started reading Validating Product Ideas by Tomer Sharon, I instantly understood what he was trying to do: teach entrepreneurs how to love the problem, not the vision. I’ve been trying to help my clients with this through hands-on, user-research practice. Now I might start assigning reading “homework” from Validating Product Ideas too.
I wrote a more extensive review of this book on The UX Book Club blog.
https://medium.com/the-ux-book-club/a...
I wrote a more extensive review of this book on The UX Book Club blog.
https://medium.com/the-ux-book-club/a...
December 25, 2021
About a 4.4/5 for me
Really valuable information. He's right when he says you shouldn't read it cover to cover but just use for reference for what you're currently working on. (This was for a UX book club so I didn't have much of a choice, and as a warning it's a bit of a slog to get through in one go.)
A number of the suggestions I was able to put into practice, as well as a few reminders of best practice to emphasize with my team (such as the the repeated reminders to run a pilot test, please and thank you), and I'm particularly interested in particular in using the lostness metric in the future.
I disagreed on a couple of the minor takes. For example, that you shouldn't use quantitative questions when identifying needs. Quant questions can be hugely helpful for this, not just in contextualizing information, but also giving a sense of how severe an issue is. For example, asking how many times a week someone has to call in for specific information from shelters. If it's once a month, yeah there might be something there, but any new solution would likely more of a hassle than a help. If it's 18 times a day, that's more likely a need that needs to be addressed.
Also minor issue but an MVP is. Literally a "minimal version of a product with the smallest possible feature set." Like it's even in the name. Minimum Viable Product. Though this could also be lack of consistency within the field (or even within a single organization in one past case).
Other takes I heavily endorse. Such as personas are not a research methodology, and their primary use (alongside user stories) is as a communication tool to gain empathy from the product team for the actual users.
I also appreciated the very specific examples and advice, especially around things like expected time for particular analyses when split different ways, artifact templates, or social etiquette during in person interviews that isn't always explicitly taught. Also convenient to have the recommended sample sizes for particular techniques as well (such as the 500 users for the lostness metric or other findability-based quant studies.)
I would be interested to read more about the tie-in with product metrics (KPIs/OKRs), especially on the quantitative side and benchmarking over time.
Really valuable information. He's right when he says you shouldn't read it cover to cover but just use for reference for what you're currently working on. (This was for a UX book club so I didn't have much of a choice, and as a warning it's a bit of a slog to get through in one go.)
A number of the suggestions I was able to put into practice, as well as a few reminders of best practice to emphasize with my team (such as the the repeated reminders to run a pilot test, please and thank you), and I'm particularly interested in particular in using the lostness metric in the future.
I disagreed on a couple of the minor takes. For example, that you shouldn't use quantitative questions when identifying needs. Quant questions can be hugely helpful for this, not just in contextualizing information, but also giving a sense of how severe an issue is. For example, asking how many times a week someone has to call in for specific information from shelters. If it's once a month, yeah there might be something there, but any new solution would likely more of a hassle than a help. If it's 18 times a day, that's more likely a need that needs to be addressed.
Also minor issue but an MVP is. Literally a "minimal version of a product with the smallest possible feature set." Like it's even in the name. Minimum Viable Product. Though this could also be lack of consistency within the field (or even within a single organization in one past case).
Other takes I heavily endorse. Such as personas are not a research methodology, and their primary use (alongside user stories) is as a communication tool to gain empathy from the product team for the actual users.
I also appreciated the very specific examples and advice, especially around things like expected time for particular analyses when split different ways, artifact templates, or social etiquette during in person interviews that isn't always explicitly taught. Also convenient to have the recommended sample sizes for particular techniques as well (such as the 500 users for the lostness metric or other findability-based quant studies.)
I would be interested to read more about the tie-in with product metrics (KPIs/OKRs), especially on the quantitative side and benchmarking over time.
July 13, 2021
"One of the hardest things to know in product development is who your target audience is." - Tomer Sharon
If you are about to develop a product or service and ask yourself what people need, this book is for you. Sharon gets straight to the point with clear guidelines about user research designs. In addition, he shares tips and tricks for immediate practice.
The book has 9 chapters: Each of the first 8 chapters answers a specific question product developers have about their users. Then, a step-by-step guide answers each question. This structure allows the reader to read the most relevant chapter without reading the book from start to end.
Chapter 9 is about recruiting participants for research.
And yes, it is hard work to get to know users. User research can also be frustrating, if not hurtful. But Tomer Sharon has valid points about why it should be essential for every business to know their target audience. He is not advocating for using "quick & easy" processes but instead encourages product developers and founders to go "into the field". The author presents a variety of methods and approaches for various situations.
If you choose to read the book from start to finish, you'll find lots of repetition. Some sections are even copied 1:1. I found that irritating at first, but the recurrences make sense if you cross-read the book.
If you are about to develop a product or service and ask yourself what people need, this book is for you. Sharon gets straight to the point with clear guidelines about user research designs. In addition, he shares tips and tricks for immediate practice.
The book has 9 chapters: Each of the first 8 chapters answers a specific question product developers have about their users. Then, a step-by-step guide answers each question. This structure allows the reader to read the most relevant chapter without reading the book from start to end.
Chapter 9 is about recruiting participants for research.
And yes, it is hard work to get to know users. User research can also be frustrating, if not hurtful. But Tomer Sharon has valid points about why it should be essential for every business to know their target audience. He is not advocating for using "quick & easy" processes but instead encourages product developers and founders to go "into the field". The author presents a variety of methods and approaches for various situations.
If you choose to read the book from start to finish, you'll find lots of repetition. Some sections are even copied 1:1. I found that irritating at first, but the recurrences make sense if you cross-read the book.
May 30, 2017
Distills user research into simple and actionable methods based on the higher order question at hand (e.g., "what do people need?", "can people use the product?"). Tomer does not attempt to be comprehensive in technique or strategy, and is silent on the deeper synthesis of insights and design implications beyond answer the question at hand.
Focused and useful as a text or reference for experienced researchers, and an able (if not dry; there's no fluff here) introduction for product-or-designfolk who understand the value of research practice, but don't know how to start.
Along with Steve Portigal's 'Interviewing Users' and Erika Hall's 'Just Enough Research', these three books make up the holy trinity of practical research basics: technique, mindset, and method, respectively. You'll have to look elsewhere for deeper theory or insight into the larger design process itself.
Focused and useful as a text or reference for experienced researchers, and an able (if not dry; there's no fluff here) introduction for product-or-designfolk who understand the value of research practice, but don't know how to start.
Along with Steve Portigal's 'Interviewing Users' and Erika Hall's 'Just Enough Research', these three books make up the holy trinity of practical research basics: technique, mindset, and method, respectively. You'll have to look elsewhere for deeper theory or insight into the larger design process itself.
November 20, 2017
Awesome book about lean user research, very useful for beginners, for experienced UX people, and also for non-UXers.
Grouped by how to answer the following questions throughout product development:
What do people need?
Who are the users?
How do people currently solve a problem?
What is the user's workflow?
Do people want the product?
Can people use the product?
Which design generates better results?
How do people find stuff?
Also has an extensive section for recruiting users.
Methods described:
Experience sampling
Interviewing
Personas
Observations
Diary study
Concierge MVP
Fake doors
Usability testing
a/b testing
tree testing
first click testing
Grouped by how to answer the following questions throughout product development:
What do people need?
Who are the users?
How do people currently solve a problem?
What is the user's workflow?
Do people want the product?
Can people use the product?
Which design generates better results?
How do people find stuff?
Also has an extensive section for recruiting users.
Methods described:
Experience sampling
Interviewing
Personas
Observations
Diary study
Concierge MVP
Fake doors
Usability testing
a/b testing
tree testing
first click testing
June 13, 2020
Overall the chapters are well structured, but there's a lot of repetition. It truly wasn't meant to be read from start to finish, as the author outlined in the introduction of the book. I do think that the last chapter (social media participant recruiting) was extremely weak. I expected a well thought through professional approach to effectively recruit participants in a cost efficient way. Instead I thought the approach was quite "spammy" and I'd have my doubts if my or other bigger professional companies would truly consider such approaches. Spamming Facebook groups and pages with screeners? Might do more harm than good for a strong brand...
December 29, 2016
Reads more like a textbook, but very useful while practicing user research. Great for product managers, product designers, marketing researchers, and user researchers. Would pick this up again the next time I do a deep dive into user research. I especially liked the section about poor interview questions and how to make them better. Everyone could benefit from asking better targeted questions.
August 16, 2018
In this book, you'll find 8 questions product builders have to answer with how-to guides for every question.
Tomer Sharon provides detailed instructions starting from how to recruit users for each activity, ending with how to analyze the findings.
I’d recommend the book to all product people (managers, designers, builders, founders).
Tomer Sharon provides detailed instructions starting from how to recruit users for each activity, ending with how to analyze the findings.
I’d recommend the book to all product people (managers, designers, builders, founders).
February 18, 2021
It is a good introduction to user research for those from other fields like product or design. It is written in a format for execution oriented. Hence it can work best when paired with a theoretical foundation, than a sole source.
November 4, 2017
Super awesome and mandatory book if you're developing products. Especially when starting out to build something.
January 26, 2018
One to keep by your desk at all times, and bring to any project kickoff meeting
October 21, 2018
A useful practical guide on how to find a winning idea and build your product.
January 3, 2020
Admittedly quite useful but any book that states that “observation” can also be referred to as “ethnography” is just perpetuating confusion in the field.
February 20, 2020
Think it was harder to read on Hoopla, both because it was hard to read the graphics and was harder to flip around to relevant information.
Read
May 23, 2020decent utility book
February 2, 2016
This book is a must read for anyone building a new product/startup or for anyone who already have a product but needs answers from real users. Tomer wrote an easy to read and step by step book with the best user research and product validation techniques. Instead of just showing them he also define which one is best to answer each different question (like "What do people need?", "Do people want the product?", "Which Design generates better results" and many others). For me the detailed step by step and tons of examples to create better questions and observation methods is worth more than gold for any company or startup who wants to really understand its users.
January 5, 2017
Reads more like a textbook -- would be great for someone practicing UX research to use this as a reference guide. Particularly liked the section on what are bad interview questions and how to change them for the better.
May 16, 2016
A comprehensive guide to validate products
The book contains a lot of tools and techniques that will help to validate and test products. Easy to read and follow.
The book contains a lot of tools and techniques that will help to validate and test products. Easy to read and follow.
January 29, 2017
too practical
Currently reading
May 23, 2020This book is not intended to be read from cover-to-back.
I skimmed through and will be back at it once the need arises.
I skimmed through and will be back at it once the need arises.
February 29, 2024
Great source of information and practical tips on how to effectively and efficiently validate product ideas and prototypes.
April 7, 2017
muy interesante resumen de tecnicas de validacion
Displaying 1 - 28 of 28 reviews