A heuristic is “an aid to learning, discovery, or problem-solving by experimental and especially trial-and-error methods.” There are a number of heuristics that product managers will find useful and powerful. Last week I talked about the “Mission-Critical Core/Context model” for product managers, and I’ve talked before about various other models and heuristics. In this post I start to drill into how they help you solve product management problems. Some of my favorites – because they give me the best insight – are:
These are all aids that help you reduce uncertainty, map a course through complexity, and give you more information about both your landscape and your response to the landscape. In fact, we can divide them up (roughly) into mapping heuristics and response heuristics (some, like prototyping and MVPs) fit in both categories).
Another way to look at these heuristics is that they are about exploring. Some are for broad exploring, getting a sense of “where is there a problem?” and some give you more focus: “OK, I’ve found a problem, can I solve it?”, and “Have I solved it?” For broad exploring you’re going to use things like “Get In The Van” and many of the other techniques that are described, for example, in the d.school bootleg (download). You will use the Five Whys. You might use prototypes in this phase as well, with the goal not of validating that your solution is good, but that there is a problem that needs a solution.
Once you’ve found a problem, then you use a set of heuristics for determining if you have the ability to create a solution, then to determine if your solution is effective and valuable.
Your host and author, Nils Davis, is a long-time product manager, consultant, trainer, and coach. He is the author of The Secret Product Manager Handbook, many blog posts, a series of video trainings on product management, and the occasional grilled pizza.
Please log in again. The login page will open in a new tab. After logging in you can close it and return to this page.