Stop / Pivot / Invest: A Survival Metrics Primer

Your team already knows which products on your roadmap shouldn't be there.

They have no legitimate mechanism to say so.

Three weeks. Three versions of the same problem.

Your dashboard shows what leadership declared as priority — not what's actually surviving. Nobody in the meeting has permission to say "kill it." And upwards of thirty percent of your delivery capacity is maintaining features nobody planned to own.

These aren't three separate problems. They're one problem seen from three angles: the measurement problem, the permission problem, and the cost problem. Stop / Pivot / Invest is what you run when you're ready to address all three at once.

I ran a Stop / Pivot / Invest session and invited customer success and marketing into the room. I used to run these sessions with product teams only. We were always making placements with partial signal and didn't know it. This time the CS manager spoke first — and surfaced three products that customers had quietly stopped asking about. None of that signal was in any dashboard. The placements shifted in the room based on information product had never had access to, because nobody had built a mechanism for it to arrive.

The exercise produces decisions — not classifications. That distinction matters more than the framework.

Stop / Pivot / Invest isn't a framework. It's a conversation your team has been trying to have for months.

Three categories. Three commitments.

Most frameworks give you buckets. Stop / Pivot / Invest gives you decisions.

Stop means this product is no longer earning its place. The survival signals are absent or negative. The customer need is gone, or better served elsewhere. Stopping isn't failure — it's the delivery capacity that comes back. A Stop decision needs three things: a named date, a named responsible party, and a plan for the maintenance handoff. Without all three, it's a classification. Not a decision.

Pivot means the product has potential the current form isn't realizing. The survival signals are weak but not absent — there's a customer need, but the approach isn't finding it. A Pivot decision requires a new hypothesis: different customer, different scope, different form. Not "let's try harder at the same thing." A genuinely different test.

Invest means the survival signals are strong. The product is earning its place. An Invest decision isn't "keep going" — it's a commitment to increase attention, capacity, or ambition. Products in this category deserve more than maintenance. They deserve a bet.

How to run it

Bring the portfolio. For each product, run three questions drawn from the last three weeks:

Does it have a meaningful survival signal from customers — not habit, not KTLO usage, but genuine need?

Can the team sustain it for the next two quarters without it consuming capacity meant for something else?

Would leadership fund it if you pitched it fresh today — with no prior investment, no sunk cost, no existing sponsor?

Based on those answers, place it. The exercise doesn't take long. What takes long is the conversation that follows — because the placements will surface disagreements your team has been having silently for months.

The disagreements are the output. Not the placements.

The hard version: cross-functional portfolios

Running Stop / Pivot / Invest on a product your team owns entirely is the easy version.

The hard version is when the product crosses two organizations. Two teams. Two sets of objectives. Two sponsors with different incentives. The exercise works the same way — but it surfaces the question that was already there, unasked: who makes the kill call?

This is where the empowerment problem from two weeks ago becomes structural. It's not enough to have the data and the framework. Someone has to have the decision rights. In a cross-functional portfolio, that person often doesn't exist — or doesn't know they have the authority — until the exercise forces the question out into the open.

The product that nobody can Stop is usually the product that crosses an organizational boundary. The Stop / Pivot / Invest exercise is where that boundary becomes visible. Naming it is the first act of fixing it.

What changes when you run it

Not the framework. The organization.

Teams that run Stop / Pivot / Invest regularly start building the infrastructure that makes it possible: survival criteria set before products launch, signal routes for kill decisions, portfolio reviews designed to surface decisions rather than confirm strategy.

The dashboard stops lying — not because you built a better one, but because you agreed what surviving looks like before you started measuring. The meeting where nobody said "kill it" starts having someone who says it — not because they're braver, but because they have a category to put it in and a room that expects the answer. The delivery drag lifts, not because the team got faster, but because the undead got a formal ending.

This is the conversation I run inside organizations in the Survival Metrics workshop. The exercise takes an hour. The products that come out of it have often been on the roadmap for years. If you want to run this with your team — or you're not sure where to start — reply to this email. I read every response and I'll point you in the right direction.

The prompt

Take your product portfolio. Pick five products — the ones you're least certain about.

Run the three questions. Place each one in Stop, Pivot, or Invest.

The placements aren't the output. The disagreements are. The products your team can't agree how to classify are the ones carrying the kill-permission gap. Those are the ones that need a decision — not a better dashboard, not another quarter of data.

A decision. With a name on it and a date attached.

What came out of the exercise? Reply and tell me what you find.