Killing a Product Line

There is a product, somewhere in your portfolio, that should have been killed two years ago. The team running it knows. The finance partner who closes its books each quarter knows — the gross margin has been drifting south for eight quarters, the customer count is being held up by a single legacy contract, the engineering team assigned to it is more than half-occupied with maintenance. The product roadmap document has been quietly thinned. The marketing budget has been quietly cut. Nobody has written, in any document the executive team has seen, that the product should be shut down. The product continues.

We have, between us, watched this exact pattern in companies across every sector we have worked in. The product changes — it is a regional offering, a product-line extension, a former flagship in decline, a side bet from a previous CEO. The dynamics do not. Killing a product is the decision a typical company runs worst of all the major decisions in its operating cadence, and the cumulative cost of doing it badly is, in our experience, larger than the cost of any single bad launch.

The structural asymmetry

Launching a product and killing a product look superficially like inverse decisions. They are not. They are structurally different in three ways, and the differences explain why almost every company runs the first reasonably well and the second poorly.

The first is constituency. A launch decision is supported by the team that wants to build the product, the executive who wants to sponsor it, and the finance partner who wants the growth on the deck. The opposition, if there is any, is diffuse — the people who would rather the resources went elsewhere, who are not yet organized into a constituency because no specific alternative use of the resources has been proposed. A kill decision inverts this. The kill is opposed by the team that runs the product (they lose their jobs or their org), the executive who originally sponsored it (they lose face), the long-tenured customers who use it (they will complain loudly), the salespeople who depend on it for cross-sell anchors, and the finance partner who is now booking its remaining revenue against a quota. The support for the kill is, again, diffuse — the resources freed will go somewhere, but no specific somewhere yet has a champion. The political math is asymmetric and the kill loses by default.

The second is reversibility. A launch is reversible, in principle, in both directions — you can scale it up, you can scale it back. A kill is reversible only in one direction. Once the team is dispersed, the code is archived, the customers are migrated off, restarting the product is functionally a relaunch with worse economics. The asymmetry makes the kill feel more momentous than it actually is. In practice, the cost of killing a product that should have been kept is usually much smaller than the cost of keeping a product that should have been killed — but the framing in the room is the reverse, because the cost of the kill is concentrated and visible while the cost of the non-kill is diffuse and quiet.

The third is attribution. The launch that succeeds is attributed to the executive who sponsored it; the launch that fails is attributed to "the market" or "execution." The kill, by contrast, is attributed to the executive who pulled the plug, regardless of who originally launched the product. The reputational cost of the kill falls on the person who makes the call, not on the people who built the case for the product in the first place. A senior executive surveying this incentive structure correctly concludes that pulling the plug is a personally expensive thing to do. They do not pull it.

The kill that should have happened two years ago is one of the cheapest acquisitions a company can make from itself. It just looks expensive on the day it gets done.

The three asymmetries compound. A typical mid-sized company we have worked with carries, at any given moment, a portfolio of two to five products that on any honest reading should be wound down. The cumulative drag — engineering time, sales attention, executive cycles, brand confusion, the opportunity cost of the talent the lines are consuming — runs into low double-digit percentages of operating profit. Nobody books it. Nobody sees it. It is paid every quarter, like the decision tax we have written about elsewhere.

How to frame a kill decision

The fix is not willpower. The fix is process. A kill decision run well has three components, each of which addresses one of the asymmetries above.

The first component is a clean separation between "this was a bad bet" and "the world has changed since." This distinction matters enormously, and it is the one most often elided in kill conversations. A product that was launched into reasonable assumptions, executed reasonably, and is now being killed because the market moved is not the same product as one that was launched into wishful assumptions, executed against internal resistance, and is now being killed because the original case was always weak. The first kill is decision hygiene; the second is a learning opportunity. Conflating them costs the company the learning. The executive who sponsored the launch should be allowed — required, ideally — to write the distinction in their own words, on the record, before the kill decision is taken. The act of writing it depersonalizes the kill.

