Understanding Product Management

Product Management is not just a phase in the product lifecycle — it is the continuous process of taking a product through ideation, development, deployment, marketing, gathering customer feedback, and then repeating the cycle. The actual job is to maximize the value that customers can derive, while respecting the business constraints that inevitably exist.

This balancing act is the core challenge of product management.

Consider Facebook’s business model. Facebook makes money by selling ads. Ads are fundamentally a poor experience for users — they interrupt what users want to see. The ideal user experience would be a news feed free of ads and promotional content. Who wants to see the 10 millionth cat video from a random stranger? But if Facebook removed ads entirely, it would have no revenue and would have to shut down.

This is where the art of product management comes in — balancing two conflicting priorities to maximize the value users can derive.

The problem gets more complex when you realize that the users of Facebook’s product are not the only customers. The advertisers who pay to publish ads are the real customers from a business perspective. Product management tries to solve exactly this kind of problem: how to balance the demands of two very different sets of users — content consumers and ad publishers.

Product management requires a broad, diverse set of skills

Successful product management demands expertise spanning multiple domains — market research, user experience, branding, technical understanding, business strategy, and more. The core responsibility is building a product that maximizes sales revenue, market share, and profit margins by maximizing the value users can derive.

This focus on user experience is not new. The origins of product management date back nearly a century.

The origins of product management date back to 1931

Product management traces back to a memo written by Neil McElroy at Procter & Gamble in 1931. McElroy wrote an 800-word memo requesting two new hires to serve as Brand Managers. These Brand Managers would be absolutely responsible for a brand end-to-end — from tracking sales to defining the product to planning promotions.

Not only did McElroy get his hires, but his memo set the direction for a customer-centric role that would evolve into modern product management. His ideas influenced companies such as Hewlett-Packard and laid the foundation for the role we know today.

For those interested, I recommend reading these articles to understand the history and evolution of product management:

• https://www.mindtheproduct.com/2015/10/history-evolution-product-management/
• http://queue.acm.org/detail.cfm?id=2683579
• https://www.oreilly.com/ideas/the-evolving-role-of-product-management

The product management role evolved into multiple specialized roles

When I first heard the term Product Management and its responsibilities, my immediate thought was: where will I find a single individual with all these diverse skills? And if I do find such a person, they would be insanely expensive.

It turns out product management quickly fragmented into a diverse set of roles, each bundling various skill sets. Only one of those roles is the Product Manager — which is the focus of this course.

In this section, I will walk you through the different roles that have emerged within the domain of product management.

The Product Manager owns business strategy, design, and engineering skill sets

The Product Manager role overlaps with other roles like Product Marketing, but what makes the PM role stand out is the responsibility and accountability for the success of the product.

A Product Manager typically owns:

• Business strategy: defining what to build and why
• Design: shaping the user experience and interface
• Engineering: collaborating with developers to build the product

The PM is ultimately accountable for the product’s success or failure.

The PM Triangle: understanding the spectrum of product roles

Product management covers a wide range of deliverables and tasks. The PM Triangle is a useful model to describe the concentration of different roles along three edges and corners — technical strategy, technical marketing, and marketing strategy.

In practice:

• The Technical PM role is common in many companies.
• The Product Strategist role exists in large corporations with specialized teams.
• Tactical Product Marketing may be generalized as Marketing Specialist or Manager.

Understanding these roles helps reduce confusion in the field. In mid to large organizations, it is critical to identify functional gaps using a model like the PM Triangle. A product manager’s role is diverse and crucial to a product’s success — knowing where a PM focuses enables better collaboration and coverage.

The Product Manager role is about leadership through influence — not authority

A common misconception is that Product Managers are mini-CEOs who have authority over their teams. The reality is very different.

No one on the product team reports directly to the Product Manager. Designers, developers, and other stakeholders work collaboratively but do not have a reporting relationship with the PM.

The PM must lead through subject matter expertise, clarity of vision, and influence — not through authority.

This is why the term “Product Manager” is something of a misnomer. A better term is “Product Leader.”

The PM’s influence must be so strong that stakeholders respect their opinions and look to them for solutions.

The diverse skills a Product Manager must master

Product management is challenging and requires a diverse skill set across different buckets:

Design skills

• Visual design patterns
• Human-computer interaction guidelines
• User experience principles
• Advanced user research
• Information architecture

Engineering skills

• How APIs work
• Mobile app architecture
• Internet protocols
• Database design
• Notification systems
• AI/ML basics
• A/B testing

Business skills

• Pricing strategies
• Opportunity evaluation
• Market segmentation
• Business case creation
• Prioritization frameworks
• Market research and sizing
• Product-market fit analysis

Influencing skills

• Rallying opinions around product value
• Active listening and evangelism
• Articulating value clearly
• Bridging business, users, and tech teams
• Stakeholder engagement and conflict resolution
• Decision making under uncertainty
• Communication with CxO-level executives

Synthesis skills

• Integrating inputs from multiple sources into a coherent vision
• Building product strategy and roadmaps
• Collaborating with business analysts, designers, developers, and stakeholders

Mastering these skills takes time and practice. The PM role is not easy, but it is deeply satisfying for those who embrace it.

The Product Manager is accountable but lacks direct authority

The PM is accountable for the product’s success but has no direct authority over the team members building it. This is by design — it ensures honest feedback and collaboration without power dynamics skewing communication.

Typically, the PM reports to the CEO or a senior executive.

The PM’s job is to influence through logic, expertise, and vision to align the team toward shared goals.

The product lifecycle is iterative and helix-shaped

Product management is not a linear process. The product goes through cycles of ideation, development, deployment, marketing, and customer feedback — then repeats.

You can think of this process not as a single circle but as a helix that moves upward with each iteration, increasing value and learning.

Every decision revolves around delivering value to customers within business constraints.

Supporting media

Test yourself: The PM Triangle roles

Where to go next

• If you want to understand what product management actually entails: What Is Product Management
• If you want to develop a product mindset: Product Thinking
• If you want to explore the PM career path: The PM Career Ladder
• If you are preparing for your first PM role: Breaking Into PM
• If you want to learn how to run discovery and user research: User Research Methods