product-lifecycle-plays skill

Product Lifecycle Plays

Purpose

Decide what to do with a product that has stopped growing. There are three plays — extend, replace, retire — and picking the wrong one is expensive in a different way each time. This skill gives you the stage diagnosis, the criteria that discriminate the plays, and the hazard register for the one that goes wrong most often.

Most teams skip straight to a play. Someone says "let's rebuild it" or "let's kill it," and the argument that follows is about the answer rather than the diagnosis. The diagnosis is the work.

Input

Works best with: The product or product line, and the signal that prompted the question — flattening revenue, rising support costs, a competitor move, a strategy shift.

Also useful: Revenue and margin trend, customer counts and concentration, support load, what else in the portfolio is adjacent, and how much investment appetite exists.

Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.

Arriving empty-handed? That works too. Bring the product name and a hunch. The stage diagnosis runs off the transition questions below, which are answerable from what a PM already knows without pulling a report.

Example invocations:

• Revenue on our reporting module has been flat for six quarters — extend, replace, or retire?
• Run the play worksheet across our four aging SKUs.

Key Concepts

The Product Life Cycle

Five stages, each with a different economic job:

Go-to-market happens at the front. End-of-life happens at the back. The plays live at the mature-to-decline inflection — which is exactly where most teams have no framework and default to whoever argues hardest.

The Strategy Grid

What "good" looks like changes by stage. Each lever tells you something different about where you actually are:

The Transition Questions

This is the diagnostic. For each lever, ask the question that tells you whether you've crossed from mature into decline. Answering "yes" to four or more means you are in decline regardless of what the revenue chart says this quarter:

Why ask rather than measure: revenue lags. A product can post a flat quarter while every one of these has already turned. The questions catch the inflection before the chart does.

The Three Plays

Extension Play — introduce a new variant or additional features to an existing product line.

Reasons why: expand into new customer segments · meet diverse customer needs · differentiate from competitors · boost sales with new variants · strengthen brand loyalty.

Shape: the existing product keeps running; you add alongside. Cheapest play, lowest risk, and the one most often dismissed because it isn't exciting.

Replacement Play — introduce a new product to take the place of an existing one, offering similar or improved capability while phasing the old one out.

Reasons why: address supply issues · reduce production costs · eliminate obsolete or unused features · align with strategic goals · comply with regulatory change.

Shape: GTM and EOL happen simultaneously. This is the expensive play, and the reason is structural — see below.

Retirement Play — phase the product out without a successor of your own.

Reasons why: costs exceed revenue · strategic exit from the market · the core problem stopped existing · technology made it obsolete.

Shape: pure EOL. Customers land somewhere else, possibly a competitor, and the goal becomes losing the product without losing the customer.

Why Replacement Is the Expensive Play

On a replacement you are running a launch and a retirement at the same time, for two products that compete with each other. Every GTM risk and every EOL risk applies at once, plus one that only exists here: cannibalization between your own two products.

Both directions of that failure are instructive:

pricing dynamics they had to manage for years.

• Kodak feared cannibalizing film and starved its digital business. The fear cost the market.
• Amgen cannibalized Epogen with Aranesp deliberately. It worked, and still produced complex

Fear it and you lose the future; ignore it and you lose margin. Plan for it and you get a transition.

The Seven Replacement Hazards

What goes wrong on a replacement play, with the pattern each one leaves:

Hazard 7 is the one this repo's EOL suite exists to prevent — and it's the one teams discount most, because by the time they're planning the launch, the retirement feels like paperwork.

The Risk Register

For each hazard that applies, fill five columns. The fifth is the one people skip:

A register with no contingency column is a worry list. Plan B is what makes it a plan.

Anti-Patterns (what this is NOT)

see ansoff-matrix and organic-growth-advisor.

• Not a growth framework. Where the next tranche of growth comes from is a different question —

support cost is a harvest, not a project.

• Not a forecast. It reasons about stage and direction, not numbers.
• Not automatic. Decline is not a death sentence; a mature product throwing off margin with low

interact — two products can't both be the replacement.

• Not one product at a time, necessarily. The worksheet runs across a line, and the plays

Application

Use template.md for the worksheet and risk register.

Step 1: Diagnose the stage

Run the seven transition questions. Count the yeses:

changing an outcome

• 0-1 yes — mature and healthy. The question isn't a play, it's whether to invest more
• 2-3 yes — mature and softening. Extension play territory; watch quarterly
• 4-5 yes — crossing into decline. Pick a play deliberately, now
• 6-7 yes — in decline. Replace or retire; extension likely postpones a decision rather than

Write down which questions came back yes. The pattern discriminates the plays more than the count does.

Step 2: Identify what's driving the pressure

Three sources, and they point at different plays:

The trap: supply-side pressure feels like a customer problem when it reaches the roadmap. "We need to rebuild this" often means "our costs are bad," which is a legitimate reason for a replacement — but say it out loud, because it changes what success looks like.

Step 3: Test the extension play first