They turn knowledge of the market, the customers and the product's performance into explicit strategic choices: where to play, for whom, with what value proposition and at the cost of which sacrifices.
The Product Manager holds the coherence between market needs, company strategy, the business model and product investment. Their role is not to collect every request or to produce a roadmap designed to please every stakeholder. They have to tell structural opportunities from one-off requests, and make the sacrifices comprehensible.
The Product Manager consolidates information from several sources: usage, customer interviews, product data, sales feedback, market movements, economic constraints and what the organisation can actually do. A request from a customer or a prospect is an input, but it does not automatically become a product priority.
The Product Manager decides mainly where to invest and why — the Product Owner works more directly on what the team should deliver within its scope. The Technical Product Manager carries a product whose value is directly technical. The Solutions Engineer works at the scale of a specific sales opportunity. The Product Manager can draw on what they learn, without turning the roadmap into an extension of the sales pipeline.
Market benchmarks
The Product Manager remains sought after in organisations that need to professionalise their product investment choices. Demand is no longer only about command of discovery methods, but about the ability to connect customer knowledge, usage data, strategy, technology and financial performance.
The market is getting better at separating responsibilities once bundled under one title: Product Manager, Product Owner, Growth Product Manager, Technical Product Manager, Solutions Engineer. The strongest profiles are those who can show they choose in a constrained environment and own the cost of their decisions.
Context
In an IT services firm, the Product Manager role makes sense when the company has a genuinely productised offering: software, a platform, a reusable solution or a shared asset serving several clients. When each client gets an entirely different solution and no shared asset is managed over time, the Product Manager title risks masking a project-manager or presales function.
Level 1
Junior
A Junior Product Manager investigates a bounded opportunity within an explicit frame. They gather the available information, gradually tell the request from the underlying problem, and contribute to the analysis of a segment or a use case. They can be swayed by the most recent request, the most visible customer, or the most senior stakeholder's opinion.
Click to read
Level 2
Mid-level
A Mid-level Product Manager autonomously runs a clearly defined product scope. They cross-reference user feedback, usage data, financial objectives and company strategy. They are able to refuse an attractive initiative when it diverts resources from a more important goal.
Click to read
Level 3
Senior
A Senior Product Manager chooses between several credible, competing opportunities. They connect segmentation, differentiation, business model, delivery capacity, adoption conditions and opportunity cost. They factor in technical constraints and presales feedback, without letting a single deal dictate product strategy.
Click to read
Level 4
Expert
An Expert Product Manager redefines the ground the company chooses to play on. They may decide to abandon a segment that is still profitable, delay an expansion, or stop a product. They make visible what the company agrees to lose: short-term revenue, growth rate, functional coverage, or the satisfaction of a major customer.
Click to read
This category measures the ability to define a coherent playing field: segmentation, choice of markets, competition and strategic sacrifices. A Product Manager can have full command of discovery methods while scattering resources across too many segments.
This category measures the ability to understand users without confusing a stated request with a validated problem. The point is not to answer fast, but to determine whether the problem justifies an investment.
This category measures the ability to connect product decisions to their financial consequences: value creation, pricing, packaging, adoption, retention and cost.
This category measures the ability to spread limited resources across several opportunities. A good trade-off also means determining which ones should get nothing.
This category measures the ability to get a decision understood and made to stick without leaning on hierarchical authority alone, while listening to the expertise of the Technical Product Manager, the Product Owner and presales.
The method in action
The scorecard at a glance — hover an axis
Product, presales & customer-facing roles