Find this guide helpful?
Consider donating
🐼
Product Manager's Guidebook
GithubAuthorDonateContribute
  • Guidebook
    • Welcome
    • Contribute
    • Donate
  • Prelude
    • A Note From The Author
    • How To Use This Guide
  • Introduction
    • Overview
    • What is a Product Manager?
      • Roles and Responsibilities of a Product Manager
      • The Product Mindset
      • Understanding the Product Management Lifecycle
      • Different Types of Product Managers
    • Product Team Structures
      • Stakeholders, Leadership, and the Company
      • Cross-Functional Product Team
      • Differences between Project, Program, and Product Management
  • People Skills
    • Overview
    • Communication
      • Knowing Your Audience
      • Elements of Persuasion and Motivation
      • The Art of Storytelling
      • Effective Meeting Management
      • Delivering Presentations and Demos
    • Building Relationships
      • Collaboration Cadence and Tools
      • Team Agreements and Purpose
      • Understanding Business Problems
      • Managing Expectations
      • Communicating Progress
    • Leadership
      • Cross-Functional Leadership
      • Applied Motivation and Getting Buy-In
      • Giving and Receiving Feedback
      • Aligning Product Mission, Vision, and Strategy
      • Sharing Impact and Outcomes
  • Process Skills
    • Overview
    • Strategy
      • Objective Setting
      • Prioritization
      • Roadmapping
    • Discovery
      • Problem Research and Definition
      • Customer Discovery and Research
      • Solution Design and Validation
    • Development
      • Writing and Using Product Requirements
      • Concepts through Designing
      • Working with Designers
      • Development Execution and Methodologies
      • Working with Engineers
      • Scoping and Writing User Stories
      • Technical Debt Management
    • Delivery
      • Roll-out and Release Management
      • Assessing Assumptions, Risk, and Issues
      • Measuring Product Launch Success
      • Marketing and Communications
      • User Activation
    • Optimization
      • Iterative Development and Learning
      • Streamlining Processes and Experiences
  • Knowledge Skills
    • Overview
    • Understanding the Customer
      • Customer Segmentation and Targeting
      • User Research Methods
      • Understanding Customer Pain Points
      • User Personas Development
      • User Behavior and Psychology
      • Acquiring and Retaining Customers
    • Data-Driven Decisions
      • The Role of Data in Product
      • Data Analysis and Interpretation
      • Identifying and Understanding Assumptions
      • Formulating Your Hypotheses
      • Selecting a Hypothesis for Testing
      • Navigating Signal Metrics to Define KPIs for Hypothesis Testing
      • Testing Your Hypothesis
      • Upholding Data Privacy and Ethics
    • Domain Knowledge
      • Competitive Analysis and Industry
      • Achieving Product-Market Fit
      • Technology and Innovation
      • Aligning with the Company
    • Business Understanding
      • Organizational Values, Objectives, and Priorities
      • Long-Term Planning
      • Business Model Fit
      • Monetization Strategy
Powered by GitBook

Created by Mark Progano • Free & Open Source • Visit the Contribute Page to Help

On this page
  • Example
  • Pain Points
  • Practical Exercise
  • Related Research Topics
Edit on GitHub
  1. Process Skills
  2. Strategy

Objective Setting

PreviousStrategyNextPrioritization

Last updated 1 month ago

Objective setting involves defining clear, measurable, and time-bound goals that align with the product vision and business strategy. These objectives guide decision-making, prioritize initiatives, and motivate the team. They are often set at multiple levels, including company-wide objectives, product-specific objectives, and team or individual objectives. It’s common for the company to set these goals on a regular basis, such as quarterly.

Example

Imagine you’re a Product Manager at a ride-sharing company, like Lyft, and it’s the end of June (Q2) which marks the time to update your product’s quarterly objectives. The previous quarter saw a lack of growth in daily riders and there’s some fear that it could continue to trend downwards. As a result, the leadership team has asked everyone at the company to focus on increasing the number of new rides and improving user retention. More specifically, the company wants to increase the number of unique rides by 10% over the next 3 months.

As the PM who is responsible for the Driver mobile app experience, you start to dig through old notes, usage data, and talk with key members of your team to brainstorm objectives. You decide to use the Objective Key Results (OKR) framework, and you outline your top objectives and the key results you expect from each.

Your engineering manager rehashes a previously explored concept of an enhanced navigation system, which would make rides faster and more enjoyable for the passenger, helping you write your first objective “Increase riders satisfaction by optimizing routes for drop-off, turns, and travel-time”. You hypothesize that if you update the earnings screen for drivers that it will incentivize drivers to be more responsive with rides, which would increase ridership. You then write a matching objective. Your boss reminds you of an in-app chat feature enabling users and drivers to better communicate, especially at the time of pick up, which you write your third objective for.

After additional concepts are considered, you land on these three as the most impactful towards increasing ridership and start building out the key results that would come from each of these. You start with the enhanced navigation system feature and you think through the things you hope to achieve. You then outline these three key results: (1) increase time in app, since drivers won’t be switching to other navigation apps, (2) decrease in complaints from riders regarding delays, and (3) increase in the quality of the drop-off locations of riders. You repeat this exercise with each of the objectives and share your team’s OKRs with your manager for input and sign-off.

Your manager is happy with the OKRs as it provides a clear direction for prioritizing features and initiatives that can help achieve this objective.

Pain Points

Setting effective objectives can be challenging. It requires a deep understanding of the business strategy, market dynamics, and user needs. Objectives also need to be realistic and achievable, yet ambitious enough to drive progress and improvement.

Practical Exercise

Reflect on your product or a product you use regularly. What could be a potential objective for this product? How does this objective align with the product's mission and vision? How would you measure progress towards this objective?

Related Research Topics

  • OKRs (Objectives and Key Results) [ | ]

  • SMART goals (Specific [ | ]

  • Measurable [ | ]

  • Achievable [ | ]

  • Relevant [ | ]

  • Time-bound) [ | ]

  • KPIs (Key Performance Indicators) [ | ]

  • Goal setting theory [ | ]

  • Aligning product and business objectives. [ | ]

Google
Perplexity
Google
Perplexity
Google
Perplexity
Google
Perplexity
Google
Perplexity
Google
Perplexity
Google
Perplexity
Google
Perplexity
Google
Perplexity