Why Product Management should recognise its multidisciplinary nature
Product management is often described as the intersection of business, technology and user need. The familiar Venn diagram is neat, reassuring and misleading.
Product management is often described as the intersection of business, technology and user need. The familiar Venn diagram is neat, reassuring and misleading.
It implies boundaries.
In practice, product management has no clean edges. It is not a discipline that simply sits between others. It is a synthesis discipline, one that borrows, adapts and recombines expertise from across an organisation. That is also why product management cannot be separated from strategy. Strategy is not something product merely executes, it is something product continually shapes through choices made under constraint.
Marty Cagan and SVPG position empowered product teams as accountable for outcomes, for ensuring what is built is valuable and viable, not merely delivered. That framing places product squarely inside strategy, not downstream of it.
And yet, as organisations mature, a subtle fragmentation tends to emerge. Discovery becomes something research does. Requirements become something business analysis does. Sustainability becomes something a specialist network does. Delivery becomes something programme management does. Strategy becomes something leadership workshops produce.
Product risks narrowing into coordination.
The synthesis problem in practice
This tension becomes especially visible in public sector transformation.
In one programme, we began discovery with almost no validated evidence base. There was a strong assumption that digitisation would generate cost savings, but limited data to support it. The task was not to prioritise features, it was to interrogate an economic hypothesis without bias.
That work required economic reasoning about marginal cost and long-term savings, business analysis to map current-state processes and regulatory dependencies, systems thinking to anticipate knock-on effects across the wider ecosystem and political literacy to understand institutional incentives.
Kanban boards and collaborative tools helped structure the work, but the real challenge was integration. Had we treated economics as “finance’s job”, modelling as “analysis’ job” and strategy as “policy’s job”, product would have reduced itself to delivery administration. Instead, it operated in the uncomfortable space of synthesis, i.e. validating or invalidating cost assumptions and enabling better strategic decisions.
The same pattern surfaces in central government digital identity work. On the surface, transaction monitoring and fraud detection look like technical challenges. But deeper questions quickly emerge: what false positive rate is acceptable in a public identity system? How much friction can users tolerate? How do you balance fraud prevention with accessibility and trust?
These are statistical, ethical and strategic questions that are intertwined. Data science alone cannot resolve them. Nor can policy alone. Product decisions must integrate risk appetite, user impact, operational feasibility and public accountability simultaneously.
Even in retail environments, the dynamic holds. Revenue optimisation intersects with behavioural psychology, operational constraints and brand positioning. A change that improves short-term conversion but increases returns, customer service costs or erodes trust is not a strategic win. Product choices become strategy expressed in increments.
Strategy is not handed down - it is refined through learning
Melissa Perri’s framing of product strategy as an evolving system of aligned outcomes is instructive. Strategy is not a static directive, it is refined through learning. Roadmaps composed of outcomes and hypotheses rather than feature lists are strategic instruments. In practice, especially where evidence is initially weak, product-level learning can materially reshape what is considered viable or desirable at portfolio level.
Business analysis sits directly within this synthesis too. The International Institute of Business Analysis defines it as enabling change by defining needs and recommending solutions that deliver value. In both regulatory and service-delivery contexts, modelling current-state processes, identifying constraints and exposing hidden assumptions were not adjacent to product work, they were integral to it. If product abdicates that literacy entirely, it loses the ability to interrogate scope and value effectively.
The danger of clean separation
The risk of separating disciplines too neatly is local optimisation.
Delivery optimises for throughput. Data optimises for rigour. Policy optimises for compliance. Sustainability optimises for carbon reduction. Commercial teams optimise for revenue. Each is rational within its own boundary. Systemic optimisation rarely happens without integration across those boundaries.
Product management, at its best, is that integrative function. Recognising this does not mean inflating the role. It does not mean claiming to be an economist, a data scientist or a policy expert. It means accepting that product judgement depends on borrowed literacies: enough economic fluency to question cost assumptions, enough analytical rigour to model change, enough strategic awareness to understand organisational incentives and enough systems thinking to anticipate second-order effects.
Product cannot be cleanly extracted from strategy, because strategy is expressed through product decisions. Nor can it be cleanly extracted from business analysis, because defining needs and navigating constraints are not optional extras, they are core to determining what is worth building.
The more we attempt to separate product from the disciplines it synthesises, the more we hollow it out into process.
The work is not to draw sharper boundaries. It is to recognise that product management is inherently multidisciplinary and that its value lies precisely in the integrative space between expertise.