Great video, although this was not what I was looking for. You should have probably named the video as "how to plan a product discovery schedule". The question I was trying to answer was in the beginners space "how to do product discovery". Thank you anyway, your recommendations can help anyone planning a project that involves different stakeholders.
Thanks so much! Here are some of my all-time favorites (beyond the usual suspects): *Validating Product Ideas Through Lean User Research by Tomer Sharon* What I love most about this book is its insane focus on practicality. It doesn't bother you with flashy introductions or stories but gets right at it. In addition, you can use it as a catalog. Skimming it for whatever you need at any given time. It's also organizing techniques around questions (i.e., "What do users need?") to help you select what framework to apply when. The book also sticks to the basics without re-inventing the wheel. *Radical Candor by Kim S. Scott* Probably the most transformative book of my career in regards to soft skills. It helped break with traditional limiting beliefs (like the "shit sandwich) and how to balance giving it straight to people and not being a jerk. As someone who was sometimes a bit too focused on harmony, this book helped me approach hard(er) conversations with more confidence and to embrace those to create clarity. *Just Enough Research by Erika Hall* I love diving into writing from domain experts that operate within the broader craft of Product Management. As a User Researcher, Erika Hall is focused on this particular craft with high-quality standards, without making it sound only she could to great research. This book is complementary to the work of Tomer Sharon (see the first recommendation) as a deeper layer of research activities. It also stays away from adding fluff through artificially created frameworks and buzzwords and instead focused on the necessary basics and categories like differentiating Competitive Research from Evaluative Research, etc. *Crossing the Chasm by Geoffrey A. Moore* Recently, I've seen some discussion around how startups or solutions are driving a "wedge" into a market to gain adoption. I think this is similar to the concept of the chasm in this book and it's such an excellent reminder for product companies to think strategically about the adoption of a new feature or entire product. The chasm refers to the 'handover' process between user groups along the lifecycle Disruptive and innovative products don't cross the chasm organically. They require smart efforts to cross the chasm in order to avoid remaining stuck in an earlier but maybe smaller customer segment.
Woah Tim, Thank you for this comprehensive response.. I would definitely be purchasing this books especially the soft skill, am a new Business Analyst, i did the course during the lockdown... And i just got a role but am definitely being challenged in terms of the soft skills.. Thank you for your recommendations
Hey Tim, Thanks for putting out this great content. I have been leaning on it lately to get a Discovery process going and it has helped me shape my thoughts on how to tackle the situation. I really appreciate it, keep up the great work!
@@herbigt You're very much welcome Tim! If you don't mind, I'd like to create the subtitles for one other video you have on your channel at no cost! I see you have 3 more. What do you think?
Thanks Tim... great presentation. Do you know of a tool or a template that people can use to ensure that everyone is clear on the discovery process - (I mean get a buy-in on the discovery process) and can follow along as a way to ensure ppl don't keep jumping into the solution from the start.
Such a great question, Syed. I have seen lots of success with teams that create an explicit understanding around the problem space using alignment frameworks like the Mission Briefing: herbig.co/product-discovery/#mission-briefing But, as with any tool, it‘s about how you use it. Even the best framework can be misused by solely focusing on features, cramming all pet projects in there, or never revisiting it again. Make sure to keep this in mind.
Hey Tim! Thank you for a such great content in this video. I would say this is on of the best explanation of the Prodcut Discovery process. I have few questions for you. What do you think about Double Dimaond approach from Design Thinking? Is it good enough to be used for Product Discovery?
Hey Ruslan, thanks for the question. I believe that the general act of diverging and converging is very useful for Discovery as a whole and the individual activities in it. Like co-creating a research interview guide or collaborative ideation sessions after understanding the problem space. But, in general, I wouldn’t be too rigid about the order of your activities and recommend to adapt to new insights. Your progress should be more important than the process.
Great question, Oleksandr. Since I'm a firm believer in individual better practices, rather than over-generalized examples, I typically don't talk about specific scenarios outside of my course student community calls.
Tim, this explanation of the process is excellent. I have a question about post product launch and the kind of activities you feel are appropriate at that point, and the discovery process you might utilize for a V2 of a launched product where there are “high confidence” features you didn’t add in the V1. Thank you!
Thanks, Dave. My first question would be what drove the high confidence in the first place and are these signals still as strong? Also, what are the overarching strategic directions and goals for v1+? Still the same? Are you going after the same users? I talked more about structuring evidence strength and prioritization in this post: www.linkedin.com/posts/herbigt_productdiscovery-outcomes-productteams-activity-6948127234008203264-Wuqa I hope that's helpful
Great question, Josh. You can probably get the best overview from Teresa Torres‘ recent book or Marty Cagan‘s Inspired (2nd edition). However, I am also a fan of enabling teams to go deeper through the content provided by specialists. That‘s why I repeatedly recomment these three books for specific parts and disciplines of Discovery: Erik Hall - Just enough Research David Bland - Testing Business IdeS Tomer Sharon - Validating Product Ideas
Great question! Here are two resources on this topic (which is more complex than a YT comment allows for): herbig.activehosted.com/index.php?action=social&c=521&m=496 herbig.co/okrs-product-management/#okrs-product-discovery
![[안방1열 직캠4K] 베이비몬스터 치키타 'DRIP' (BABYMONSTER CHIQUITA FanCam) @SBS Inkigayo 241110](http://i.ytimg.com/vi/tnlxo79cAqY/mqdefault.jpg)
Tim is a great coach I really enjoy his videos.
Awe, thanks so much, Dave. That's amazing to hear!
Super useful video, thanks Tim!
Thanks a lot for the feedback, Jana. That's great to hear!
Thank you Tim. These videos are very helpful.
By far the best guide I have seen on this subject, great job Tim!
Thanks so much, Kamil. That's amazing to hear!
Great video, although this was not what I was looking for.
You should have probably named the video as "how to plan a product discovery schedule".
The question I was trying to answer was in the beginners space "how to do product discovery".
Thank you anyway, your recommendations can help anyone planning a project that involves different stakeholders.
That‘s a great point, Vinicius! I will work on a follow-up video for that specific question soon.
Yes please do change the title as I felt it was misleading.
Very informative and helpful.
Thanks, Priyesh. That's great to hear!
Great video. thanks you for all this stuff and time taking to produce it.
Thanks, Leandre. Happy to hear it resonates!
Hi Tim, thanks for the video. What about Creation, Validation and Refinement ? They do not appear in the schedule.
This is gem.
Thanks a lot for the feedback, Meet!
What a great video for new product manager like me!
That‘s awesome to hear, Daffa!
thank you for such a great explanation.
Thanks, Anshu. That's great to hear!
Thank you Tim!
Thank you for watching, Allan!
Well done Tim! Thanks for this awesome content on product discovery.
Thanks so much, Yurii!
Loved it.. Thanks man!
That's great to hear, Nikhil. Thanks for your feedback.
Very useful Tim
Glad you think so, Magnum!
Really good content Tim
Thanks a lot, Venkat. That‘s great to hear!
Awesome! It help me a lot, thanks @Tim Herbig!
That's amazing to hear, Leo. Thanks for the feedback!
Great stuff...
Thanks for the feedback, Solomon!
Good sessions...Thank you . What books would you recommend for me please. To keep on learning
Thanks so much! Here are some of my all-time favorites (beyond the usual suspects):
*Validating Product Ideas Through Lean User Research by Tomer Sharon*
What I love most about this book is its insane focus on practicality. It doesn't bother you with flashy introductions or stories but gets right at it. In addition, you can use it as a catalog. Skimming it for whatever you need at any given time.
It's also organizing techniques around questions (i.e., "What do users need?") to help you select what framework to apply when. The book also sticks to the basics without re-inventing the wheel.
*Radical Candor by Kim S. Scott*
Probably the most transformative book of my career in regards to soft skills. It helped break with traditional limiting beliefs (like the "shit sandwich) and how to balance giving it straight to people and not being a jerk.
As someone who was sometimes a bit too focused on harmony, this book helped me approach hard(er) conversations with more confidence and to embrace those to create clarity.
*Just Enough Research by Erika Hall*
I love diving into writing from domain experts that operate within the broader craft of Product Management. As a User Researcher, Erika Hall is focused on this particular craft with high-quality standards, without making it sound only she could to great research. This book is complementary to the work of Tomer Sharon (see the first recommendation) as a deeper layer of research activities. It also stays away from adding fluff through artificially created frameworks and buzzwords and instead focused on the necessary basics and categories like differentiating Competitive Research from Evaluative Research, etc.
*Crossing the Chasm by Geoffrey A. Moore*
Recently, I've seen some discussion around how startups or solutions are driving a "wedge" into a market to gain adoption. I think this is similar to the concept of the chasm in this book and it's such an excellent reminder for product companies to think strategically about the adoption of a new feature or entire product. The chasm refers to the 'handover' process between user groups along the lifecycle Disruptive and innovative products don't cross the chasm organically. They require smart efforts to cross the chasm in order to avoid remaining stuck in an earlier but maybe smaller customer segment.
Woah Tim, Thank you for this comprehensive response.. I would definitely be purchasing this books especially the soft skill, am a new Business Analyst, i did the course during the lockdown... And i just got a role but am definitely being challenged in terms of the soft skills..
Thank you for your recommendations
Great work here! Love it.
Thanks so much, Kakau!
Hey Tim,
Thanks for putting out this great content. I have been leaning on it lately to get a Discovery process going and it has helped me shape my thoughts on how to tackle the situation. I really appreciate it, keep up the great work!
Thank you for this piece of valuable content Tim👍. Do keep it up Sir.
Thanks so much, Nworah. That's awesome to hear!
@@herbigt You're very much welcome Tim!
If you don't mind, I'd like to create the subtitles for one other video you have on your channel at no cost! I see you have 3 more. What do you think?
Thanks Tim... great presentation. Do you know of a tool or a template that people can use to ensure that everyone is clear on the discovery process - (I mean get a buy-in on the discovery process) and can follow along as a way to ensure ppl don't keep jumping into the solution from the start.
Such a great question, Syed. I have seen lots of success with teams that create an explicit understanding around the problem space using alignment frameworks like the Mission Briefing: herbig.co/product-discovery/#mission-briefing
But, as with any tool, it‘s about how you use it. Even the best framework can be misused by solely focusing on features, cramming all pet projects in there, or never revisiting it again. Make sure to keep this in mind.
Awesome content, Tim. Thank you for that!
Thanks, Marcelo. Feedback like this keeps me going!
Nice!
Thanks so much, Caio!
I have a 1 week Product Discovery and definition deadline lol, Only two days left, wish me luck
Hey Tim! Thank you for a such great content in this video. I would say this is on of the best explanation of the Prodcut Discovery process. I have few questions for you. What do you think about Double Dimaond approach from Design Thinking? Is it good enough to be used for Product Discovery?
Hey Ruslan, thanks for the question. I believe that the general act of diverging and converging is very useful for Discovery as a whole and the individual activities in it. Like co-creating a research interview guide or collaborative ideation sessions after understanding the problem space. But, in general, I wouldn’t be too rigid about the order of your activities and recommend to adapt to new insights. Your progress should be more important than the process.
Please provide more examples on how actually discovery process happening
Great question, Oleksandr. Since I'm a firm believer in individual better practices, rather than over-generalized examples, I typically don't talk about specific scenarios outside of my course student community calls.
Tim, this explanation of the process is excellent. I have a question about post product launch and the kind of activities you feel are appropriate at that point, and the discovery process you might utilize for a V2 of a launched product where there are “high confidence” features you didn’t add in the V1. Thank you!
Thanks, Dave. My first question would be what drove the high confidence in the first place and are these signals still as strong? Also, what are the overarching strategic directions and goals for v1+? Still the same? Are you going after the same users? I talked more about structuring evidence strength and prioritization in this post: www.linkedin.com/posts/herbigt_productdiscovery-outcomes-productteams-activity-6948127234008203264-Wuqa
I hope that's helpful
Love it!
Thanks, Eldar. I appreciate the feedback!
Animal. Parabéns e muito obrigado. Continue assim!
Thanks, Andrew
Can you recommend any decent books on discovery?
Great question, Josh. You can probably get the best overview from Teresa Torres‘ recent book or Marty Cagan‘s Inspired (2nd edition). However, I am also a fan of enabling teams to go deeper through the content provided by specialists. That‘s why I repeatedly recomment these three books for specific parts and disciplines of Discovery:
Erik Hall - Just enough Research
David Bland - Testing Business IdeS
Tomer Sharon - Validating Product Ideas
How can I set a discovery OKR?
Great question! Here are two resources on this topic (which is more complex than a YT comment allows for):
herbig.activehosted.com/index.php?action=social&c=521&m=496
herbig.co/okrs-product-management/#okrs-product-discovery
Thank you!
You‘re welcome!
Discovery chickens
Useless. You spoke a lot but said nothing useful
Sorry to hear that, Paul. Maybe future videos can provide more tangible value for you.