springload

Defining Product Management as a discipline can be hard, here’s everything you ever needed to know!

by Eric Picard

Product Management resides within the “builder” organization, the team responsible for creating products, services, or media offerings to be sold to customers. These offerings are typically developed by engineers, powered by scientists, and designed by product designers. The entire process is orchestrated by Product Managers, who are ultimately accountable for ensuring products are properly defined, developed efficiently, launched effectively, and operate profitably.

The Spectrum of Product Management Work

Product Management spans a wide range, covering everything from what a sales team sells to what an engineering team builds. The work in between encompasses various roles, and in different companies, these roles may be divided differently. Below is a breakdown of the interrelated disciplines, illustrating why Product Management is challenging to define and execute. Note that while each discipline is described separately, Product Managers in many companies may be responsible for multiple (or even all) of these areas in their day-to-day work.

If we move from sales towards engineering, the breakdown sort of looks like this (note that the path isn’t truly linear, so it’s just a loose framework.)

1. Product Marketing / Go-to-Market

Product Marketing involves preparing products for market consumption, ensuring they are presented in a consumable form that sales and marketing teams can utilize to reach customers. Product Marketing is a distinct discipline closely aligned with the builder organizations, although sometimes it reports into Marketing. Product Marketing is not Marketing Communications, and is much more closely aligned to Product Management. Responsibilities include: Developing compelling product positioning that clearly defines the product’s value proposition. Crafting messaging that highlights key differentiators and resonates with target customers. Managing the end-to-end launch process, including internal training, external communications, and post-launch analysis. Sales enablement functions such as creating sales materials, presentations, and demos. A critical deliverable is the Product Positioning document, which includes messages or claims about the product that can be used broadly across the organization and easily transformed into marketing or sales materials. For example, a product positioning statement might be, “Renovate your home with confidence using our easy-to-use device that scans walls for wiring before you begin a project.”

2. Product Strategy / Product Planning

This discipline focuses on determining what to build, requiring extensive research to understand market needs. It includes competitive analysis to understand the market landscape, customer research to gather insights from current, potential, and former customers, and market requirements analysis. The long-term vision, ideally spanning three years, often resides here. A key deliverable is the Market Requirements Document, distinct from Product Requirements Documents, which emphasizes customer needs without detailing implementation specifics. For instance, a market requirement could be, “Customers need a way to find wires inside walls to avoid accidentally cutting them during renovations.”

3. Product Operations

Product Operations might fall under the Product Manager’s purview or exist as a separate discipline, especially in larger companies. This role manages the business of existing products in the market, ensuring product health, profitability and alignment across teams. It involves defining and measuring metrics to ensure product success, optimizing to increase profitability, and collaborating across disciplines to maintain clear communication and alignment. Product Operations is often responsible for pricing, performance measurement, and ensuring products meet KPIs and business goals. Product Operations Specialists work closely with Product Management, Engineering, Marketing, Sales, and Customer Support to align all aspects of the product effectively. A primary task is defining and implementing product dashboards to measure performance against KPIs.

4. Technical Product Management

Often considered the “core” of Product Management, Technical Product Management is responsible for creating and managing a product roadmap. This includes developing a Product Requirements Document that spans multiple releases, breaking it into individual features, and writing specifications. It involves collaborating with Product Design for user-facing features to develop prototypes, design systems, and screen layouts. Technical Product Managers work closely with Engineering to ensure requirements are clear, fostering debate and improvement within a healthy organization. They also collaborate with Sales and other customer-facing teams to ensure feature prioritization aligns with business needs and work with Marketing to ensure demand creation. They often manage daily coordination efforts like standups or scrums, or other mechanisms for coordinating the day-to-day work related to building and releasing software (unless a Technical Project Manager is assigned to the project, in which case they do those things). A primary deliverable of a Technical Product Manager is the Product Requirements Document, which details necessary features to solve customer problems while avoiding implementation specifics, which are handled by Engineering. Another important deliverable is the Product Roadmap, which can take a variety of forms. Ultimately PMs are responsible for defining the product and getting the right product built, and writing requirements is a core function. A good high level requirement could be, “Create a small handheld device that clearly alerts a customer that active or inactive electrical wires are inside of a given wall.”

5. Technical Project Management

Technical Project Management focuses on coordinating engineering and other resources across a complex organization with varying timelines and levels of effort. The purpose is to keep projects on track and ensure complete transparency and coordination across teams. A key responsibility is maintaining a unified Gantt Chart, detailing team deliverables and timelines. Unlike other roles, Project Managers aren’t tasked with deciding what to build or communicating product details; they ensure that all teams understand their responsibilities, deadlines, and resource allocation, optimizing the efficiency of the overall process.

6. Product Design

Product Designers, sometimes called User Experience Designers, have a unique discipline within the world of design. Very often Product Designers are misunderstood by people outside of their day-to-day working chain as Graphic Designers. While Product Designers do sometimes create work that feels a bit like Graphic Design, their work is fundamentally different. The discipline ranges broadly from Research to Usability. User Experience Research includes deliverables like User Journeys, User Personas, Competitive Analysis Reports (from a design perspective), and Usability Research. They own the look and feel of the product by implementing design system that define how all aspects of the product look, and what the user interaction model of the product will be. This includes colors, fonts, and various elements of the styling of the product (buttons look like this, form fields look like that, there should be x many pixels buffer around images, etc…). Execution oriented deliverables include Information Architectures, proof of concept Wireframes, Pixel-Perfect Wireframes, and clickable prototypes. Product Designers, especially those building digital products or software, establish a design system for all aspects of the user experience. Product Designers are also responsible for usability testing and talking to customers about the products that they use to understand what works, and what doesn’t work. They sometimes do this with quantitative methods, and sometimes qualitative methods. Often they will also use automated tools that provide heatmaps and click-tracking analysis to show what users are looking at on the page, and what paths they are taking through the product or site.

A Complex Discipline

As you can see, the discipline of Product Management is complex and comprehensive. The work extends across a lot of discrete skills, and requires many different capabilities. Finding a product person who excels in all of these various disciplines is hard, we usually refer to those people as “Unicorns.” At early stage startups, the product managers are generally responsible for several, if not all, of these disciplines. As companies mature, the work breaks down into specific roles and responsibilities. When I was at Microsoft each of these were very clearly defined and separate roles, albeit sometimes with different names. Unicorns do exist, you can find people with the ability to effectively do all of this work, and to do it well. But they are extremely rare. My advice to most companies is to figure out what your teams do well, and what they need help with. Then find a logical breakpoint between the disciplines and establish the work in a way that everyone involved celebrates, rather than feeling like the work that they are good at and enjoy is being ‘taken away’ from them.

To show you how these teams interact, see the chart below. We’re looking at the product development life cycle from Left to Right, and the interaction between Product Marketing, Product Strategy and Product Management. You can see that Product Strategy starts the process off, and then hands off to Product Management. As the life cycle progresses, different roles are more or less engaged.

This is a product development life cycle map from a very mature company with a global footprint. Smaller companies will have less complexity in their map, and frankly, the roles will condense down to one or two rather than all three.

This chart doesn’t include software developers, scientists, researchers, technical operations, release management, product designers, or product operations. You can imagine how complex things might get in a fully resourced organization – and why a team might need a Technical Project Manager to coordinate it all.

I hope this gives you some sense of what Product Management as a discipline is all about. It takes a lot of work to build a product. Whether you’re a 3 person team or a 300,000 person organization, the work is the work, is the work. It all needs to be done in order to deliver a great product. It’s just a question of how large the offering is, and how streamlined of a process the team can use in order to deliver the product in a reasonable amount of time.