What Makes a Good Product Manager?

What Makes a Good Product Manager?

A detailed guide to product management mindset, strategic thinking, customer understanding, leadership, decision-making, and long-term product ownership.

Core idea: A good Product Manager is not simply someone who delivers features. A good Product Manager helps the organisation solve meaningful customer problems, make informed decisions, and create sustainable product value throughout the product lifecycle.

Introduction: What Separates a Good Product Manager From Someone Who Just Manages Tasks?

Product Management is often misunderstood as a role where someone writes requirements, manages Jira tickets, attends meetings, and communicates with developers.

These activities can be part of a Product Manager’s work, but they do not fully define the profession.

A Product Manager needs to understand customers, business objectives, technology, market conditions, and the trade-offs involved in making product decisions.

The real challenge is that there is rarely one perfect answer. Customers may want different things. Engineering may have technical limitations. Leadership may have revenue targets. The market may change while a product is still being developed.

A good Product Manager helps the team navigate this uncertainty while maintaining a clear focus on customer and business value.

“Product Management is not about building everything people request. It is about understanding which problems deserve to be solved, deciding how to approach them, and learning whether the solution actually creates value.”

1. Customer Empathy: Understanding the Person Behind the Problem

What does customer empathy mean?

Customer empathy means making a genuine effort to understand the customer’s situation, needs, frustrations, motivations, and context.

It does not mean agreeing with every customer request. It means understanding why the customer is asking for something before deciding how to respond.

Example: Healthcare appointment scheduling

A clinic administrator tells you:

“We need an AI feature that automatically reschedules appointments.”

Instead of immediately creating a user story, you investigate the workflow.

  • Why are appointments being rescheduled so frequently?
  • What happens when a patient cancels?
  • How are staff currently managing available time slots?
  • What problems occur with the existing system?
  • Are there different rules for different appointment types?
  • What risks could arise from incorrect automated scheduling?

You may discover that the biggest problem is not rescheduling itself. It may be that staff cannot see availability across multiple providers. Or the system may not support a reliable cancellation workflow.

What a good PM does

  • Listens without immediately jumping to a solution.
  • Asks follow-up questions.
  • Observes the customer’s real workflow.
  • Identifies repeated problems rather than isolated complaints.
  • Balances customer feedback with broader evidence.
Key lesson: Customers may describe a solution, but the Product Manager must investigate the underlying problem.

2. Strategic Thinking: Understanding the Bigger Picture

Why strategy matters

A Product Manager needs to understand how individual product decisions connect to the organisation’s broader goals.

A company may want to increase revenue, enter a new market, improve customer retention, reduce operational costs, or strengthen its competitive position.

Product strategy helps determine which opportunities the product should pursue and which opportunities should not be prioritised.

Example: An AI healthcare platform

The company wants to become a leading AI healthcare workflow platform. It has limited engineering resources and several potential opportunities:

  • AI appointment scheduling.
  • Patient communication automation.
  • Clinical reporting.
  • Billing workflow automation.
  • Analytics dashboards.

The PM should not assume that all opportunities can be pursued simultaneously.

The team needs to understand which customer segment it is serving, which problems are most important, and which opportunities align with the company’s capabilities and objectives.

Questions a strategic PM asks

  1. Who is our primary customer?
  2. What problem are we trying to solve?
  3. Why is this problem important now?
  4. What alternatives do customers have?
  5. What makes our solution valuable?
  6. What should we prioritise and what should we avoid?
  7. How will we measure progress?
Key lesson: Strategy is about making choices. A PM needs to understand not only what the team will build, but also why it is worth building.

3. Prioritisation: Learning What Not to Build

Why prioritisation is difficult

Product teams rarely have unlimited time, people, or money. Every decision to build one thing means that another opportunity may receive less attention.

A Product Manager must evaluate competing priorities and help the team focus on work that supports the product’s objectives.

Example: Three competing requests

Request Reason for consideration
New AI assistant Potential differentiation and new customer value.
Fix appointment failures Existing customers are experiencing operational problems.
New reporting dashboard Requested by several customers and internal stakeholders.

A weak approach is to choose whichever request is the loudest or most exciting.

A stronger approach is to evaluate customer impact, business importance, urgency, effort, dependencies, and risk.

Useful prioritisation questions

  • How many customers experience this problem?
  • How significant is the problem?
  • Does the opportunity support our product strategy?
  • What is the cost of not addressing it?
  • How much effort and risk are involved?
  • What other work would be delayed?
  • What evidence do we have?

Frameworks such as RICE, MoSCoW, and opportunity scoring can support prioritisation. They are decision aids, not replacements for judgement.

Important: A prioritisation framework does not automatically produce the correct answer. The quality of the inputs, assumptions, and strategic context still matters.

4. Product Discovery: Being Comfortable With Uncertainty

What is uncertainty?

Before developing a product or feature, you may not know whether customers will use it, whether the technology will work reliably, or whether the business model will be sustainable.

A good Product Manager does not pretend to know everything. Instead, they identify assumptions and find ways to test them.

Example: Building an AI tutor

An education company wants to create an AI tutor for students.

The team assumes that students will use it to receive answers to homework questions.

Before investing in a full product, the PM should explore:

  • What do students and teachers actually need?
  • How should the tutor support learning rather than simply provide answers?
  • What level of accuracy is required?
  • How will incorrect responses be identified?
  • What safeguards and age-appropriate design considerations apply?
  • How will teachers evaluate whether the tool is useful?

The team might conduct interviews, create a prototype, run usability tests, and evaluate generated responses before deciding on the next development investment.

Key lesson: Discovery is about reducing important uncertainty before committing significant resources.

5. Analytical Thinking: Turning Data Into Better Decisions

Why data matters

Product Managers need to understand what is happening in their product. Analytics can reveal patterns that are difficult to identify through individual customer conversations.

However, data does not explain everything by itself. Quantitative data and qualitative research often work best together.

Example: Low feature adoption

Your team launches an AI-generated lesson planning feature. Only 15% of active teachers use it each month.

This number is a signal, not a complete explanation.

You investigate:

  • Do teachers know the feature exists?
  • Is the onboarding process clear?
  • Are generated lessons useful and accurate?
  • Is the feature difficult to find or use?
  • Does the workflow fit teachers’ preparation routines?
  • Are there technical or account access problems?

You may discover that the feature has low adoption because teachers cannot easily edit the generated content, not because they do not need AI assistance.

Metrics a PM should understand

Metric What it helps you understand
Activation Whether new users reach an important early product experience.
Retention Whether users continue receiving value over time.
Churn How many customers stop using or cancel the product.
Conversion How users move from one defined stage to another.
Task success Whether users can complete a meaningful task effectively.
Customer satisfaction How customers perceive their experience, using an appropriate measurement method.
Key lesson: Data helps you identify what is happening. Research and analysis help you understand why it is happening.

6. Technical Understanding: Working Effectively With Engineers

Does a Product Manager need to be technical?

The level of technical expertise required depends on the role and organisation. A technical PM working on APIs, infrastructure, AI platforms, or enterprise systems may need deeper technical understanding than a PM working in another product context.

A PM does not need to personally write all the code. But understanding technology helps them collaborate with engineers and make informed product decisions.

Example: Adding an AI feature to an existing system

The business wants to introduce an AI assistant that retrieves information from internal company records.

The PM should work with engineering to understand:

  • Where the relevant data is stored.
  • How the assistant will access the data.
  • What APIs or integrations are required.
  • How permissions and access controls will work.
  • How incorrect or incomplete responses will be handled.
  • What monitoring and evaluation are needed.
  • What the cost and maintenance implications are.

In healthcare or other sensitive environments, additional privacy, security, regulatory, and safety requirements may apply.

How technical knowledge helps

  • Ask more relevant questions.
  • Understand engineering constraints.
  • Identify dependencies earlier.
  • Evaluate trade-offs between different solutions.
  • Communicate more effectively with developers.
Key lesson: Technical knowledge should help the PM make better product decisions. It should not replace customer understanding or strategic thinking.

7. Communication: Creating Clarity Across Teams

Why communication matters

Product Managers work with people who have different responsibilities, expertise, and priorities.

Engineering may focus on feasibility and reliability. Sales may focus on customer opportunities. Leadership may focus on strategic outcomes. Design may focus on usability and accessibility.

The PM needs to communicate the problem, priorities, rationale, and trade-offs clearly.

Example: A roadmap disagreement

The sales team requests a feature for a large prospective customer. Engineering estimates that it will require substantial effort. Meanwhile, existing customers are reporting problems with a core workflow.

A good PM should not dismiss sales or automatically agree to the request.

They should:

  1. Understand the business opportunity.
  2. Clarify the customer requirements.
  3. Assess the technical effort and dependencies.
  4. Compare the opportunity with existing product priorities.
  5. Discuss options and trade-offs with stakeholders.
  6. Communicate the decision and its rationale.

Good communication includes

  • Clear written requirements and decision records.
  • Concise explanations of product priorities.
  • Active listening.
  • Transparent communication about uncertainty.
  • Respectful handling of disagreement.
  • Adapting communication to different audiences.
Key lesson: Communication is not just sharing information. It is helping people understand decisions well enough to work together effectively.

8. Leadership Without Formal Authority

What does leadership mean for a PM?

Product Managers often need to influence people who do not report to them.

They may coordinate with engineering leads, designers, executives, customer success teams, and external stakeholders.

Leadership in this context means creating clarity, building trust, facilitating decisions, and helping teams work toward a shared outcome.

Example: A delayed product release

A release is delayed because an important integration has not been completed.

The PM could blame engineering for missing the deadline. However, blaming a team does not resolve the underlying issue.

A stronger response is to:

  • Understand the reason for the delay.
  • Identify the impact on customers and business priorities.
  • Explore alternative delivery options.
  • Communicate revised expectations.
  • Help the team make decisions about scope and timing.
  • Identify lessons for future planning.

This does not mean avoiding accountability. It means addressing problems constructively while maintaining responsibility for product outcomes within the PM’s scope.

Key lesson: Strong PM leadership is based on influence, clarity, collaboration, and accountability rather than simply giving instructions.

9. Decision-Making: Knowing When to Say Yes and No

Why saying no is important

Product Managers frequently receive feature requests from customers, stakeholders, and internal teams.

Saying yes to everything creates an overloaded roadmap and can make it difficult for the team to deliver meaningful outcomes.

Saying no, however, should not mean dismissing people without understanding their needs.

Example: A customer requests a custom feature

A major customer wants a specialised reporting workflow. The request would require two months of development and would only be used by that customer.

The PM should investigate:

  • What problem is the customer trying to solve?
  • Do other customers have a similar need?
  • Can the problem be solved with existing functionality?
  • Is there a reusable product opportunity?
  • What are the development and maintenance costs?
  • How does the request align with product strategy?

The possible decision could be to build a reusable capability, offer a limited workaround, defer the request, or decline it.

The decision depends on the evidence and context.

A professional way to decline: “We understand the problem you’re trying to solve. We are not prioritising this specific implementation at the moment because of current product priorities. We would like to explore whether there is a broader solution that could support your workflow and other customers as well.”

10. Ownership: Thinking Beyond Your Immediate Tasks

What does product ownership mean?

Ownership means taking responsibility for understanding problems, following through on decisions, and helping ensure that work produces the intended results.

It does not mean doing everything yourself or taking personal responsibility for every issue caused by another team.

Example: A feature has been released

The development team completes an automated appointment reminder feature.

A task-oriented approach might consider the work complete once the feature is deployed.

A product-oriented approach asks:

  • Are clinics using the feature?
  • Are reminders being sent correctly?
  • Are users experiencing difficulties?
  • Are patients receiving the intended communications?
  • Is the feature achieving its intended outcome?
  • What improvements should be considered next?

The PM collaborates with the relevant teams to investigate these questions and determine follow-up actions.

Key lesson: Product ownership extends beyond delivery. It includes understanding whether the product is creating the value it was intended to create.

