As you can observe, the objectives serve as the guiding principles directing the focus and efforts of individuals or teams. They are clear, qualitative statements that outline what needs to be achieved.
Likewise, the key results section provides quantifiable metrics or outcomes that help evaluate success. By establishing concrete and measurable criteria, key results enable teams to track their progress.
Learn more on OKR from this video and enhance your knowledge on important product management topics.
Benefits of OKRs
The benefits of OKRs can be better understood when you ask two questions.
- What is the role of alignment in OKR?
- How can you monitor progress when using OKR?
Answering the first question, alignment ensures that individual, team, and deartmental objectives are interconnected and contribute to the overarching mission of the company. Alignment also prevents silos, as it becomes a unified effort towards the shared vision.
To answer the second question - organisations regularly monitor results. These regular reviews allow for course correction, adjustments, and realignment of strategies if necessary. Check-ins facilitate agility and responsiveness to changing circumstances. That’s how teams stay on track towards achieving their objectives.
Types of OKRs
Aspirational OKRs
Aspirational OKRs are ambitious, stretch goals or moonshots that aim high and push the boundaries of what's achievable. They might not be entirely attainable within a given timeframe but serve as a source of inspiration and motivation for teams.
These OKRs focus on significant progress, innovation, and growth. They challenge individuals or teams to strive for remarkable achievements that might seem challenging to reach.
Example
Objective: Revolutionise User Experience and Engagement
Key Results:
KR1: Develop and launch an AI-powered user interface feature that achieves a minimum of 90% positive user feedback within three months.
KR2: Increase user engagement by 50% through the introduction of gamification elements or interactive functionalities.
KR3: Achieve a Net Promoter Score (NPS) of 70+ by implementing personalised, AI-driven recommendations to enhance user satisfaction.
This aspirational OKR pushes the boundaries by aiming for groundbreaking innovations that significantly enhance user experience and engagement. Setting ambitious goals that challenge existing norms is important here.
Committed OKRs
Committed OKRs are achievable objectives. Teams are fully committed to accomplishing them within a specified timeframe. These goals are realistic and have a higher likelihood of being attained with concerted effort.
These OKRs are specific, measurable, and attainable. They outline concrete outcomes or milestones that teams can realistically achieve, focusing on successful deliverables.
Example
Objective: Launch Enhanced Feature Set for Improved Customer Satisfaction
Key Results:
KR1: Successfully deploy and operationalise five new product features within the next development cycle.
KR2: Attain a 30% increase in customer satisfaction scores (through user feedback and surveys post-feature launch).
KR3: Achieve a 20% decrease in customer-reported issues or bugs related to the newly launched features within the first month.
Learning OKRs
Learning OKRs are focused on experimentation, exploration, or acquiring new skills or knowledge. These objectives prioritise learning outcomes, insights, or discoveries rather than solely achieving a specific target.
They encourage risk-taking, innovation, and acquiring new knowledge or capabilities.
Example
Objective: Explore Emerging Technologies for Future Product Enhancement
Key Results:
KR1: Conduct comprehensive research on blockchain integration possibilities, presenting findings on potential benefits and challenges for product enhancement.
KR2: Organise workshops and training sessions on machine learning applications, generating at least three potential use cases for product improvement within the next quarter.
KR3: Collaborate with industry experts through seminars or webinars to gain insights into the latest technological advancements and their potential applications in the product roadmap.
Case Study: The Impact of OKRs in Driving Google Chrome's Success
Google Chrome's meteoric rise to dominance stands as a testament to the efficacy of Objectives and Key Results (OKRs). Let’s see how Google used it for innovation, persistence, and strategic goal-setting.
Challenge
In 2008, Sundar Pichai and his team faced the formidable task of launching Google Chrome in an already crowded market. Their objective was not merely to introduce another browser in the market, but to revolutionise the web browsing experience.
OKRs as a Strategic Tool
Sundar Pichai, then Vice President of Product Development, recognised the power of OKRs in setting ambitious yet achievable goals.
Utilising OKRs, they established clear Objectives – making the web browsing experience faster and more user-friendly – and defined specific Key Results to track their progress.
Setting Stretch Goals
The Chrome team embraced stretch goals within their OKRs, aiming for milestones that pushed beyond conventional boundaries. The ambition to reach 111 million seven-day active users became a pivotal OKR, embodying the stretch goal philosophy.
Adaptability and Persistence
Despite initial setbacks and not meeting their 2009 target of 50 million active users, the team remained undeterred. They pivoted, adapting strategies, broadening product distribution, and launching innovative marketing campaigns to increase Chrome's accessibility and appeal.
Innovation and Reinvention
The OKR framework fuelled innovation, driving the Chrome team to reinvent the business model, explore new marketing strategies, and expand the browser's reach to different operating systems, breaking the Windows-only barrier.
The Result
Through persistent effort and strategic use of OKRs, the Chrome team witnessed significant growth, surpassing their ambitious target of 111 million active users. Their adaptive approach, guided by OKRs, led Chrome to become the most popular web browser, on both mobile and desktop platforms, till today.
How to Set OKRs for Your Product Team
Product managers generally focus on the key areas of development process when setting OKRs. They could look into improving user engagement metrics, such as customer feedback scores. Or, they could improve revenue by focusing on the average revenue per user (ARPU).
Let’s look at how OKRs are set in the product scenario, right from understanding top-level objectives and finally narrowing down - a top-down approach of sorts.
Organisational Goals
Gain clarity on the company's overarching objectives, business strategies, and priorities. Identify how the product team's efforts contribute to these broader goals.
Stakeholders’ Needs
Engage with cross-functional teams, including engineering, design, marketing, and sales, to understand their needs and align product objectives with their requirements. This phase makes stakeholder management easier later.
Define Clear Objectives
Establish specific and outcome-driven Objectives that reflect the desired achievements for the product team. These objectives should be ambitious yet attainable and directly linked to product success.
Craft Measurable Key Results
Break down each Objective into measurable and quantifiable Key Results. These Key Results should be specific, time-bound, and serve as indicators of progress towards achieving the Objectives.
Prioritise Key Areas of Focus
Identify and prioritise key focus areas for the product team. This could include product improvements, user experience enhancements, feature launches, or market expansion.
Ensure Alignment and Relevance
The Objectives and Key Results must be aligned with customer needs, market trends, and the product's strategic roadmap. They should be relevant and impactful for the product's success. This step is important for customer engagement.
Balance Aspirational and Committed Goals
Include aspirational goals that encourage innovation and push boundaries, balanced with committed goals that are realistic and achievable within a defined timeframe.
Quantify Key Results with Metrics
Define metrics or KPIs for each Key Result. These metrics should be measurable and directly correlated with the progress towards achieving the desired outcomes.
Communicate and Gain Buy-in
Communicate the set OKRs across the product team and relevant stakeholders. Ensure everyone understands the Objectives, Key Results, and their role in contributing to their accomplishment.
Regularly Review and Iterate
Conduct regular check-ins and reviews to monitor progress towards Key Results. Be open to iterations or adjustments based on changing priorities, market dynamics, or new insights.
Celebrate Achievements and Learn from Failures
Acknowledge and celebrate milestones achieved along the way. Additionally, learn from any setbacks, using them as opportunities for learning and improvement.
Common Mistakes to Avoid in OKRs
Here are some common OKR mistakes you MUST avoid.
OKR Mistakes |
Description |
Overloading with Objectives |
Setting too many Objectives, leading to confusion and lack of focus among teams. |
Vague or Unrealistic Objectives |
Objectives lacking clarity, being too broad or unattainable, hindering progress. |
Neglecting Key Results' Measurability |
Key Results without measurable metrics or being too subjective, hampering progress tracking. |
Lack of Alignment with Company Goals |
Failure to align individual or team OKRs with broader organisational objectives. |
Set-and-Forget Mentality |
Not reviewing or updating OKRs regularly, resulting in stagnant or irrelevant objectives. |
Micromanaging Key Results |
Excessive control over Key Results limiting innovation and discouraging risk-taking. |
Ignoring Failures or Setbacks |
Overlooking failures without learning opportunities or adaptation. |
Lack of Communication and Transparency |
Not communicating OKRs transparently, leading to misunderstandings and lack of alignment. |
Not Celebrating Achievements |
Failure to acknowledge or celebrate milestones achieved, impacting team motivation. |
Blindly Copying OKRs |
Replicating OKRs from other organisations without context or relevance to the company's needs. |
So far on OKRs in this blog…
- OKRs align product strategies with organisational goals for enhanced focus and productivity.
- There is a balance between ambitious goals and realistic objectives in product development.
- OKRs serve as a catalyst for innovation, adaptability and continual improvement within product teams
- Regular reviews and adjustments keep teams on track, facilitating agile responses to market dynamics.
Now that you got a hang of OKRs, you may learn further how to write and refine them yourself with hands-on online courses such as OKR Certification by Measure What Matters on Coursera.
FAQs on OKRs
What is the difference between OKR and KPI?
OKR (Objectives and Key Results) and KPI (Key Performance Indicators) differ in focus and scope. OKRs are about setting strategic goals and measurable outcomes to align teams towards achieving broader objectives, fostering innovation and adaptability. On the other hand, KPIs are specific, quantifiable metrics used to track performance in particular areas, providing ongoing measurements of success against predefined targets or benchmarks within an organisation. While OKRs guide the direction and alignment of efforts, KPIs monitor and evaluate performance in specific operational aspects.
How do OKRs differ for product teams compared to other departments?
OKRs for product teams are tailored to focus on product-specific objectives and outcomes aligned with the product's success. They often revolve around improving user experience, launching new features, or enhancing product functionality. Unlike other departments that might concentrate on sales targets or operational efficiency, product teams centre OKRs around innovation, customer satisfaction, and iterative product improvements.
What strategies can product managers use to ensure effective communication of OKRs across cross-functional teams?
Product managers can employ several strategies for seamless OKR communication across diverse teams. These include conducting regular meetings to discuss and align OKRs, utilising visual aids like charts or dashboards for clarity, encouraging open dialogue for feedback, setting clear expectations through concise documentation, and fostering a culture of transparency and collaboration to ensure everyone understands their role in achieving the set objectives.
What role do learning OKRs play in product development, and how do they foster innovation within teams?
Learning OKRs in product development prioritise exploration, experimentation, and acquiring new knowledge or skills. These objectives encourage teams to take calculated risks, explore innovative ideas, and seek new approaches or technologies. By fostering a culture of curiosity and learning, these OKRs inspire innovation within teams, leading to the discovery of new solutions, enhancement of skills, and the cultivation of an environment conducive to continuous improvement and growth.
What makes OKR good?
A good OKR is clear, measurable, aligned with organisational goals, time-bound, regularly reviewed, and fosters a culture of learning and adaptability.