Skip to main content

Dormant Problems

Some problems that exist in the marketplace are dormant. Dormant problems are those problems of which your customers are not aware, and to which they will be oblivious until you present them with a new way of doing things.

Before the advent of e-mail, few people or companies considered written communication to be inefficient or a problem. Yet imagine a company like Dell scrapping the use of e-mail and going back to using paper notes and memos for their internal communications. Not only would it be inconvenient, it would have a devastating impact on their bottom line. It was not apparent just how inefficient written communication had been until we started using e-mail. Inefficient written communication, therefore, was a dormant problem.

Dormant problems are a challenge for a product manager to uncover, as well. Facilitation is one tool a product manager can use to uncover dormant problems. You also have to persistently ask, "Why?" Putting yourself in your customer's shoes, via an ethnographic study, is also helpful.

Sometimes the most effective way to uncover dormant problems, however, is to use these methods after releasing a prototype. That way, prospective customers have a chance to experience a new way of doing things, which helps them become aware of the problems they faced all along.

Comments

Brandon said…
Slightly off topic but sometimes I wonder what the net productivity of email really is. Of course, there is SPAM. Then there is the occupational SPAM. If everyone had to send a memo there would be a lot less FYI emails... I know there is no going back but sometimes the technology that is suppose to help actually becomes the problem itself.

Agree on your main point though. Finding latent needs is job for a good PM.
Jossie said…
I really enjoyed the content on your blog about Product Design will be back very frequently! I actually have my own Product Design Exposed blog with all kinds of stuff in it. You�re welcome to com by

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Henry Ford's "Faster Horse" Quote

You may have heard the ( apocryphal ) Henry Ford quote: If I'd asked customers what they wanted, they would have said "a faster horse". Over at the On Product Management blog , Saeed gives his take on this infamous quote. He "hates" it, and gives some compelling reasons. Saeed is spot on in his explanations. Personally, I think the quote is great, but it's a matter of interpretation. The valid point of the quote is not that it's a bad idea to facilitate a conversation with your market to better understand it. The valid points are: You must ask the right questions to get valuable answers. You must interpret the answers thoughtfully - often outside their direct meaning - to glean reliable information. Asking questions is not always the best way to "listen" to your market. (E.g., sometimes pure observational studies are more reliable.) Nonetheless, I find the quote is helpful to combat "armchair product management" in the

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio