Portfolio analysis: which products carry the business and which just keep you busy

What does a portfolio analysis actually do?

It answers a question nobody asks in daily business: what are we spending our limited resources on, and what do we get in return? In day-to-day operations, the order in which requests come in decides that. In a portfolio analysis, management decides.

The typical finding in mid-sized companies is always the same: a small share of products delivers most of the contribution margin, a middle group carries itself, and a long tail ties up attention in development, production, spare parts inventory and sales training without leaving anything behind once that effort is deducted. Everyone in the company knows this roughly. What's missing are the numbers a decision can be anchored to.

The real payoff, then, isn't the insight. It's the ability to decide. As long as the picture stays vague, the person with the best story wins the discussion. The moment there's a number for each product, the burden of proof shifts to the people who want to keep a product.

Which numbers do you need?

Three per product or product group. More doesn't make the analysis better, only longer.

• Contribution margin, not revenue. Revenue tells you how much activity a product generates, not how much it brings in. Almost every portfolio has that high-revenue, thin-margin product that everyone internally considers important because its number is big.
• Resources tied up. Development hours, setup times, number of variants, spare parts inventory, sales training needs, complaint rates. This is the figure nobody has cleanly available, and it's the one that makes the difference: it explains why a portfolio with forty items is more sluggish than one with fifteen.
• Direction of demand. Growing, holding, falling: viewed over three years, not one. One year is the economic cycle, three years are a trend.

The effort figure is where most analyses get stuck, because accounting doesn't deliver it. It doesn't have to be exact. A three-level assessment by production, development and service, assigned together in a single meeting, is precise enough for a portfolio decision. And roughly two orders of magnitude faster than a project to build activity-based costing.

How does the four-box matrix work, and where does it mislead you?

The best-known model sorts products into four boxes by market growth and relative market share and derives four courses of action: build, harvest, watch, exit. It comes from the Boston Consulting Group in 1970 and is so widespread because it fits a complex picture onto a single page.

For mid-sized portfolios it has three weaknesses you should know about before using it:

• Relative market share is rarely known. In niche markets without market research it gets estimated, and then the estimate determines the position in the chart, not reality.
• Products are connected. The thin-margin product is often the one that brings the customer into the relationship, or the one that keeps the machine busy that produces the profitable item. Assessed on its own it looks like a candidate for the axe; in context it doesn't.
• It says nothing about capabilities. A box says "build," but not whether you have the people for it. The matrix sorts, it doesn't decide.

For mid-sized companies, a simpler plot is usually more useful: contribution margin against resources tied up, each dot a product, the size of the dot its revenue. This picture needs no market data, it comes from your own numbers. And it shows the question that actually matters: which product keeps everyone busy and brings in little.

What do you do with a product that doesn't make money?

Don't cut automatically. There are four clean decisions, and the analysis only tells you which one is up for review.

The fourth row is the one most often claimed and least often tested. "We need this to get in the door with the customer" is a verifiable statement: if twenty such entries produced two follow-up orders in three years, it was a habit, not a door opener.

Why is cutting so hard?

Because every product has three defenders, and all three are right. There's a customer who buys it. There's someone in-house who developed or introduced it. And there's the worry that losing the product means losing the customer.

On top of that comes an asymmetry that plays out in every leadership meeting: the benefit of cutting is distributed and invisible, a bit more breathing room in production, fewer variants, shorter sales training. The loss is concrete and has a name. In that setup, the concrete wins unless you've agreed in advance how the decision gets made.

What helps is a process, not a discussion. The decision is made once a year, for all products at the same time, with the same three numbers and in the same group. Whoever wants to keep a product makes the case, not the other way around. And every cut gets a date, a last-order deadline and a conversation with the affected customers, held before they find out from a price list.

In practice, a meeting like this rarely ends in wholesale cuts. More often it's three to five products with a price increase and two that get phased out. That's unspectacular, and it still works: these are usually exactly the products that have been tying up a disproportionate share of attention.

How often should the portfolio be on the table?

Once a year as a full review, using the same three metrics so changes become visible. Plus one trigger: whenever a development decision or an investment is pending that locks in a product for years.

The annual review doesn't belong in the budget round. Budgeting is about next year's numbers, and a portfolio discussion loses out there every time against the question of how to close the gap. The better place is the strategy process, or a dedicated half day with a clear task. And with the preparatory work finished and on the table, not done during the meeting.