This was an incredibly informative interview with Mr. Kaba. So many jewels were dropped! I will download the books he recommended, but those frameworks were gold! I will be subscribing to your channel..keep interviews like these coming!
Thank you, Lenny! I’m sure I am not the only one, who saved this episode in “favourites”and will watch it again and again. Special thanks for the summaries that you provide together with videos!
"Understand, Identify, and Execute" - three simple words that completely transformed my perspective on Product Management. I had fallen into the trap of "Identify, Justify, and Execute," but this podcast helped me recognize common pitfalls and strike a better balance. As always, thank you, Lenny, for yet another amazing podcast!
i watched almost every videos of yours ,it's worth time spending on youtube , your video reach is little low but it has immense amount of knowledge and wisdom .keep it up....
Awesome video Lenny! Could you please make a video about requirement gathering? (Or if there are any good resources you recommend?) What sort of questions you ask your stakeholder when they request for a feature? And how do you say no to requests that might be un-impactful?
Discovery can be a form of understand work and is usually filled with many work streams. For example, if your current product stalls and your team has tried to optimize it with little success, there could be discovery work to (for example): - run surveys and hold in-person customer conversations to identify the biggest pain points not being served - define and prioritize the jobs to be done based on the customer conversations - brainstorm what product solutions you could build based on customer and problem hypotheses - create med-low fidelity mocks of 1-2 ideas and get customer feedback via UXR - building out the case for roadmap investment and building out the MVP Hope this helps!
This was an incredibly informative interview with Mr. Kaba. So many jewels were dropped! I will download the books he recommended, but those frameworks were gold! I will be subscribing to your channel..keep interviews like these coming!
This episode is insanely insightful. It made everything that has happened in the past clear to me.
I generally love all your guest and interviews, but this has been the best one yet. Thanks Lenny!
Thank you, Lenny! I’m sure I am not the only one, who saved this episode in “favourites”and will watch it again and again.
Special thanks for the summaries that you provide together with videos!
Great info, Bangaly! I will be listening to this again and again as a resource. Thank you.
Awesome podcast, Bangaly is really insightful!
"Understand, Identify, and Execute" - three simple words that completely transformed my perspective on Product Management. I had fallen into the trap of "Identify, Justify, and Execute," but this podcast helped me recognize common pitfalls and strike a better balance. As always, thank you, Lenny, for yet another amazing podcast!
One of the best interviews Lenny!!! I don´t know which framework I should start implementing first, all are amazing.
Watching parts of it for the fourth time. Love it. Thanks Lenny.
Loved all the useful action packed convo.
i watched almost every videos of yours ,it's worth time spending on youtube , your video reach is little low but it has immense amount of knowledge and wisdom .keep it up....
Great podcast. Thank you, Lenny.
Awesome video Lenny!
Could you please make a video about requirement gathering? (Or if there are any good resources you recommend?)
What sort of questions you ask your stakeholder when they request for a feature? And how do you say no to requests that might be un-impactful?
Insightful
What's the difference between "understand work" and "discovery"? Is it the same thing?
Discovery can be a form of understand work and is usually filled with many work streams. For example, if your current product stalls and your team has tried to optimize it with little success, there could be discovery work to (for example):
- run surveys and hold in-person customer conversations to identify the biggest pain points not being served
- define and prioritize the jobs to be done based on the customer conversations
- brainstorm what product solutions you could build based on customer and problem hypotheses
- create med-low fidelity mocks of 1-2 ideas and get customer feedback via UXR
- building out the case for roadmap investment and building out the MVP
Hope this helps!
I loved this interview, where can I find the blog post by Bangaly?
Here you go www.reforge.com/blog/how-to-make-career-decisions
This was so insightful! Thank you Lenny !