Product Portfolio Management

Ask most product companies to describe their portfolio and they'll walk you through it product by product: this one's core, this one's mature, this one's new, this one's someone's pet project from three years back. Ask them why each one is still getting commercial attention, and the answers get vaguer fast. That gap, between knowing what's in the portfolio and knowing why, is where most product portfolio management consulting conversations end up starting.

One portfolio review we sat in on had a product like this three items down the agenda: mature, technically declining, but nobody had proposed killing it in at least two planning cycles. Revenue was flat rather than falling, so the case for keeping it going always sounded reasonable in the room. When we asked who the product was actually winning with now, versus five years ago, nobody had a segment to name. Just "it's always sold." That's not evidence. That's momentum with a spreadsheet attached.

It's not usually a crisis, and that product wasn't losing money. The portfolio just quietly grows, product by product, decision by decision, until commercial energy is spread across more offerings than the organisation can actually push hard on. Getting the commercial agenda built in the right order helps here, since portfolio prioritisation only produces a defensible answer once market focus has already settled which segments the business is actually building for. But sequence alone doesn't tell you how to sort what's already on the shelf. That's a separate discipline, and it's one most organisations run once a year, badly, instead of continuously.

Not every product needs the same test

Part of the reason portfolio reviews feel unproductive is that every product on the table gets judged by the same yardstick. Revenue this quarter. Margin this quarter. Growth versus last year. That works fine for a product that's mature and should be delivering exactly that. It's the wrong test entirely for something newer.

A useful way to sort the portfolio is by what each product actually needs right now, not by what category it sits in on an org chart. Some products are still unproven — the demand signal is real but thin, and what they need is validation, not a growth target. Some are proven and scaling, and what they need is investment: more sales attention, more production capacity, more marketing spend. And some are mature, already winning, and what they need is efficiency and margin discipline rather than more resource thrown at them.

