Is Your Product Strategy Still Working? Three Signs It's Dead

Strategies don't announce when they've stopped working. They don't send a notification. They don't turn red on your dashboard.

They just quietly become irrelevant while everyone keeps executing against them.

I call this a dead strategy — a strategy that's still in your decks, still on your roadmap, still driving decisions, but no longer connected to reality. And most product teams are executing against at least one right now.

Three Signs Your Strategy Is Dead

• The strategy produces debates instead of decisions. A living strategy makes decisions easier. When a new opportunity appears, the team knows whether to pursue it. A dead strategy encounters a new situation and nobody knows what to do — the assumptions no longer match reality. So every decision becomes a debate.
• The market has changed and the strategy hasn't. Your biggest competitor launched a new product. A regulatory change shifted customer priorities. An economic downturn changed your buyer's budget. Your strategy was built for a world that no longer exists. But nobody updated it because updating feels like admitting the last six months were pointed in the wrong direction.
• Teams are working around the strategy. The surest sign. Teams start ignoring it — not publicly, that would require confrontation. Quietly. They make decisions that don't align with the strategy but produce better results. The strategy is still official. It's just not relevant.

Why Dead Strategies Persist

If the strategy is dead, why doesn't someone say so?

• Sunk cost. The organization invested months building it. Presentations were made. Teams were aligned. OKRs were set. Declaring the strategy dead means admitting all of that work was based on assumptions that turned out wrong.
• No mechanism for review. Most organizations have a process for creating strategy. Almost none have a process for killing it. There's no calendar invite for "stress-test whether our strategy is still alive." So it persists by default, not by merit.
• Fear of the vacuum. If you kill the current strategy, you need a new one. Creating a new strategy means new choices, new sacrifices, new commitments. It's easier to keep executing the old one than to face the uncertainty of building something new.

This is the survival metrics problem applied to strategy itself. Without tripwires that tell you when a strategy should die, the default state is "keep going." And the default state is almost always wrong.

Alive vs. Dead: The Contrast

• Alive: A new customer request comes in. The team evaluates it against the strategy and gets a clear answer in 5 minutes. Dead: Every request triggers a 45-minute debate because nobody's sure what the strategy says about this situation.
• Alive: The strategy was updated 6 weeks ago based on Q3 results. Dead: It hasn't been touched since the January offsite.
• Alive: Teams can explain how their current sprint connects to strategic priorities. Dead: Teams can't remember the priorities without looking them up.

If the dead column sounds more familiar, you know what you're dealing with.

How to Kill a Dead Strategy (And Build a Live One)

You don't need to start from scratch. You need three things:

• A formal review. Get the people who built the strategy in a room. List the assumptions it was built on. Test each one: Is this still true? What's changed? The broken assumptions are the reasons the strategy died. Name them explicitly.
• A decision, not a discussion. Based on the review, decide: is this strategy fixable or replaceable? If the core thesis is still sound but the tactics are wrong, update the tactics. If the core thesis is dead, you need a new strategy. Don't split the difference.
• Survival metrics for the new strategy. Whatever you build next, define what would kill it upfront. "If market share drops below X by Q2..." "If our top 3 customers haven't adopted by month 6..." These tripwires ensure the next strategy can die a healthy death when it needs to.

The Quarterly Gut-Check

The real fix is preventive. Don't wait for a strategy to die — check on it regularly.

Every quarter, run a 30-minute review with three questions:

• What assumptions did our strategy make that might no longer be true?
• What decisions did the strategy make easier this quarter? What decisions did it make harder?
• If we were starting over today with what we now know, would we write the same strategy?

If the answer to that third question is no, you have a dead strategy. The sooner you acknowledge it, the less time and money you spend executing against a ghost.

Because dead strategies don't cost you nothing. They cost you everything — in resources directed at wrong targets, in decisions made with outdated assumptions, and in teams losing faith in the planning process itself.

Not sure if your strategy is still alive?

In my Survival Metrics: Roadmap Review Reset workshop, product teams define the tripwires that tell you when to stop, pivot, or invest — including tripwires for the strategy itself. The output: a decision framework that keeps your strategy alive by design, not by default.

Book a Clarity Call — 30 minutes, no pitch. Just clarity on whether your strategy needs a reset.

Not ready for a call? Subscribe to The Adam Thomas for frameworks and honest takes on product leadership, delivered biweekly.