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

What does a portfolio analysis actually do?

It answers a question that never comes up day to day: what are we spending our limited resources on, and what do we get in return? In daily business, the order in which requests arrive decides that. In a portfolio analysis, management decides.

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

So the real payoff isn't the insight, it's the ability to decide. As long as the picture stays approximate, 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, just longer.

• Contribution margin, not revenue. Revenue tells you how much activity a product creates, not how much it brings in. Almost every portfolio has that high-revenue product with a thin margin that everyone internally treats as important because its number is big.
• Effort tied up. Development hours, setup times, number of variants, spare parts inventory, sales training needs, complaint rates. This is the figure nobody has cleanly at hand, 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, measured 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 supply 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 version sorts products by market growth and relative market share into four boxes and derives four behaviors from that: build, harvest, watch, exit. It came from the Boston Consulting Group in 1970 and it's 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 you use it:

• Relative market share is rarely known. In niche markets without market research, it's estimated, and then the estimate determines the position in the picture, 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 one. Assessed on its own it looks like a candidate for cutting. In context, it isn't.
• It says nothing about capabilities. A box says "build," but not whether you have the people to do it. The matrix sorts, it doesn't decide.

For mid-sized companies, a simpler chart is usually more useful: contribution margin against effort 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 earn 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 checked. "We need this to get in the door with the customer" is a testable 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 the company who developed or introduced it. And there's the worry that losing the product means losing the customer too.

On top of that comes an asymmetry that plays out in every leadership meeting: the return from cutting is distributed and invisible, a little more 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 procedure, not a discussion. The decision is made once a year, for all products at the same time, using the same three numbers and with the same group of people. Whoever wants to keep a product presents the case for it, not the other way around. And every discontinuation gets a date, a last order option, 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 clear-cutting. More common are three to five products whose price goes up, and two that are phased out. That's unspectacular, and it works anyway: these are usually exactly the products that have absorbed a disproportionate amount of attention.

How often should the portfolio be on the table?

In the StrategyFrame®, this analysis belongs to the module "Own Realities," the last of the six in the situation analysis. It comes last on purpose: if you look at your own numbers before looking at customers and competitors, you judge them without the benchmark they depend on. A good margin in a shrinking segment looks like a success in the spreadsheet.

Once a year as a complete round, using the same three measures, so changes become visible. Plus one trigger: whenever a development decision or an investment is coming up that locks in a product for years.

The annual meeting does not belong in the budget round. The budget is about numbers for next year, and there a portfolio discussion loses 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 prep work finished and on the table, not produced during the meeting.