I've seen over 15 product thinking videos, mock interviews and read loads of blogs. This video by far has given me the most fascinating insight into product management, Thanks a lot for posting this.
I loved this talk a lot , it made a lot of sense to me truly!! Thank you so much for explaining it in the simplest terms , makes it easier for newbies to really get a hang of what Problem Thinking and solving really means!!✨🔥
I had a problem on which i was working and was googling problem solving for PMs, luckily got your video. Super helpful !!! and in simple words !! Loved it.
Thank you for the worthy video's.I always admire the topics you pick and the ease in your explanation .And I am really glad that you being one of the best product thinker , are in opinion that it's not the bestest way that during interview PM candidate has to think on spot and based on that one get decided for next .I thought only I am the one who thinks this is unfair .
I completely agree. Interview is a contrived setting, and that's why I like written assignments to candidates allowing them to showcase their writing, research and clarity of thought as we spend time chatting about what they came up with
Hi Anushumani, Thank you for all the content you are putting out for people like us who are aspiring to build meaningful products. I have been following you from your Practo days and have learnt a lot from you. Thank you .
Hi Anshumani, great content. Can't believe we get this for free from one of the top product leaders in India! I've been in product for only 1 year and this has been one of the harder things to learn and even harder to actively apply, especially because in your day job things come at you like Tetris and a lot of time you get so caught up in placing the boxes that you become blind to the easy wins. Have you already made or could you plan a video around this too? Just how to handle the day job, the best processes to stay stoic in your responsibilities so as to do justice to what a PM is brought on to do?
Awesome insights! Can you share some books/blogs for the folks who are beginners and are interested in switching to Product Management. Thanks and keep up the good work.
Thanks for the great video! I really like the meaningful content you put together. Great work and great learning experience. Regarding the problem solving and product thinking, I also often get asked this question in interviews! Would love to explore the part you mentioned about Strategy, Tactics and Execution. Any books or blogs you suggest to get more acquainted with this?
Hi Rudra, You mentioned that early on in careers as PMs (or even in Engg for that matter), we usually deal with the execution part and it is indeed true. And as one is expecting to grow in the role, they'll be expected to be tactician and strategists, My question is since execution is the start point in our careers, wouldn't a huge factor in our careers early on would be what we have executed and for whom? And our next set of opportunities would only be limited by the insights we had drawn during the execution?
Who you've executed for and how well you executed will both play a big part in your next set of opportunities. You are absolutely right. This is why you need to learn outside of work as well. If you are only learning at the job then your learning set is limited. Build broader and deeper insights from everywhere around you.
Heyy Anshumani, your content is very knowledgeable, can you share your knowledge regarding 'how can an engineering student get into Product Management role right after undergrad'.
These are very useful, thank you for sharing your learnings. I have one request. Could you please make one video on how the user segmentation should be done?
Thanks for another amazing playbook, Anshumani! Question: How do we figure how much time is simply too much time to spend in a problem space (to avoid going down the rabbit hole / overcomplicating for no reason)? or is that what we should be doing?
Depends on how much time it takes to answer the questions - why should we solve this problem and why would users care if we did solve it? At a feature level, this should not take more than a week or two. For new products or new product verticals this could take longer. But this is not a hard and fast rule.
Why don't we start with Why. Is it because Why needs deep probing, getting into the Why space would need us to be flexible & clear of all the biases of our mind, Is it because it forces us out of the comfort zones of our mind & requires us to dwell deeper into the real world complexities/equations of the problem itself - meeting large number of people /covering a sizeable potential market space, which faces a particular problem, questioning them to dig out the actual pain points, empathizing with their problem, putting ourselves in their shoes, it will require us to be grounded & humble to understand a problem in its entirerity & zeroing in on one priority area to create a solution,.
watching 1st video from this channel. I have decided that I will binge watch all the videos from this channel
I've seen over 15 product thinking videos, mock interviews and read loads of blogs. This video by far has given me the most fascinating insight into product management, Thanks a lot for posting this.
Glad it was helpful!
Simple & Effective...
I loved this talk a lot , it made a lot of sense to me truly!! Thank you so much for explaining it in the simplest terms , makes it easier for newbies to really get a hang of what Problem Thinking and solving really means!!✨🔥
My favourite Playbook yet. Thanks!
Loved it 😊
I had a problem on which i was working and was googling problem solving for PMs, luckily got your video. Super helpful !!! and in simple words !! Loved it.
Glad it helped!
thanks Anshumani. Great quality of content.
Loving this entire PM series! Trying to make the transition and these are really helpful
Thank you for the worthy video's.I always admire the topics you pick and the ease in your explanation .And I am really glad that you being one of the best product thinker , are in opinion that it's not the bestest way that during interview PM candidate has to think on spot and based on that one get decided for next .I thought only I am the one who thinks this is unfair .
I completely agree. Interview is a contrived setting, and that's why I like written assignments to candidates allowing them to showcase their writing, research and clarity of thought as we spend time chatting about what they came up with
Hi Anushumani, Thank you for all the content you are putting out for people like us who are aspiring to build meaningful products. I have been following you from your Practo days and have learnt a lot from you. Thank you .
This means a lot. Thank you!
Very rare I subscribe after one video but this was so perfect
This is an absolute gem of a talk. So lucidly explained and so enlightening. 2thumbs up👍👍
Hey loved the video and about to implement to boost my career.
Hey bro, I have recently gotten into product domain. This was helpful.
Glad it was helpful!
Thanks. Quite helpful!
Hi Anshumani, great content. Can't believe we get this for free from one of the top product leaders in India!
I've been in product for only 1 year and this has been one of the harder things to learn and even harder to actively apply, especially because in your day job things come at you like Tetris and a lot of time you get so caught up in placing the boxes that you become blind to the easy wins.
Have you already made or could you plan a video around this too? Just how to handle the day job, the best processes to stay stoic in your responsibilities so as to do justice to what a PM is brought on to do?
Great suggestion - will put together a video on how to handle the day job, constantly learn and improve and stay stoic.
Awesome insights! Can you share some books/blogs for the folks who are beginners and are interested in switching to Product Management. Thanks and keep up the good work.
Loved the Mapping of Why - Strategy , how - tactics , What - execution . Love your videos .. What tools you use
Glad you like them! Using Loom for shooting the videos.
Thanks for the great video! I really like the meaningful content you put together. Great work and great learning experience.
Regarding the problem solving and product thinking, I also often get asked this question in interviews!
Would love to explore the part you mentioned about Strategy, Tactics and Execution. Any books or blogs you suggest to get more acquainted with this?
Read Simon Sinek's "Start With Why"
@@playbooksbyanshumaniruddra5895 Thank you!! Will check it out.
Hi Rudra,
You mentioned that early on in careers as PMs (or even in Engg for that matter), we usually deal with the execution part and it is indeed true. And as one is expecting to grow in the role, they'll be expected to be tactician and strategists, My question is since execution is the start point in our careers, wouldn't a huge factor in our careers early on would be what we have executed and for whom? And our next set of opportunities would only be limited by the insights we had drawn during the execution?
Who you've executed for and how well you executed will both play a big part in your next set of opportunities. You are absolutely right. This is why you need to learn outside of work as well. If you are only learning at the job then your learning set is limited. Build broader and deeper insights from everywhere around you.
Heyy Anshumani, your content is very knowledgeable, can you share your knowledge regarding 'how can an engineering student get into Product Management role right after undergrad'.
This topic probably deserves a series of videos.
Hi anhsumani, what in your opinion is the key distinction between problem solving and product thinking?
I think they are intersecting sets. Not all problem solving has to do with UX or business objectives - but product thinking does.
These are very useful, thank you for sharing your learnings.
I have one request. Could you please make one video on how the user segmentation should be done?
Great suggestion!
Thanks for another amazing playbook, Anshumani!
Question: How do we figure how much time is simply too much time to spend in a problem space (to avoid going down the rabbit hole / overcomplicating for no reason)? or is that what we should be doing?
Depends on how much time it takes to answer the questions - why should we solve this problem and why would users care if we did solve it?
At a feature level, this should not take more than a week or two. For new products or new product verticals this could take longer. But this is not a hard and fast rule.
Makes complete sense, thanks again :)
Why don't we start with Why.
Is it because Why needs deep probing, getting into the Why space would need us to be flexible & clear of all the biases of our mind,
Is it because it forces us out of the comfort zones of our mind & requires us to dwell deeper into the real world complexities/equations of the problem itself - meeting large number of people /covering a sizeable potential market space, which faces a particular problem, questioning them to dig out the actual pain points, empathizing with their problem, putting ourselves in their shoes, it will require us to be grounded & humble to understand a problem in its entirerity & zeroing in on one priority area to create a solution,.