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.
Step 1: The mindset change
We cannot move forward on this journey without a changed mindset.
Once your mindset changes, everything on the outside will change along with it.
Myspace 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 ad banners. My favourite example is Blockbuster. 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 helps 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 everyone's 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 depending on 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.
Step 2: Finding zombies
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.
- The gut feeling of the product team outweighs all other factors. Your team is often aware of the troublesome features, processes or even products.
- Reach out to other teams (higher management, Sales, Marketing) to understand perspectives outside your core team. Do these teams avoid talking about the product or feature?
- Listen to your customers. Do they know about your portfolio synergy? Do they care? Keep your ears open for feedback from your target users.
- Check with your support team about which features customers seldom ask about, and when they do, it takes ages to get back to the customer.
These and many other signals can help you start thinking about a zombie.
Step 3: Evaluate
Once you have a list of potential zombies, it is time to evaluate them. Many factors can shape your evaluation; here are some of the top ones.
- Company strategy: Does the identified zombie fit the company strategy? Does your feature or process fit your product strategy? If not, you have zombies at your disposal. Google shut down Inbox as it did not suit the company strategy despite a positive response from users.
- Cannibalisation: Some features or products cannibalise others. Coca-Cola Zero Sugar cannibalised the downward spiral of Diet Coke. When Apple launched the iPhone, it cannibalised iPod sales.
- Not used anymore: Your feature or product may have worked very well in the past, yet users no longer use it. Consider whether you want to keep working for a small customer base. The Google toolbar became a zombie after most users switched to Chrome.
- Weaker roadmap: A weak roadmap forces teams to keep adding features to fill the bandwidth, so you add less value to solving the user's problem. It is often a sign of a zombie.
- Trust data: Trust the information you collect rather than biasing toward emotions. When you talk about discontinuing something, you will hear emotional sentences. Filtering them out is critical.
- Missed revenue projections, if backed with data, can help you identify whether you are dealing with a zombie.
Avoid getting biased while evaluating. Do not overlook the dependency product code may have on a feature, or whether the sales team uses a feature or product extensively in the sales pitch. Make sure you acknowledge all dependencies with your stakeholders.
Step 4: Killing a zombie
After a thorough evaluation, killing the zombies is where the real fun starts. Plan it the way you plan any other feature launch. Here are a few pointers.
- Reduce the visibility of your zombie feature or product first. Make sure you do not onboard new users onto your zombies.
- In some cases you may try to adapt the feature, process or product to make it relevant again. Avoid the trap of putting on plasters. Define a measure for a successful kill and follow it diligently.
- You will have to transition existing users to new alternatives. This can take longer depending on the domain and the product. The sunset will be slower in such cases, but keep the momentum going as a product team.
- Be mindful of the cost of killing zombies. Estimate it before you begin and agree on it with your stakeholders.
Company culture, domain and other macro-environmental factors will define the procedure that suits a particular product team.
Step 5: A successful kill
I believe the sunsetting of a product or feature is only successful when we learn from the experience.
Change is the end result of all true learning.
The sense of learning over loss is critical to the mindset change you need for your next zombie kill. You should feel good about it.
Overcommunicate. Often, miscommunication makes a correct zombie kill a nightmare. If you bring customers and users in earlier in the process, you will be surprised how pragmatic they are. You can see this again and again with companies like Slack, Google and Atlassian.
Most important of all, celebrate at the end. The sense of accomplishment needs to be felt by everyone involved. Celebrations pave the way for future iterations of the process, and eventually help change the mindset.
In conclusion
Create, maintain and destroy are the three pillars of any successful product or portfolio. Following the five-step approach of finding, evaluating and killing product zombies, with the right mindset and a robust success assessment, can result in a well-toned portfolio.
Killing zombies is challenging but not impossible. As humans, we are terrible at letting go of things. Companies like Yahoo, Nokia, BlackBerry, Kodak and Blockbuster are great examples of what happens when you befriend your product zombies and nourish them. Eventually, those zombies killed them. We should learn from such failures. Start small and try to make one successful zombie kill. You will be surprised by its effect on team culture.
Each product team and company has a different culture. Sharing your experience with others and offering help will aid culture change and reduce #ProductWaste.