The second component is an explicit expected-value calculation that includes the opportunity cost of the talent the line is consuming. This is the calculation most companies do not do, because the talent cost feels like a fixed cost (the engineers are paid either way). It is not a fixed cost. The right framing is: if we redeployed the team currently working on this product to our highest-EV alternative use, what would we expect them to produce? In our experience this calculation, done honestly, often returns a number two to five times larger than the contribution margin the dying product is throwing off. The product is "profitable" only in the accounting sense. In the economic sense — the sense that matters for portfolio decisions — it is a meaningful destroyer of value, and the destruction grows every quarter the redeployment is deferred.

The third component is a structured portfolio review that the kill decision lives inside, rather than a standalone kill conversation. This is the most important component. A standalone kill conversation has the structure described at the top of this essay: a concentrated group of people defending the product, against a diffuse case for redeployment, with the reputational cost concentrated on the person proposing the kill. A portfolio review inverts the politics. The question on the table is not "should we kill this product?" — the question is "given our top opportunities and our finite resources, which products should we be running, and at what level of investment?" Within that framing, the kill becomes a reallocation decision, which is the executive function. Several of our clients have moved to formal quarterly portfolio reviews where every product line is, in principle, up for re-investment, hold, or sunset. The reviews do not produce a kill every quarter. They do produce, on average, the kills that should have happened, on roughly the schedule on which they should have happened. The drag on the company comes down.

What a good kill looks like

A good kill, in our experience, has a few characteristics worth naming.

It is announced quickly, once decided. The longest-running organizational damage from a kill is not the kill itself — it is the eight months of speculation that precede it, during which the team knows the product is in trouble and is not yet told. Quick announcement, with a clear runway for the team to either be redeployed or transitioned out, costs much less in morale and retention than a slow leak.

It treats customers as a real consideration. The customers who depend on the product are owed a thoughtful migration path. The customers who are nominal users and would not actually miss the product are owed an honest conversation that does not pretend they were ever the strategic core. The kill is not an opportunity to redefine, in marketing, who the company was serving. The customers will remember.

It produces a written postmortem on the bet. Not a blame document. A learning document — what was the original case, what assumptions did it rest on, which of those held and which did not, and what should the company conclude about its next adjacent bet. The postmortem is the thing that converts a kill from a one-time cost into a compounding institutional asset. Most companies do not write it. The few that do find their next launch is meaningfully better-framed, because the company has actually learned something.

It is owned, in the executive team's record, as a decision the team is proud of. This is the cultural piece, and it is the one most companies get wrong. If kills are treated as embarrassments, the executive team teaches itself, by example, that the careers are made by launching and never by stopping. The next generation of executives reads the signal correctly and does not propose kills. If kills are treated as portfolio decisions of the same dignity as launches — celebrated when done well, examined when done late — the next generation proposes them on time.

The board's role

In our experience, the lever that most reliably installs this discipline is at the board. A board that asks, in every quarterly review, a single explicit question — "what would we kill if we were forced to take ten percent of our resources out, and why are we not killing it anyway?" — restructures the executive team's incentives within a year. The question costs the board nothing to ask. It costs the executive team an uncomfortable hour of preparation. It produces, reliably, the kill conversations that were otherwise being deferred indefinitely.

The boards that ask the question end up with leaner, sharper portfolios and more discretionary capital available for the bets that matter. The boards that do not ask end up funding, indefinitely, the slow accumulation of products that the company is no longer the right home for. The two boards are looking at the same company at the same point in time. The difference, five years later, is enormous.

If you are reading this and the product we described in the opening paragraph has a name in your portfolio — and you can already feel the political weight of the conversation that would be required to kill it — that is the kill the company most needs to run, and the kill that will most benefit from being run through an external process rather than an internal one. We are happy to discuss how a structured portfolio review would look in your specific context.