11. Adaptability: Responding to Changing Customer and Market Needs

Why adaptability matters

Products operate in changing environments. Customer expectations, technologies, competitors, regulations, and business priorities can change over time.

A good PM needs to adapt while maintaining a clear understanding of the product’s purpose.

Example: An education platform introduces AI

An EdTech platform has traditionally focused on interactive learning activities. New AI-powered tools become available, and competitors begin introducing AI-assisted lesson creation.

The PM should investigate:

  • What problems are teachers trying to solve?
  • What value do competing products provide?
  • Are AI tools reliable and appropriate for the intended users?
  • What opportunities align with the product’s existing strengths?
  • What new risks and operational costs might arise?

The PM may recommend adding AI functionality, improving existing capabilities, changing the product positioning, or not pursuing a particular opportunity.

Adaptability does not mean chasing every trend. It means responding to relevant changes using evidence and strategic judgement.

12. Product Thinking: Looking at the Entire System

What is product thinking?

Product thinking means considering the relationship between customer needs, user experience, technology, business objectives, and the broader product ecosystem.

A feature can be useful in isolation but create problems elsewhere in the product.

Example: Adding more features to a SaaS platform

A SaaS company keeps adding new dashboards, settings, integrations, and automation tools.

Over time, users report that the product has become difficult to understand.

The PM should evaluate whether the new functionality is increasing customer value or creating unnecessary complexity.

  • Can the navigation be simplified?
  • Are some features rarely used?
  • Can related workflows be combined?
  • Are customers struggling to discover important functionality?
  • Is the product becoming expensive to maintain?
Key lesson: Product improvement is not always about adding more. Sometimes the best improvement is to simplify, remove, or redesign.

13. Case Study: Microsoft and the Evolution of Microsoft 365

Background

Microsoft 365 represents a broader evolution from traditional productivity software toward a subscription-based suite of connected productivity and collaboration services.

The product ecosystem includes applications such as Word, Excel, PowerPoint, Outlook, Teams, and other services. Microsoft’s development of cloud-based offerings and subscription services illustrates how an established product portfolio can evolve.

Product management lessons

  • Product evolution: Products can expand beyond their original delivery model.
  • Ecosystem thinking: Connected products and services create dependencies and opportunities for integration.
  • Customer value: New capabilities need to provide meaningful benefits rather than simply increasing the number of features.
  • Continuous investment: Mature products require ongoing decisions about functionality, reliability, pricing, and customer experience.

What a PM should consider

If you manage a mature productivity platform, you may need to balance new capabilities with reliability, usability, integration, and customer retention.

The right priorities depend on the product’s customers, strategy, performance, and competitive environment.

14. Case Study: Product Management in Healthcare AI

Hypothetical scenario

A healthcare technology company is developing an AI-powered administrative assistant to help clinic staff retrieve information and complete routine workflow tasks.

The team has strong engineering capabilities and wants to launch quickly. However, the product must operate within the needs and constraints of healthcare organisations.

What a good PM should consider

  1. Customer needs: Understand the actual administrative tasks and problems.
  2. Safety and privacy: Identify applicable requirements, risks, and access controls.
  3. Technical feasibility: Understand data sources, integrations, and system limitations.
  4. User experience: Ensure staff can understand and use the product effectively.
  5. AI quality: Evaluate accuracy, reliability, and appropriate handling of uncertainty.
  6. Business value: Determine whether the solution addresses a meaningful problem sustainably.

Key lesson

A good PM in healthcare technology needs to balance innovation with patient and organisational needs, technical quality, and applicable obligations.

AI functionality should not be treated as valuable simply because it is new or technically impressive.

15. What Makes a PM Weak or Ineffective?

Understanding common mistakes can help product managers improve their practice.

1. Building features without understanding the problem

A PM accepts a request and immediately adds it to the backlog without investigating the underlying need.

Better approach: Understand the problem, identify the target user, and assess whether the opportunity aligns with product priorities.

2. Treating the roadmap as fixed regardless of evidence

A PM continues to pursue an initiative even after new evidence suggests that the assumptions may be incorrect.

