Both CSAT and NPS are lagging metrics, which take time (end of month etc) for a PM to read signals. A good leading metric is usage %, time spent etc with the product. Also, I would pick one pain to solve and present 3-4 solutions instead of doing a pain-solution combo.
yep exactly. North star metric should be time spent on browser, you would want this to increase over time. Segmenting should be done based on jobs to be done -> what needs are underserved on google chrome?
I have this thought in my mind, If I watch UA-cam videos on Chrome, Will you consider it as time spent on the browser or time spent on the content? how can this really be a North Star metric? I would have prioritized the fact that Chrome drains a lot of my laptop battery, heats up my laptop, and consumes a lot of RAM, this is probably faced by every user of Chrome. @@user-jp7ni5xv1r
@@user-jp7ni5xv1r Hey! I am just learning, but for power user time spent on a browser would be high anyways, so in that context does csat and nps weigh in more?
The time spent in any productive application might be a contrarian metric. In the sense that a user might spend too much unnecessary time on it while not achieving their intent. CSAT and NPS measure the satisfaction directly, rather than indirectly based on assumptions. If we were talking about entertainment or learning apps, then sure, you can assume time spent brings value to the customer with a higher degree of confidence.
Great content. Just a feedback here: Maybe you should show how much time was used thinking for list solutions and so on. That well bring to us a more realistic sense.
Interesting take on the chrome improvement question. I likely would have echoed the mission of the company first then double down on the collection of additional data aspect and display it to the user based on search relevancy. For example if I were to search for LA clippers I would show flyouts of latest game results along with merchandise and also ways to watch the next game. Counter metric here would be drop off due to too much different info types and make chrome busier than it needs to etc Structure and presentation here was very sound and easy to follow. The issue with memory consumption and getting lose with tabs are both very real and relatable
Thanks Anchal! If you didn't already, you can subscribe to our channel as we'll be releasing loads more PM mock interviews over the next weeks and months. ua-cam.com/channels/FJy5E_3XknWv42cvedoALw.html
Would have liked to hear more about how he would measure CSAT, also agree with the leading vs lagging indicators comment. On pain points, he didn’t explain why the pain point he chose to solution for is better to drive toward the selected goal. And while it’s good to reference personal experiences, it felt like he was just trying to solve his own problem vs exhibiting user empathy.
A moonshot idea would be using Google Assistant to achieve both the two features Akshat mentioned. Also, why does chrome not have a document editor and a document/webpage summariser?
Akshat is amazing and I love all his interviews. One piece of feedback is: He picked "Productivity" as pain point, but didn't explain why. It would have been nicer to hear what criteria he used to pick that pain point to focus on
Personally, I would prefer focussing on engagement. That should be the NSM. Customer experience, new features, security and other elements would feed Engagement. Also, I would prioritise 'Medium users' and not "Power users' as they are already using it to a great extent. Better to focus on Medium users who are the lower hanging fruit and also understanding why they are 'Medium users' and working on features/awareness initiatives accordingly. Again, this is my analysis
Awesome Video! I do have a question/feedback. I noticed that the user segmentation was very sparce. Chrome was only sliced in 1 type of user (Power user, light user, etc), and no other use case or user segment was mentioned. Is this on purpose? Should we keep user segments relatively light (Pun not intended).
Very good! great answer and very very good video overall, SUBSCRIBED! one point for improvment from my side: He mentioned a lot HIS point of view, and i think in those parts he should look through the eyes of the users and not only from the eyes of himself, like a true PM does. one more thing, it would be nice if you add analysis to the interview at the end with pros and cons :) can add a lot. amazing overall, 9/10.
Hi Omer, glad you liked the video :) To respond to your point about adding extra analysis at the end, sure, I'll keep that in mind for future videos. Obviously we already have the feedback sections throughout the interview but I can see that some extra analysis at the end could be helpful. In regards to your point about Akshat answering from a user perspective, I actually think he does that pretty well - he describes different various types/segments of users and evaluates what their needs might be. Anyway, thanks so much for your feedback, make sure you a few of the other the interviews on our channel!
When people come up with the pain points in these mock interviews, and they just make them up - I presume this is just to respond to the brainstorm like framework. But in reality if you were tasked with improving something like this at google, you would have a bunch of feedback to trawl through to help generate ideas and insights on where customers would like to see improvements right?
Yup apparently, tons of user and market research. I think phrasing this approach as "in real life we'll...but for the sake of this exercise we'll simplify and blah blah blah"
Great video, it's definitely pointed me in the direction that I need to improve my skills. In a real-world scenario, does your interviewer send you the question "How would you improve google Chrome?" so that you can prepare for it? Thank you!
Glad you found it helpful. No, you won't get the question in advance, certainly not in interviews for companys like Google, Meta, etc. You'll need to be ready with a method that you can apply to any question to help you structure your answer. You can learn more with our guide to design questions here: igotanoffer.com/blogs/product-manager/product-design-questions Good luck!
13:02 lol this is already implemented, how tf am I supposed to figure out a new functionality in the interview I guess all we have to do is pretend the solution doesn't exist, exaggerate the issue and gift wrap an existing solution
even the 14:20 thing is already implemented, the event planner organizer just needs to add notifs to the event, and as you accept the invite you will be pinged that hey turn on notifs for your browser which sends out a voice-note + notif 5/10/30 mins before the meeting is scheduled
I find it funny that these people were Google PMs. None of the things you mentioned is a business goal. Biz goal is ALWAYS revenue. Everything else are product objectives to achieve that. You need to make that very clear
Increasing engagement, gives better ROI for advertisers (As they get more impressions for their ads) and better ROI for advertisers means more monetization for Google which is revenue
Google is such a massive company and its already bringing in billions of dollars in profit each quarter. Unlike other *smaller* companies, there is NOT a strict focus on revenue across everything. In fact, they make so much money the litmus test of creating/building a product is worth it if it will generate MORE than half a billion dollars. Things that will only generate tens of millions to hundreds of millions, arent worth the time/energy because that amount doesnt really move the needle.
Both CSAT and NPS are lagging metrics, which take time (end of month etc) for a PM to read signals. A good leading metric is usage %, time spent etc with the product. Also, I would pick one pain to solve and present 3-4 solutions instead of doing a pain-solution combo.
yep exactly. North star metric should be time spent on browser, you would want this to increase over time.
Segmenting should be done based on jobs to be done -> what needs are underserved on google chrome?
Hey Udayan, agreed that would also have been a good approach. Thanks for the feedback
I have this thought in my mind, If I watch UA-cam videos on Chrome, Will you consider it as time spent on the browser or time spent on the content? how can this really be a North Star metric? I would have prioritized the fact that Chrome drains a lot of my laptop battery, heats up my laptop, and consumes a lot of RAM, this is probably faced by every user of Chrome. @@user-jp7ni5xv1r
@@user-jp7ni5xv1r Hey! I am just learning, but for power user time spent on a browser would be high anyways, so in that context does csat and nps weigh in more?
The time spent in any productive application might be a contrarian metric. In the sense that a user might spend too much unnecessary time on it while not achieving their intent. CSAT and NPS measure the satisfaction directly, rather than indirectly based on assumptions. If we were talking about entertainment or learning apps, then sure, you can assume time spent brings value to the customer with a higher degree of confidence.
Please have more of Akshat on here!! He’s amazing.
Request noted!
Great content. Just a feedback here: Maybe you should show how much time was used thinking for list solutions and so on. That well bring to us a more realistic sense.
I really loved the feedback snippets.
Thanks Anuj, it takes a while to edit them in so that's really nice to hear!
Interesting take on the chrome improvement question. I likely would have echoed the mission of the company first then double down on the collection of additional data aspect and display it to the user based on search relevancy. For example if I were to search for LA clippers I would show flyouts of latest game results along with merchandise and also ways to watch the next game. Counter metric here would be drop off due to too much different info types and make chrome busier than it needs to etc
Structure and presentation here was very sound and easy to follow. The issue with memory consumption and getting lose with tabs are both very real and relatable
What a great approach, I loved it! You guys are doing a fantastic job. Awaiting for more such videos.
Thanks Anchal! If you didn't already, you can subscribe to our channel as we'll be releasing loads more PM mock interviews over the next weeks and months. ua-cam.com/channels/FJy5E_3XknWv42cvedoALw.html
Would have liked to hear more about how he would measure CSAT, also agree with the leading vs lagging indicators comment.
On pain points, he didn’t explain why the pain point he chose to solution for is better to drive toward the selected goal. And while it’s good to reference personal experiences, it felt like he was just trying to solve his own problem vs exhibiting user empathy.
Awesome Mock interview !! I love your approach and thought process..
Really glad you like it, Alex! We've got plenty more in the pipeline, so make sure to subscribe if you want to see more 😃
A moonshot idea would be using Google Assistant to achieve both the two features Akshat mentioned.
Also, why does chrome not have a document editor and a document/webpage summariser?
Akshat is amazing and I love all his interviews. One piece of feedback is: He picked "Productivity" as pain point, but didn't explain why. It would have been nicer to hear what criteria he used to pick that pain point to focus on
Fair point, thanks for the feedback :)
This is a great example! One question is i know it may seem obvious, but between those two pain points why do we choose productivity to focus?
Good point, the interviewer should have got him to explain that choice (or ideally he should said why without prompting)
Personally, I would prefer focussing on engagement. That should be the NSM. Customer experience, new features, security and other elements would feed Engagement. Also, I would prioritise 'Medium users' and not "Power users' as they are already using it to a great extent. Better to focus on Medium users who are the lower hanging fruit and also understanding why they are 'Medium users' and working on features/awareness initiatives accordingly.
Again, this is my analysis
So moving aiming to move the Medium Users to the Power Users... great strategy
Awesome Video! I do have a question/feedback. I noticed that the user segmentation was very sparce. Chrome was only sliced in 1 type of user (Power user, light user, etc), and no other use case or user segment was mentioned. Is this on purpose? Should we keep user segments relatively light (Pun not intended).
Akshat could have mentioned more user segments, yes. Feel free to segment a bit more, time permitting.
Very good! great answer and very very good video overall, SUBSCRIBED! one point for improvment from my side: He mentioned a lot HIS point of view, and i think in those parts he should look through the eyes of the users and not only from the eyes of himself, like a true PM does. one more thing, it would be nice if you add analysis to the interview at the end with pros and cons :) can add a lot. amazing overall, 9/10.
Hi Omer, glad you liked the video :)
To respond to your point about adding extra analysis at the end, sure, I'll keep that in mind for future videos. Obviously we already have the feedback sections throughout the interview but I can see that some extra analysis at the end could be helpful. In regards to your point about Akshat answering from a user perspective, I actually think he does that pretty well - he describes different various types/segments of users and evaluates what their needs might be.
Anyway, thanks so much for your feedback, make sure you a few of the other the interviews on our channel!
When people come up with the pain points in these mock interviews, and they just make them up - I presume this is just to respond to the brainstorm like framework. But in reality if you were tasked with improving something like this at google, you would have a bunch of feedback to trawl through to help generate ideas and insights on where customers would like to see improvements right?
Yup apparently, tons of user and market research. I think phrasing this approach as "in real life we'll...but for the sake of this exercise we'll simplify and blah blah blah"
Great content! Loved it
Glad you enjoyed it!
Great video, it's definitely pointed me in the direction that I need to improve my skills. In a real-world scenario, does your interviewer send you the question "How would you improve google Chrome?" so that you can prepare for it? Thank you!
Glad you found it helpful. No, you won't get the question in advance, certainly not in interviews for companys like Google, Meta, etc. You'll need to be ready with a method that you can apply to any question to help you structure your answer. You can learn more with our guide to design questions here:
igotanoffer.com/blogs/product-manager/product-design-questions
Good luck!
this is excellent!
Get 1-1 coaching and land a PM job at Google, Facebook, Amazon, etc. Browse our coaches: igotanoffer.com/en/interview-coaching/role/product-manager
Why is DAU user acquisition vs engagement?
Should be an engagement metric rather than an acquisition metric.
13:02 lol this is already implemented, how tf am I supposed to figure out a new functionality in the interview
I guess all we have to do is pretend the solution doesn't exist, exaggerate the issue and gift wrap an existing solution
even the 14:20 thing is already implemented, the event planner organizer just needs to add notifs to the event, and as you accept the invite you will be pinged that hey turn on notifs for your browser which sends out a voice-note + notif 5/10/30 mins before the meeting is scheduled
I would advise that you explore the company's product as much as you can before the interview.
I find it funny that these people were Google PMs. None of the things you mentioned is a business goal. Biz goal is ALWAYS revenue. Everything else are product objectives to achieve that. You need to make that very clear
Biz goal can be to increase market share
Increasing engagement, gives better ROI for advertisers (As they get more impressions for their ads) and better ROI for advertisers means more monetization for Google which is revenue
Google is such a massive company and its already bringing in billions of dollars in profit each quarter. Unlike other *smaller* companies, there is NOT a strict focus on revenue across everything. In fact, they make so much money the litmus test of creating/building a product is worth it if it will generate MORE than half a billion dollars. Things that will only generate tens of millions to hundreds of millions, arent worth the time/energy because that amount doesnt really move the needle.
segmentation was very weak,
light, middle, heavy
This is actually one of the most common way to segment for PM interviews as it was mentioned in the book
@@eisgavajs I believe utilization does not bring insight to the segments. I know is common.
6/10