Wrapping up the your product failed because you didn’t enable your users to realize value branch of¬†the root causes of product failure, is this article on the context in which your user is using your product. ¬†If you ignore your user’s context, they won’t be able to realize the value you provide – or won’t be interested in solving those particular problems at that particular time.
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.
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.
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.
Read the rest of the article …