Put all three on one dashboard measured against one set of KPIs and the unproven product always looks like it's failing. It hasn't had the chance to prove anything yet, and it's being compared against a product that's had years to mature. [future link to #36] This is exactly the trap that kills innovation at the portfolio layer: a genuinely promising idea, still early, evaluated on the same revenue expectations as something ten years into its life.

The fix isn't complicated, but it does require discipline most portfolios don't have: three different sets of expectations, three different funding logics, three different conversations at the leadership table, instead of one spreadsheet pretending everything's comparable.

"An unproven product judged on a mature product's numbers will always look like it's failing."

Push, pull, exit — and the question that should decide it

Once the portfolio is sorted by what each product needs, the harder decision follows: where does commercial energy actually go next. Which products get pushed, which get maintained without extra investment, and which get exited so the resource can move somewhere it earns more.

Most organisations answer this from internal reporting. Which product line shows up biggest on the P&L. Which one has the loudest internal sponsor. Which one finance flagged as flat this quarter. None of that tells you where demand is actually heading, and a portfolio call made on last quarter's revenue is really a decision about where the business has already been, not where it's going.

The value proposition work makes the better starting point clear. Portfolio decisions stop being about which products the organisation likes keeping and start being about which ones a specific segment will genuinely pay for. That's a demand signal, not a revenue line. It comes from what buyers are actually choosing, what they're asking for that nothing in the range currently answers, and where they're walking away because the fit isn't there. A product can look healthy on the P&L and still be losing ground with the exact segment it was built to serve. The revenue just hasn't caught up to that yet.

Building a push, pull, exit process around customer demand rather than internal reporting means the uncomfortable conversations happen earlier, while there's still time to act on them, rather than eighteen months later when the numbers finally confirm what the market already knew.

The test that "it's not losing money" fails

There's a version of portfolio discipline that stops at the easiest question: is this product profitable. It's the wrong question, or at least an incomplete one, because plenty of products clear that bar and still shouldn't be getting the attention they're getting.

That mature product from the review is a good example of exactly this. It wasn't losing money. It was consuming a slot in the sales conversation, a line in the support playbook, and a place at the planning table that a product with a segment to point to would have used better.

Complexity has a cost that doesn't show up cleanly on a P&L. A product line that requires its own support playbook, its own sales training, its own set of exceptions in the delivery process, is draining resource in ways that get absorbed into overhead rather than attributed back to the product causing it. Product Strategy for Manufacturers makes this point from the manufacturing side: portfolio decisions are resource allocation decisions, not product decisions, and the same logic holds well beyond manufacturing. A consumer product company carrying a long tail of SKUs that each sell in small volumes faces exactly the same maths, just with different line items.

The better test isn't whether a product is profitable in isolation. It's whether it's helping win in a space the business has actually committed to, with a segment it understands, or whether it's just there because removing it feels harder than keeping it. Plenty of products pass the first test and fail the second, and it's the second one that should decide whether they keep getting resource.

"The question isn't whether a product is profitable. It's whether it's helping win where you've actually committed to compete."

Making this a discipline, not an annual event

None of this works as a once-a-year portfolio review. Demand signals shift continuously, and a decision that was right in January can be wrong by autumn. The organisations that manage this well treat portfolio prioritisation as a standing input to planning, not a slide deck produced once and revisited when someone remembers.

That's also where this connects to the layers above and below it. The portfolio decisions made here are the direct input to the commercial roadmap. Get the portfolio calls wrong and the roadmap is sequencing work against the wrong priorities from the start. Making the funding side of this real, rather than a political negotiation dressed up as strategy, is what separates portfolio intentions from portfolio outcomes. And the tension between what product wants to build, what commercial wants to sell, and what delivery can actually support is exactly where portfolio disagreements tend to surface between functions, which is a conversation in its own right.

The place to start isn't a full portfolio overhaul. It's a smaller test: for each product currently getting meaningful commercial attention, can anyone in the room name the segment it's winning with and the demand signal that says it should keep getting that attention? Where the answer is vague, that's not a product problem. It's a portfolio decision that's overdue.

Key takeaways

Portfolio management fails when every product is judged against the same KPIs regardless of whether it's unproven, scaling, or mature — an unproven product will always look like it's failing next to one that's had years to prove itself.

Push, pull, and exit decisions made from internal P&L reporting reflect where the business has already been, not where demand is heading. Decisions built on customer demand signals surface the uncomfortable calls earlier.

A product can be profitable in isolation and still be the wrong thing to keep investing in. Complexity cost — support burden, sales training, delivery exceptions — rarely shows up cleanly against the product causing it.

The real test for any product isn't whether it's losing money. It's whether it's helping win in a space the business has committed to, with a segment it actually understands.

Portfolio prioritisation works as a continuous discipline, not an annual review. Demand signals move faster than most planning cycles account for.

FAQ

What is product portfolio management?
It's the ongoing discipline of deciding where commercial energy and resource go across a product range — which products to push, which to maintain, and which to exit — based on where customer demand is actually heading rather than on internal revenue reporting alone.

How do you decide which products to cut from a portfolio?
Start with whether the product is helping win in a segment the business has genuinely committed to, not whether it's profitable in isolation. A product can clear the profitability bar and still be consuming resource, in support, sales attention, and delivery complexity, that would deliver more value directed elsewhere.

Why do portfolio reviews usually fail to change anything?
Because they judge every product against the same set of numbers regardless of where it is in its life. A newly launched product measured against a mature product's revenue expectations will always underperform, which makes the review look decisive without actually being useful.

What's the difference between a market trend and a portfolio decision?
A trend is an observation about where demand might be moving. A portfolio decision is a commitment to allocate resource toward a specific product because of what a specific segment is actually choosing to pay for. Confusing the two is how portfolios end up chasing every visible trend without winning anywhere.

How often should a portfolio be reviewed?

Continuously, not annually. Demand signals shift throughout the year, and a portfolio call made in January against the year's plan can be wrong by the third quarter if nothing is revisited in between.