What Product Management Is

A product is anything a business offers repeatedly to many customers to solve a problem for them: a software application, a banking app, a piece of equipment, a subscription service, even a standard training package. A one-off project for one client is not a product. A product lives for years, gets better over time and has to keep earning its place.

Product management is the work of deciding what the product should do, for whom and why, and then making sure the result actually helps customers and the business. The product manager does not usually write the code, design the screens or sell the product. Their job is to make sure that the effort of all those people goes into the right things.

Outcomes, not output

The most important idea in product management is the difference between output and outcome. Output is what the team produces: features, releases, screens. An outcome is a change in what customers do, or in a business result, because of that output: fewer support calls, more repeat orders, faster invoice approval.

A team can ship ten features in a quarter and change nothing that matters. A good product manager measures success by outcomes. A feature that nobody uses is a cost, not an achievement: it must be maintained, tested and explained for as long as it exists.

Two short examples

Example 1. A company that sells fleet-management software receives many requests for a new dashboard. The product manager asks what decision customers want the dashboard to support. It turns out that dispatchers only need to know which trucks are late. A short alert solves the problem with a fraction of the work. The outcome — fewer late deliveries missed — is the same.

Example 2. A training provider adds an online booking page. Bookings do not rise, because most corporate buyers need a quotation approved before they can book. The feature was feasible and usable, but the team never checked its value and viability for the real buyer.