The Product Discipline's Ownership
by Eva Skoglund
Simply put, our job in the Product discipline is to equip Engineering, Sales and Marketing so that they can build the product, sell the product and communicate the product in an orchestrated way. If we fail at this orchestration, we will fail at building a product business.
As product managers, we interface with several different functions in the company, and between all of them, the three most important ones are Engineering, Sales and Marketing. My view is that we need to view Product as its own discipline within the company, and that this discipline needs to take greater ownership of the interface not only with Engineering, but also with Sales and Marketing.
The most fundamental thing we do as product managers is Product Definition (see picture below). We define functionality, commercial packaging, pricing, business models, etc. Both Engineering and Sales need to understand really well how the entire commercial product is defined.
What we also need to do is Product Positioning, which is the foundation for everything done in Sales and Marketing. Positioning includes differentiation, value definition, target market characteristics and market categorization.
And lastly, we work with Usage Growth of our product. What unites Engineering and Marketing is the goal of increasing usage of the product. (This is mostly important for SaaS products and digital marketing contexts, but it is relevant for other types of solutions as well).
If we think about what it is that Product Management should deliver to the three primary functions (the arrows in the picture above), the output to Engineering is straight forward. Everyone knows it’s about functionality descriptions, problems-to-be-solved (or job-to-be-done), product requirements, usecases, roadmap and product planning, because it's what they need to build the product. This is a well known area, with established methods and tools, and it is extensively described in literature and courses. I would claim: how Product Management should interface with Engineering is essentially a ”solved problem”.
But, what is it that the Product discipline should deliver to the Sales and Marketing functions? If the output to Engineering is a roadmap and requirement descriptions, what it is the actual output to Sales and Marketing? What do we fill those output arrows with? As long as we as product managers only deliver essentially the same thing to Sales and Marketing that we deliver to Engineering - meaning functionality descriptions in various forms - do we really enable them to sell and communicate the product in the best possible way? My answer is No.
In my experience, there are two things the Product discipline should deliver to Sales, and two things we should deliver to Marketing:
Customer Characteristics - in depth descriptions of our best-fit-customers (To Sales)
Value Equation Blueprints - translation of benefits to monetary value parameters (To Sales)
Context Setting - the bigger picture and reason of existence of our product (To Marketing)
Buying Assets Logic - making our product easy to buy for customers (To Marketing)
How the Product discipline needs to interface with Sales and Marketing is both an undeveloped and undefined area. While we may have "occasional success", product people usually don't work in a deliberate manor where we take active responsibility and ownership of how we best equip our Sales and Marketing teams. This can be the root cause of why we may have a great product, but not a great business.