The Meeting Where Nobody Says "Kill It"

Every zombie product has a meeting where it should have died.

A room where someone has the data. Someone has the instinct. Someone has the track record to name the thing. The numbers are visible. The trend is clear.

And nobody says it.

The teams I work with describe it as being on pins and needles around leadership. Not because they're timid — because they've learned that certain signals cost more to send than they're worth.

I had the data that said a product should die. I also had a stakeholder I thought would carry the strategic argument — so I showed up with numbers and nothing else. They didn't carry it. In a room with an exec sponsor, negativity with no motion is dead on arrival. The product got quietly deprioritized over the next quarter. No clean decision. Just a slow fade I could have stopped if I'd built the case myself.

The problem isn't courage. It's that the cost of saying "kill it" exceeds the cost of maintaining silence.

Why nobody says it

At Agile 2024, I asked a room of 40 product leaders which part of a survival metrics practice they found hardest. Most chose political safety — not strategy, not data. The permission to act.

Three mechanisms explain why the meeting happens and nothing gets said.

The emotional label. Raising a concern about a zombie product gets coded as resistance, not analysis. A product manager told me she'd learned to be careful of what she said "because I'll be charged with being emotional." The kill signal is real. But sending it costs her credibility. So she doesn't.

The arbitrary veto. Teams don't say "kill it" because they've watched leadership undo things without explanation. "Higher up leadership can grind everything to a halt on a whim" — this is learned helplessness, not laziness. When the last five kill signals got reversed or ignored, the rational response is to stop sending them. It's not fear. It's experience.

Not in the room. Sometimes the problem isn't political safety at all — it's structural. The PM who has the data isn't invited to the financial meeting where the decision could be made. A product leader at Fidelity asked it plainly: "How do you influence when you aren't invited to the financial meetings?" The signal exists. It has nowhere to go.

The engineer is watching too.

The engineer who built the feature knows it's a zombie. They're maintaining it. They're not saying anything either — for the same reasons.

Once an engineer stops trusting that their feedback will be received, they stop sending it. The most valuable signal a PM has — honest resistance from the people closest to the work — goes quiet. You lose the pushback. You lose the early warning. You lose the one voice that has the most to gain by telling you the truth.

The team's silence isn't a culture problem. It's a signal problem. And the signal stopped because nobody knew where it was supposed to go.

The kill-permission gap

Empowerment, here, isn't about confidence. It isn't a culture initiative or a communication training.

It's a mechanism.

Two things make it safe to say "kill it":

Pre-agreed survival criteria. Before a product launches, agree on what "failing" looks like. Not as a performance review — as a navigation tool. When the kill signal is measured against criteria set before the political stakes arrived, it becomes a business recommendation rather than a personal judgment. Nobody is calling for anyone's failure. They're calling against a shared standard.

A named signal route. Who receives the kill signal? If the PM isn't in the financial meeting, the signal needs a path to someone who is. This isn't hierarchy hacking. It's infrastructure. The signal exists. Build the pipe.

Most organizations have neither. Survival criteria get set retrospectively, after the product has already become a zombie. Signal routes aren't named until there's a crisis. And so the meeting happens, the data sits there, and nobody says the actual thing.

What empowerment actually looks like here

Not "be brave enough to say hard things."

That puts the burden on the person with the least power in the room.

Empowerment means the VP in that meeting opens the floor for kill signals — explicitly, before anyone has to calculate the political cost. It means survival criteria exist before the review, so the data speaks rather than the person. It means the double bind — work within the culture while trying to change it — has at least one crack of structural light.

Zombie products don't survive because teams lack data or courage. They survive because the org has no legitimate mechanism for the kill signal to become a business decision instead of a political one.

Whether you're the VP who could open that floor, or the PM sitting in that meeting running the numbers in your head — the question is the same: what would need to be true for someone to say it safely?

The prompt

Think about the last meeting where you knew something should be killed and nobody said it. Not a hypothetical. A real one.

What would have needed to be true for the kill signal to be safe? Pre-agreed criteria? A named receiver? The VP explicitly opening the floor?

That gap — between the signal that exists and the safety to send it — is your kill-permission gap. It's the most expensive silence on your roadmap.

What does your kill-permission gap look like right now?