post

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! 🎉

Successful product management in companies where it’s least understood

Measuring critical user journeys – Javier Andrés Bargas-Avila (UX Director, Google)

A new way to look at applied experiments

Product survey findings: Only 15% of users are embracing AI features 

Building high-performing product teams: The PDLC approach

Footer About

Footer Contribute

Footer Get Involved

Footer Links

Mind the Product

Guest Post

Overcoming the 20% feature usage challenge

Product Management

Three product leaders to learn from at #mtpcon inside Pendomonium

A passionate product leader with a holistic product management experience in B2B2C products with a leadership purpose to create amazing products that bring positive change. Specialising in AI product management, he likes building strong working relationships with cross-functional teams distributed across the globe. With a particular interest in mentoring would-be product managers/owners, he enjoys working alongside founders and helping startups in their seed-development-growth stages.

Swanand Marulkar

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&#8217;t functioning well. This article is an overview of a five-step approach, a trigger list, that a product team can refer to identify and kill such non-functioning product zombies.
Once we acknowledge the existence of such non-working elements within our product or portfolio, we must diligently get rid of them. The list of zombies we have is often just the tip of the iceberg. We seldom discuss discontinuing a feature/product as passionately as creating new ones. Proactively identifying and killing the product zombies is as essential as incepting new ones.
Each step below deserves a dedicated article to cover the depth and breadth of this topic. Still, here is an overview for getting you started.
<h1>Why call it zombies?</h1>
The sense of achievement is infused very deep into our DNA. Unless we think of removing or discontinuing something as an accomplishment, we will not feel passionate about it. &#8220;Killing product zombies&#8221; is like putting a gamification hat on, making the process of sunsetting non-working features and products more satisfying.
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.
<h1>Step 1: The mindset change</h1>
We cannot move forward on this journey without a changed mindset.
&#8220;Once your mindset changes, everything on the outside will change along with it.&#8221; – Steve Maraboli.
<a href="https://en.wikipedia.org/wiki/Myspace">Myspace</a> is an excellent example of how ignoring product zombies resulted in losing over one million users per month. Instead of optimising the user experience, driving ad revenue became a top priority, and the site was quickly saturated with many ad banners. My favourite one is <a href="https://en.wikipedia.org/wiki/Blockbuster_LLC">Blockbuster</a>. Blockbuster was too focused on the profits it was raking in from its video stores. They ignored all signs of a zombie, which eventually destroyed the company.
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.
Concept killing will help the product teams not to invest too much, and killing a zombie, if identified, becomes a straightforward step. This means we are challenging ideas at the design stage, listening to everyones&#8217; opinion irrespective of their experience or the product life cycle stage. Creating an environment where the product team can express their views openly is essential for a successful zombie kill.
Though the nitty-gritty details of killing a zombie differ slightly considering whether you are killing a feature, process, or established product, the fundamental mindset is the same. Ensure you find and evaluate zombies objectively at every level.
<a href="https://www.mindtheproduct.com/the-mindset-that-kills-product-thinking-by-jeff-patton/" target="_blank" rel="noopener">Find out more about the mindset that kills product thinking.</a>
<h1>Step 2: Finding zombies</h1>
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.
<ul>
<li>The gut feeling of the product team outweighs all other factors. Your team is often aware of the product&#8217;s troublesome features/process or even the product itself.</li>
<li>Reach out to other teams (e.g. higher management, Sales and Marketing) you work with to understand perspectives outside your core team. Do these teams avoid talking about the product/feature?</li>
<li>Listen to your customers. Do your customers know about your portfolio synergy? Do they care about knowing? Keep your ears always open for feedback from your target users.</li>
<li>Check with your support team about which features/products customers seldom question, and when they do, it takes ages to get back to the customer.</li>
</ul>
These and many other aspects can help you start thinking about a zombie.
<h1>Step 3: Evaluate</h1>
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.
<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. Google shut down <a href="https://en.wikipedia.org/wiki/Inbox_by_Gmail">Inbox</a> as it did not suit the company strategy despite a positive response from the users.</li>
<li>Cannibalisation: Some features or products cannibalise others. Identify if that is the case for your zombie list. Coca-Cola Zero sugar cannibalised the downward spiral of <a href="https://en.wikipedia.org/wiki/Diet_Coke">Diet Coke</a> a few years back. When Apple launched the iPhone, it cannibalised <a href="https://en.wikipedia.org/wiki/IPod">iPod</a> sales. Eventually, Apple terminated the new product development in 2019.</li>
<li>Not used anymore: Evaluate if your feature or product worked very well in the past; however, users are not using it. You should consider if you want to discontinue working for a small customer base. Entertainment companies pivoted away from CDs and cassettes over the period due to technology and user behaviour. Another example is the sunset of <a href="https://en.wikipedia.org/wiki/Google_Toolbar">Google toolbar</a>, which became a zombie after most users switched to Chrome.</li>
<li>Weaker roadmap: This forces teams to keep adding features to fill the bandwidth. In the end, you add less value to solve the user&#8217;s problem. A weaker roadmap is often a sign of a zombie.</li>
<li>Trust data: Trusting the information you collect is essential rather than a bias toward emotions. When you talk about discontinuing something, you will often hear emotional sentences; filtering them out is critical.</li>
<li>If backed with data, missed revenue projections can help you identify if you are dealing with a zombie.</li>
</ul>
Avoid getting biased while evaluating. Do not overlook the dependency product code may have on a feature. Or if the sales team extensively uses a feature/product in the sales pitch. Make sure you acknowledge all dependencies with your stakeholders.
<a href="https://www.mindtheproduct.com/managing-misaligned-stakeholders-by-rich-mironov/" target="_blank" rel="noopener">Discover more insights on managing misaligned stakeholders. </a>
<h1>Step 4: Killing a zombie</h1>
After a thorough evaluation, killing the zombies is where the real fun starts. Make sure you plan similar to what you do to deploy any other feature. Here are a few pointers:
<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. 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>
Many more factors like the company culture, domain, and other macro-environmental factors will define the procedure that suits a particular product team.
<h1>Step 5: Successful kill</h1>
I believe the sunsetting of the product or feature is only successful when we learn from the experience.
&#8220;Change is the end result of all true learning.&#8221; ― Leo Buscaglia.
The sense of learning over the loss is critical to having a successful mindset change for your next zombie kill. You should feel good about it.
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.
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.
<h1>In conclusion</h1>
Create, maintain, and destroy are the three pillars of any successful product/portfolio. Following the above five-step approach of finding-evaluating-killing product zombies with a great mindset and robust success assessment can result in a well-toned product/portfolio.
Killing zombies is challenging but not impossible. As humans, we are terrible at letting go of things. Many companies like Yahoo, Nokia, Blackberry, Kodak, and Blockbuster are great examples of what happens when you befriend your product zombies and nourish them. Eventually, these zombies killed them! We should learn from such failed products/portfolios. Start small and try to make one successful zombie kill. You will be surprised to see its effect on team culture.
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.
Discover more content on <a href="https://www.mindtheproduct.com/category/product-strategy/" target="_blank" rel="noopener">Product strategy</a>. Find out more about what <a href="https://www.linkedin.com/in/swanandmarulkar/" target="_blank" rel="noopener">Swanand Marulkar</a> is up to at <a href="https://www.mindtheproduct.com/producttank/Heidelberg" target="_blank" rel="noopener">ProductTank Heidelberg</a>.
<div class="g g-21"><div class="g-single a-170"><a class="gofollow" data-track="MTcwLDIxLDEsNjA=" href="https://www.pendo.io/pendomonium/"><img decoding="async" src="https://www.mindtheproduct.com/wp-content/uploads/2024/06/MTP-Footer_ad.png" /></a></div></div>

Killing product zombies: a five-step approach

Swanand Marulkar

Comments

Read next