Theodore Levitt may have developed the whole product model to help companies compete more effectively with their products. We wrote about the whole product game based on Mr. Levitt’s work. Recently, I’ve been using a variant of this model as a way to view a product and upcoming roadmap items. It is a powerful way to share a perspective on your product with the rest of the team, and frame conversations about where best to invest.
Continue reading Classifying Market Problems
How can Theodore Levitt’s classic Whole Product approach help with defining a product roadmap? I’ve been revisiting his concepts and their use recently, thinking about how to revise them for some exercises I’ve been doing with product teams.
Continue reading Whole Product Game
Next up in the series on the root causes of product failure – products that fail because you have ignored the user’s level of experience. The first time someone uses your product, they don’t know anything about it. Did you design your interfaces for new users? After they’ve used it for a while, they get pretty good at using it. How much do you think they like being forced to take baby steps through a guided wizard now?
This article continues the series exploring the root causes of product failure. Even when you target the right users, and identify which of their problems are important to solve, you may still fail to solve the problems sufficiently.
Continue reading Why Do Products Fail? – Incomplete Solutions
Having an outside-in bias as a product manager is important – you need to understand how your customers (or your customer’s customers) would value capabilities you might build into your product. When running a workshop to collect that information, playing some “serious games” is a great way to get more and better information. We ran a few 20/20 Vision games last week, to great effect.
Continue reading 20/20 Vision – Innovation Game in Action
Continuing the series on root causes of product failure, this article looks at the impact of focusing on the wrong user goals. Even if you have picked the right users, you may have picked the wrong goals – creating a product your customers don’t really need, or solving problems that your customers don’t care about solving.
Continue reading Why Do Products Fail? – Picking the Wrong User Goals
Exploring the reasons that a product might fail in the market is a useful way to triage and assess what you need to do to prevent the failure of your product. Instead of taking the “do these things” approach as a prescriptive recipe for product managers, I’m approaching the exact same topic from the opposite direction. I was inspired in part to explore this approach when thinking about the Remember the Future innovation game. Instead of asking “What will the system have done?” in order to gain insights what it could be built to do, I’m asking “Why did your product fail?” in order to prevent the most likely causes of failure.
There are many reasons that a product might fail in the market. One of those reasons is that your product solves the wrong problems. There are many ways to solve the wrong problems. This article continues the series on sources of product failure, exploring the idea that your product may be trying to solve the wrong problems.
Continue reading Why Do Products Fail – Solving the Wrong Problems
Why do products fail? Trying to organize all of the reasons that your product might fail is a Herculean effort. Understanding how your product did, will, or might fail will help you focus on what you need to do next.
At this point in the product comparison series, you know who your customers are, which problems are important to them, and which products compete to solve those problems. It’s time to score the competing products and see how the solutions your product provides (or will provide) will stack up. This is the latest in a series on comparing products, jump back to the start of the series if you came here first, but hurry up :).
Continue reading Rating Your Competition – Comparing Products Part 7