post

Footer About

Footer Contribute

Footer Get Involved

Footer Links

Mind the Product

mission statement

Deep dive: Crafting your product vision and mission

Podcast

Connecting fans to creators at Spotify (Dariusz Dziuk, Product Lead, Spotify)

B2B product management

Artificial Intelligence (AI) & Machine Learning (ML)

Building Product Teams

Business Strategy

Data Driven Product Management

Digital Transformation

Diversity and Inclusion

Minimum Viable Product

OKRs

Prioritisation

Product Design

Product Research

Product Development Process

Product Ethics

Product Discovery

Product Leadership

Product Management Career

Product Strategy

Stakeholder Management

🌎 <a href="https://www.mindtheproduct.com/world-product-day/" style="color:#FFFFFF;text-decoration:underline;">Happy World Product Day!</a> Be sure to celebrate product, yourself, and your peers today! 🎉

Join us at #mtpcon London in 2025 – mark your calendars

How Google makes AI work at Enterprise scale – Miku Jha (Director, AI/ML and Generative AI, Google Cloud)

5 ways to invent and simplify as an AI/ML product manager

Why teams often struggle with OKRs: A conversation with Jeff Gothelf

Building your own user experience and software stack: This week’s product news

Louron serves as the Editor at Mind the Product, bringing nearly a decade of experience in editorial positions across business and technology publications. For any editorial inquiries, you can connect with him on LinkedIn or Twitter.

Louron Pratt

<p><span style="font-style: italic;">As product people, we all have been practising building the right products rightly, yet if we look around, we find features, processes, and products that aren’t functioning well. In this Sunday Rewind, we look back to when product leader </span><span style="text-decoration: underline; font-style: italic;"><a href="https://www.linkedin.com/in/swanandmarulkar/" target="_blank" rel="noopener">Swanand Marulkar</a></span><span style="font-style: italic;"> gave us an overview of a five-step approach to tackle this issue. Read on for a recap of what advice he gave. </span></p>
<hr />
<p>Zombies are mythical creatures that eat our brains. They are tough to kill, and they drag us down. Product zombies are no different except that they very much exist. Killing them is tricky unless you change your thinking.</p>
<h2>Step 1: The mindset change</h2>
<p>Having a mentality of outcome rather than output is critical when you discontinue a feature, process or product. Instead of thinking about what we are losing, think about what we will gain. Thinking about the success matrix, failure criteria and challenging ourselves is critical.</p>
<h2>Step 2: Finding zombies</h2>
<p>Once you understand the importance of killing product zombies, the next challenge is to find them. Some of the prominent areas where you can start your search are listed below.</p>
<ul>
<li>The gut feeling of the product team outweighs all other factors</li>
<li>Reach out to other teams (e.g. higher management, Sales and Marketing) you work with to understand perspectives outside your core team</li>
<li>Listen to your customers</li>
<li>Check with your support team about which features/products customers seldom question</li>
</ul>
<h2>Step 3: Evaluate</h2>
<p>Once you have a list of potential zombies, it is time to evaluate them. Many factors can define your evaluation results; here are some top ones.</p>
<ul>
<li>Company Strategy: Does identified zombie product fit into the company strategy? Or does your feature/process fit into your product strategy? If not, you have zombies at your disposal.</li>
<li>Cannibalisation: Some features or products cannibalise others. Identify if that is the case for your zombie list.</li>
<li>Not used anymore: Evaluate if your feature or product worked very well in the past; however, users need to start using it.</li>
<li>Weaker roadmap: This forces teams to keep adding features to fill the bandwidth.</li>
<li>Trust data: Trusting the information you collect is essential rather than a bias toward emotions.</li>
<li>If backed with data, missed revenue projections can help you identify if you are dealing with a zombie.</li>
</ul>
<h2>Step 4: Killing a zombie</h2>
<p>After a thorough evaluation, killing the zombies is where the real fun starts. Make sure you plan similarly to what you do to deploy any other feature. Here are a few pointers:</p>
<ul>
<li>The first step is to reduce the visibility of your zombie feature/product. Make sure you do not onboard new users on your zombies.</li>
<li>In some cases, you have to adopt the feature, process, or product to make it relevant again.</li>
<li>However, you should avoid the trap of putting the plasters. Define a measure for a successful kill and follow diligently.</li>
<li>You will have to transition your existing users to new alternatives. This duration could be longer depending on the domain and the product. The sunset will be slower in such cases, but you have to keep the momentum going as a product team.</li>
<li>Be mindful of the cost of killing zombies. Estimate it before you begin the process and agree with your stakeholders.</li>
</ul>
<h2>Step 5: Successful kill</h2>
<p>Overcommunicate. Often, miscommunication makes a correct zombie kill a nightmare. If you onboard customers and users earlier in your zombie killing process, you will be surprised to see them being more pragmatic than you believed. You can see this again and again with companies like Slack, Google, and Atlassian.</p>
<p>The most important thing is to celebrate at the end. The sense of accomplishment needs to be felt by everyone involved. Celebrations will pave the way for future iterations of such a process, eventually helping change the mindset.</p>
<p>Each product team and company has a different culture. Sharing your experience with others and offering help will aid change the culture and reducing #ProductWaste.</p>
<p>Read<span style="text-decoration: underline;"><a href="https://www.mindtheproduct.com/killing-product-zombies-a-five-step-approach/" target="_blank" rel="noopener"> Killing product zombies &#8211; a five-step approach</a></span> in full, or delve into other articles in our <span style="text-decoration: underline;"><a href="https://www.mindtheproduct.com/tag/sunday-rewind/" target="_blank" rel="noopener">Sunday Rewind</a></span> series.</p>

core/freeform

Reduce risk, fail faster: Experimenting across the product development lifecycle

Experiment like a boss by Merissa Silk

How to find out what your customers want by Janet Bumpas

Why does my product suck? by Jen Dante

Driving customer adoption and retention as a product manager by Karen Adie

Mastering the art of the big bet by Alice Newton Rex

The magic of thinking big by Lenny Rachitsky

Making magic with balanced teams by Becki Hyde

Tools for agile product teams by Gavan Moule

Building Products for Bharat by Arpit Maheshwari and Smriti Pant

SUNDAY REWIND: Killing product zombies – a five-step approach

ProductTank Pune

ProductTank Kraków

ProductTank Cardiff

ProductTank Bangalore

ProductTank Mumbai

ProductTank Johannesburg

ProductTank Tauranga

ProductTank Bielefeld

ProductTank Auckland

ProductTank Vilnius

ProductTank Timisoara

ProductTank Stockholm

ProductTank München

ProductTank Düsseldorf

ProductTank Birmingham

ProductTank Norwich

ProductTank Heidelberg

ProductTank Malmö

ProductTank Amsterdam

ProductTank Barcelona

ProductTank Newcastle Upon Tyne

ProductTank London

ProductTank Curitiba

ProductTank Perth

ProductTank Málaga

ProductTank Buenos Aires

ProductTank Tokyo

ProductTank Braunschweig

ProductTank Edinburgh

ProductTank Pittsburgh

ProductTank Dubai

ProductTank Vienna

ProductTank Bristol

ProductTank Washington

ProductTank Valencia

ProductTank Raleigh

ProductTank Brno

ProductTank Paris

ProductTank Orlando

ProductTank Montréal

ProductTank Bangkok

ProductTank San Diego

ProductTank Hong Kong

ProductTank Charlotte

ProductTank Exeter

ProductTank Manchester

SUNDAY REWIND: Killing product zombies – a five-step approach

Louron Pratt

Read more

Comments