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
Edit on GitHub
  1. Process Skills
  2. Strategy

Prioritization

Prioritization in product management involves deciding which product features or initiatives to focus on based on their potential impact, feasibility, and alignment with the product strategy and business objectives. This process is crucial for managing resources effectively, meeting customer needs, and driving product success.

Example

A Product Manager at a ride-sharing company, like Lyft, is considering several potential features to improve the driver app. The features include an enhanced navigation system, an in-app chat with riders, and a new earnings dashboard. To prioritize these features, the Product Manager uses the RICE scoring system (Reach, Impact, Confidence, Effort).

For the enhanced navigation system, the Product Manager estimates that it will reach all drivers (high reach), significantly improve their experience (high impact), and they have high confidence in these estimates based on driver feedback and competitive analysis. However, it will also require significant engineering resources (high effort).

The in-app chat with riders is expected to reach only a subset of drivers who frequently communicate with riders (medium reach), have a moderate impact on their experience (medium impact), and there's medium confidence in these estimates based on initial user research. The effort is relatively low as it leverages existing chat infrastructure.

The new earnings screen is expected to reach all drivers (high reach), have a high impact on their understanding of their earnings (high impact), and there's high confidence in these estimates based on driver surveys. The effort is moderate as it requires backend data work and frontend UI design.

After calculating the RICE scores for each feature, the Product Manager finds that the new earnings dashboard has the highest score, followed by the enhanced navigation system, and then the in-app chat. This helps the Product Manager make a data-driven decision to prioritize the development of the new earnings dashboard, while also providing a clear rationale to communicate to stakeholders.

Pain Points

Prioritization can be challenging due to competing priorities, limited resources (such as finances or headcount), changes in marketing conditions, and uncertainties. It's also important to revisit and adjust priorities as conditions change.

Practical Exercise

Think of a product you're familiar with. What are some potential features or initiatives? How would you prioritize them based on their potential impact, feasibility, and alignment with the product strategy and business objectives?

Related Topics to Research: Prioritization frameworks, RICE, MoSCoW, Eisenhower matrix, Kano model, Stakeholder management, Agile planning, Roadmap prioritization

PreviousObjective SettingNextRoadmapping

Last updated 1 month ago