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. People Skills
  2. Building Relationships

Communicating Progress

Communicating progress involves keeping your team, stakeholders, and leadership informed about the product's development progress, including achievements, issues, and roadblocks. This is crucial for maintaining alignment, managing expectations, and fostering a culture of transparency.

Example

Consider a Product Manager at an audio book company like Audible. They are overseeing the development of a new book recommendation feature. To communicate progress, they might use a combination of different methods.

For instance, they could use sprint reviews with the development team to discuss completed tasks, ongoing work, and any issues encountered. They might send out weekly email updates to the broader organization, highlighting key achievements and discussing any challenges. They could also hold regular stakeholder meetings to provide more detailed updates, celebrate wins, and discuss any roadblocks or changes in the plan. This multi-channel approach ensures that everyone involved is kept informed about the product's progress.

Pain Points

Ensuring regular and effective communication can be time-consuming. It's also important to tailor your communication to different audiences and manage the potential impact of bad news. All Product Managers will face challenges when there are delays in the development process or when they need to communicate bad news to the broader company.

Practical Exercise

Reflect on a project or product you're familiar with. How would you communicate progress to your team, stakeholders, and leadership? What communication strategies would you use? What potential challenges might you face and how would you handle them?

Related Research Topics

  • Reporting techniques [ Google | Perplexity ]

  • Stakeholder management [ Google | Perplexity ]

  • Agile ceremonies [ Google | Perplexity ]

  • Communication strategies in project management. [ Google | Perplexity ]

PreviousManaging ExpectationsNextLeadership

Last updated 2 months ago