Daily Junction.mobi portalBusiness · June 27, 2025 · Marcus Vale · 6 min
A plain-English guide to product management — what a product manager actually does, how the role differs from project management, and the skills that make someone good at it.
"Product manager" is one of those job titles that everyone has heard and few can define. It sounds like it might mean managing a product, whatever that means, and it is often confused with project management, programme management, or just being the person in charge. In reality product management is a distinct and increasingly important discipline, found in technology companies, established businesses and even government. At its core it answers a deceptively hard question: of all the things we could build, what should we build, and why? This guide explains what product management is, what a product manager actually does, how the role differs from project management, and what makes someone good at it.
Product management is the discipline of deciding what a product should be and why — guiding it so that it genuinely serves customers and meets the goals of the business. A product, here, means whatever a company offers to its users: an app, a piece of software, an online service, sometimes a physical product or a feature within a larger system.
The defining idea is that someone has to own the direction of a product, not just its delivery. Left to itself, a product can drift: engineers build what is interesting, sales promise what closes a deal, executives chase the latest idea, and the result is an incoherent product that serves nobody especially well. Product management exists to prevent that, by making deliberate decisions about what to build, what to leave out, and in what order, all in service of real customer needs and business goals.
So product management is fundamentally about judgement under uncertainty. There are always more good ideas than time and money to build them, and rarely a clear right answer. The discipline is the structured business of making those calls well and keeping everyone moving in the same direction.
A product manager is the person who holds this responsibility. The clearest way to picture the role is as sitting at the intersection of three forces and aligning them:
The product manager's job is to bring these together into a coherent direction: understanding customers deeply, translating that into a sense of what is worth building, and working with the build teams to make it real — all while keeping it tied to what the business is trying to achieve.
In practice this means a lot of communication and decision-making rather than personally building anything. A product manager talks to customers and stakeholders, digs into data and feedback, decides priorities, articulates clearly what should be built and why, and then partners with design and engineering through delivery. The UK government even publishes a product manager role description reflecting how its Government Digital Service uses the discipline to build public services around user needs.
A product manager rarely builds the product themselves. Their job is to make sure the right product gets built — and that everyone understands why.
The most persistent confusion is between product and project management, and the distinction genuinely matters.
| Product management | Project management | |
|---|---|---|
| Core question | Are we building the right thing? | Are we building this thing efficiently? |
| Time frame | Ongoing, over the product's life | Bounded, with a start and end |
| Focus | What and why | Scope, schedule and budget |
| Success looks like | A product customers value | A deliverable completed on time |
Product management is about the what and why, owned continuously across a product's life. Project management is about delivering a defined piece of work — getting a specific thing built on time, to budget and to scope. A product manager decides that a feature is worth building and how it fits the bigger picture; a project manager makes sure that feature is actually delivered efficiently. The two are complementary, and on larger teams both roles often exist side by side, but conflating them leads to products that ship on time yet solve the wrong problem.
Because the role is about judgement and alignment, the skills that matter are broader than people expect, and largely not technical.
The foundation is customer understanding — a genuine curiosity about the people you are building for and the discipline to base decisions on their real needs rather than your own assumptions. On top of that sits business judgement: the ability to weigh trade-offs and connect product decisions to what the business is trying to achieve. Communication is central, because a product manager spends their days explaining, persuading and keeping very different people aligned. And prioritisation may be the defining skill of all — the discipline to say no to good ideas so that the best ones get done, since there is never enough time to build everything.
Technical knowledge helps, especially for technical products, but it is a supporting skill, not the heart of the job. A product manager needs to understand enough to work credibly with engineers and make sound trade-offs; they do not need to be the best coder in the room. Many excellent product managers come from non-engineering backgrounds, because the role rewards the combination above more than any single specialism.
One feature of product management deserves special mention, because it shapes the whole job: product managers typically carry a great deal of responsibility but very little direct authority. They are accountable for whether the product succeeds, yet the designers, engineers and others who build it usually do not report to them.
This means the role runs on influence rather than command. A product manager cannot simply order things done; they have to build trust, make their reasoning clear, and bring people along with a shared sense of why the work matters. The best ones are persuasive precisely because their decisions are well grounded in customer evidence and business logic, so colleagues choose to follow the direction rather than merely comply with it. This reliance on influence is why communication and clear thinking matter so much, and it connects product management to wider questions of how teams set direction together — for example through shared goals and OKRs — and how a business sharpens its unique selling point by deciding deliberately what its product is, and is not, for.
Product management is the discipline of deciding what to build and why, so that a product truly serves its customers and the business behind it. A product manager sits between customers, business goals and the teams that build, aligning all three around a clear direction — distinct from a project manager, who focuses on delivering a defined thing on time and budget. The role rewards customer understanding, business judgement, communication and ruthless prioritisation far more than technical skill alone, and it is defined by carrying real responsibility with little direct authority. Done well, product management is what keeps a product from drifting and ensures the effort of building goes into the right things.
![[View image]](/img/what-is-product-management.jpg){kind=link}