👋 Hi friend! If you need any help with: - Interview Prep - Resume reviews - Steps to break into Product Management - or simply someone to chat with... I'm here for you: bio.link/pmdiego
Great stuff! But my understanding is that the objectives themselves are qualitative, the quantitative aspect is addressed by the Key Results. Key Results provide the specific, measurable targets that help you gauge whether the objective has been achieved. This separation between qualitative objectives and quantitative key results allows for a balance between clarity of purpose and measurable outcomes.
Thanks for sharing, Diego! Like you already stated - objective of Duolingo was vague.. so - 1. How fruitful could be such non-concrete objective in critical situations like here.. which needed product (feature) recovery from dead? Or it was just an example here? 2. What would determine "best product" anyway? It is extremely subjective, would stakeholders even fund for such objectives in real life scenarios? So.. is being vague allowed in some cases? :)
Great question! Duolingo at the time probably had more objectives besides this one. Since in this case they wanted to "take a step back" and understand where their product is and whether Stories should continue (probably), their vague objective allowed them to have a clear goal in mind: "Let's understand how to make this product the best possible" or, in other words... let's try to improve it. When you look at the Key Results, they are about: 1. Doing User Research (interview X users) 2. Produce a list of pain-points ranked in high-medium-low (to know the priorities) 3. and a document with the results (I believe this was just a milestone). In general Objectives should be as clear as possible, same with KRs... and echoing what Walsh mentioned “It’s important for people to understand that OKRs should be more of a guidepost, rather than a roadmap”... Try to make your objectives and key results as clear as possible! but treat OKRs as a signpost on how to move forward, not as a strict rule. This article also explains more the Duolingo case: www.whatmatters.com/articles/duolingo-okrs-product-development
Nice Video Diego................did check your playlists but i didn't found any Analytical videos....Could you please make a video on how to answer Analytical question!!!!!!!!!!!!
It seems like some of these key results are just more objectives? like "understand their top pain points." I thought Key Results had some sort of metric involved? Am confused..
Hi Diego, is it possible to break into PM from Customer Success? I was told to get a job at a top tier company in CS and network to product. But I am tired of Customer Success and want to go straight into Product Management.
Great question! There are a few options you can take: - Yes, transfer to CS to a company you'd like to work for... and then network your way into PM. This is probably an "easy" move since you already have the CS job - You can also network internally & shadow PMs at your own company if you have that option - You can land a job in an adjacent Product role at another company, for example Product Marketing or Business Ops... and then jump into PM - You can create your own side project to share that you can be a PM and show transferrable skills: pmdiego.substack.com/p/-building-side-projects-without-code?s=w - You can find startups and network with people on LinkedIn to volunteer your time as a PM / Or find non-profits as well to do this - finally, you can network exhaustively and have an amazing story of HOW all your skills transfer directly into Product (this is prob. a long long process and I recommend trying the other approaches first). Check out the Notion guide that I have here, it can help you plan a road on how to become a PM and let me know if you have any questions! bio.link/pmdiego
Absolutely love your story-telling skills Diego! Moving from the basics of OKRs (down to the origins of the framework) to an actual case study of Duolingo, you make it extremely easy for even a novice in product management to catch up fast on the usage of OKRs. Keep up the awesome work!
are objectives quantifiable? my knowledge is that , objectives are simple quick summaries , and key results should have numbers example : objective - our customers are the happiest they have even been kR - increase nps from 30 to 50
Hello Diego. Thanks for this vedio on OKR. Just one basic query. Shouldn't the Key Results be measurable? Mean they should always be quantitative? For Dulingo, they had KR's which were more of qualitative with out any numbers to measure. Thanks for your time
Great question! Duolingo’s KRs (for the objective I shared) 2 out of 3 where quantitative: - talk to X users (user research and a specific # of users in mind) - understand their top pain-points (they don’t share specific details of numbers, but they probably had a more specific number or way to identify high, medium and low priority and identify X top pain points) - product a document analyzing user’s pain points. This is def not quant lol! But certainly it was used as a milestone. I liked that the PM mentioned: “It’s important for people to understand that OKRs should be more of a guidepost, rather than a roadmap” And we can’t say that it didn’t work for them! They turned around the feature. So… my personal takeaway is that: KRs should be measurable (quant), but if they are not, as long as they help you reach your goal: do it!
Great video Diego. I feel like you're burying the coolest part of this video and saving it to the end. The coolest part imo is how the Duolingo PM 4x'd the users by effectively using OKRs to understand the user experience and pain points. Looking forward to more content!
![Cody Johnson - I'm Gonna Love You (with Carrie Underwood) [Official Music Video]](http://i.ytimg.com/vi/yy9PuYMU29g/mqdefault.jpg)
👋 Hi friend!
If you need any help with:
- Interview Prep
- Resume reviews
- Steps to break into Product Management
- or simply someone to chat with... I'm here for you:
bio.link/pmdiego
Great stuff! But my understanding is that the objectives themselves are qualitative, the quantitative aspect is addressed by the Key Results. Key Results provide the specific, measurable targets that help you gauge whether the objective has been achieved. This separation between qualitative objectives and quantitative key results allows for a balance between clarity of purpose and measurable outcomes.
Thanks for sharing, Diego!
Like you already stated - objective of Duolingo was vague.. so -
1. How fruitful could be such non-concrete objective in critical situations like here.. which needed product (feature) recovery from dead? Or it was just an example here?
2. What would determine "best product" anyway? It is extremely subjective, would stakeholders even fund for such objectives in real life scenarios?
So.. is being vague allowed in some cases? :)
Great question! Duolingo at the time probably had more objectives besides this one. Since in this case they wanted to "take a step back" and understand where their product is and whether Stories should continue (probably), their vague objective allowed them to have a clear goal in mind: "Let's understand how to make this product the best possible" or, in other words... let's try to improve it.
When you look at the Key Results, they are about:
1. Doing User Research (interview X users)
2. Produce a list of pain-points ranked in high-medium-low (to know the priorities)
3. and a document with the results (I believe this was just a milestone).
In general Objectives should be as clear as possible, same with KRs... and echoing what Walsh mentioned “It’s important for people to understand that OKRs should be more of a guidepost, rather than a roadmap”... Try to make your objectives and key results as clear as possible! but treat OKRs as a signpost on how to move forward, not as a strict rule.
This article also explains more the Duolingo case: www.whatmatters.com/articles/duolingo-okrs-product-development
Nice Video Diego................did check your playlists but i didn't found any Analytical videos....Could you please make a video on how to answer Analytical question!!!!!!!!!!!!
Here you go 😉
How to answer Estimation Questions (Product Management Interview Tips)
ruclips.net/video/RuwXPjTbylg/видео.html
It seems like some of these key results are just more objectives? like "understand their top pain points." I thought Key Results had some sort of metric involved? Am confused..
Hi Diego, is it possible to break into PM from Customer Success? I was told to get a job at a top tier company in CS and network to product. But I am tired of Customer Success and want to go straight into Product Management.
Great question! There are a few options you can take:
- Yes, transfer to CS to a company you'd like to work for... and then network your way into PM. This is probably an "easy" move since you already have the CS job
- You can also network internally & shadow PMs at your own company if you have that option
- You can land a job in an adjacent Product role at another company, for example Product Marketing or Business Ops... and then jump into PM
- You can create your own side project to share that you can be a PM and show transferrable skills: pmdiego.substack.com/p/-building-side-projects-without-code?s=w
- You can find startups and network with people on LinkedIn to volunteer your time as a PM / Or find non-profits as well to do this
- finally, you can network exhaustively and have an amazing story of HOW all your skills transfer directly into Product (this is prob. a long long process and I recommend trying the other approaches first).
Check out the Notion guide that I have here, it can help you plan a road on how to become a PM and let me know if you have any questions!
bio.link/pmdiego
@@PMDiegoGranados Awesome. Thank you!!
Absolutely love your story-telling skills Diego! Moving from the basics of OKRs (down to the origins of the framework) to an actual case study of Duolingo, you make it extremely easy for even a novice in product management to catch up fast on the usage of OKRs.
Keep up the awesome work!
are objectives quantifiable?
my knowledge is that , objectives are simple quick summaries , and key results should have numbers
example :
objective - our customers are the happiest they have even been
kR - increase nps from 30 to 50
Hello Diego. Thanks for this vedio on OKR. Just one basic query. Shouldn't the Key Results be measurable? Mean they should always be quantitative? For Dulingo, they had KR's which were more of qualitative with out any numbers to measure. Thanks for your time
Great question! Duolingo’s KRs (for the objective I shared) 2 out of 3 where quantitative:
- talk to X users (user research and a specific # of users in mind)
- understand their top pain-points (they don’t share specific details of numbers, but they probably had a more specific number or way to identify high, medium and low priority and identify X top pain points)
- product a document analyzing user’s pain points. This is def not quant lol! But certainly it was used as a milestone.
I liked that the PM mentioned: “It’s important for people to understand that OKRs should be more of a guidepost, rather than a roadmap”
And we can’t say that it didn’t work for them! They turned around the feature.
So… my personal takeaway is that:
KRs should be measurable (quant), but if they are not, as long as they help you reach your goal: do it!
Thanks Diego
Great video Diego. I feel like you're burying the coolest part of this video and saving it to the end. The coolest part imo is how the Duolingo PM 4x'd the users by effectively using OKRs to understand the user experience and pain points. Looking forward to more content!
That is great feedback, Jonathan! And you are absolutely right! I will definitely improve how I share some of these examples. Thank you!
@@PMDiegoGranados I'm sure you will - you have good content so that's the biggest hurdle haha