Better approach: Reassess priorities when new information materially changes the decision.

3. Measuring delivery instead of outcomes

A team celebrates the number of features shipped without examining whether customers benefit from them.

Better approach: Connect delivery to meaningful customer and business outcomes.

4. Ignoring technical debt and reliability

A PM prioritises new functionality continuously while neglecting important maintenance, reliability, or security needs.

Better approach: Work with engineering to evaluate technical health and include appropriate improvement work in product planning.

5. Failing to communicate trade-offs

A PM makes a decision without explaining the reasoning, leaving stakeholders confused or misaligned.

Better approach: Explain the decision, the evidence, the trade-offs, and the expected next steps.

16. The Product Manager’s Continuous Improvement Mindset

Why learning never stops

Product management is a profession where customer problems, technology, business conditions, and team dynamics continue to evolve.

A PM needs to improve not only the product, but also their own ability to make decisions and lead effectively.

Questions to ask after a product initiative

  • What did we expect to happen?
  • What actually happened?
  • What did customers tell us?
  • Which assumptions were incorrect?
  • What did the team learn?
  • What should we do differently next time?

These questions help create a learning culture rather than a culture that only focuses on whether a project was completed on time.

Key lesson: A good PM treats every product initiative as an opportunity to learn and improve future decisions.

17. A Practical Framework for Becoming a Better Product Manager

You can develop your product management skills through deliberate practice. The following framework is designed to help you build capabilities across the product lifecycle.

Skill How to practise
Customer discovery Conduct interviews, map workflows, and write problem statements.
Strategy Analyse a product’s target market, positioning, and competitive alternatives.
Prioritisation Rank competing opportunities and explain the trade-offs.
Analytics Define product metrics and interpret usage patterns.
Technical collaboration Learn system architecture, APIs, integrations, and technical constraints.
Communication Write concise product decisions and practise stakeholder presentations.
Leadership Facilitate discussions, resolve disagreements, and align teams around goals.
Lifecycle management Evaluate a product’s growth, maturity, risks, and strategic options.

18. A Product Manager’s Self-Assessment

Use these questions to reflect on your current product management capabilities.

Customer understanding

  • Can I explain who the target customer is?
  • Can I identify the underlying problem behind a feature request?
  • Can I distinguish customer preferences from validated needs?

Strategy and prioritisation

  • Can I explain why an initiative is strategically important?
  • Can I compare opportunities using evidence?
  • Can I explain what we are not prioritising and why?

Execution and collaboration

  • Can I communicate requirements clearly?
  • Can I work effectively with engineering and design?
  • Can I identify risks and dependencies early?

Outcomes and lifecycle

  • Can I define meaningful success metrics?
  • Can I investigate why product performance is changing?
  • Can I recommend improvement, transformation, or retirement based on evidence?

Conclusion: A Good Product Manager Is a Continuous Learner and Decision Maker

Product management is more than building features, managing backlogs, or coordinating development.

It is a discipline that combines customer understanding, strategic thinking, analytical reasoning, technical collaboration, communication, and leadership.

A good Product Manager helps teams understand which problems matter, make informed decisions, deliver useful solutions, and continuously evaluate whether the product is creating value.

They understand that a product can change over time. What worked during launch may not work during maturity. A feature that was valuable previously may need to be redesigned. A product may need to expand, reposition itself, or eventually be retired.

Final takeaway: The strongest Product Managers do not measure their value only by the number of features they deliver. They develop the judgement to decide what matters, the leadership to bring people together, and the discipline to learn from product outcomes.

The journey of becoming a good Product Manager is continuous. Every customer conversation, product decision, delivery challenge, and business outcome provides an opportunity to improve.

“The goal is not to become the person who always has the answer. The goal is to become the person who knows how to ask the right questions, make thoughtful decisions, and help the team create value.”

Suggested next step: Apply these principles to a real product case study. Identify the customer problem, product strategy, prioritisation decisions, key metrics, and lifecycle challenges.

Leave a Reply

Your email address will not be published. Required fields are marked *