Will Booth
Will Booth
Home

Will Booth

Senior Product Manager

All articles
Product Strategy·November 2025·4 min

The Art of the Kill: Why Great PMs Are Defined by What They Don't Ship

Shipping features is easy. Killing them takes courage. If your primary metric is volume of features delivered, you aren't managing a product — you're managing a factory.

AI Summary✦ Powered by Claude

In the world of product management, there is a dangerous seductive pull toward the "New." Released features and shipped code are praised, whilst roadmaps are treated like sacred texts. But if your primary metric for success is the volume of features delivered, you aren't managing a product; you're managing a factory.

Standout PMs don't just ship features. They kill them.

Shipping isn't the job. Shipping the right product is.

A great PM doesn't fall in love with the roadmap; they fall in love with the problem. They have the guts to look at a request or a polished prototype and say: This isn't solving it. This adds complexity. This doesn't matter.

The Fight for Existence

Every feature, every setting, and every UI element should have to fight to exist. In a world of infinite ideas and finite user attention, complexity is the silent killer of great UX. When we add without subtracting, we dilute the value of our core offering.

To maintain a high-performance product culture, I operate by one rule:

🚫

If you can't explain why it matters, we do not build it or release it.

The "What's the Point?" Test

I regularly ask stakeholders — whether they are from Engineering, Design, Leadership, or the client side — a simple question: "What is the point of this?" and "What are you trying to achieve?"

If the answer is "It's on the roadmap" or "Leadership asked for it," the conversation stops there. Those aren't reasons; those are echoes. A roadmap is a hypothesis, not a mandate. If we can't justify a feature's existence based on the value it provides to the person on the other side of the screen, it is waste.

Seeking the Human Reason

When I ask for the "why," I'm looking for the reason a real person would care. If you can't describe the moment of relief, joy, or efficiency a human being feels when using this feature, then the feature doesn't have a soul.

The Result

This one rule has prevented dozens of features that would have been built, but never were. It has caused friction and uncomfortable silences in Slack channels. But it is also the reason my products remain lean, intuitive, and effective.

By killing the mediocre, you create the oxygen necessary for the exceptional to breathe. Stop being a feature diplomat and start being a product gatekeeper. Your users will thank you for the things you didn't make them learn.

Thanks for reading.
—Will