As Steven Haines first told me, “strategy first, roadmap second.” There is a step between the two – deciding which problems you will focus on solving with your product. Strategy defines the context for product strategy, and your product roadmap is a planning (and communication) tool for executing your product […]
Business Analysis / Communication / Product Management / Requirements / Requirements gathering
Posted on:
Minimum Valuable Problem
Defining and building a good minimum viable product is much harder than it sounds. Finding that “one thing” you can do, which people want, is really about a lot more than picking one thing. It is a combination of solving the minimum valuable problem and all of the other things […]
Business Analysis / Interviews / Product Management / Requirements / Requirements gathering
Posted on:
Professional Services and Improving Your Product
How do you work with professional services, consulting, field engineers, etc. to make your product better? Do you just treat their inputs as yet another channel for feature requests, or do you engage them as an incredibly potent market-sensing capability?
Business Analysis / Interviews / Product Management / Requirements / Requirements gathering
Posted on:
Why Not What – An Example
Forbes quoted Steve Jobs as saying “I’m as proud of what we don’t do as I am of what we do.” This is a really enlightened perspective – and a way to enforce focus from the top down. Before you can drive a “this goal is more important than that […]
Agile / Communication / Prioritization / Product Management / Product Strategy / Requirements gathering / Software development
Posted on:
Whole Product Game
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.
Interaction design / Interviews / Prioritization / Product Management / Requirements / Requirements gathering / Uncategorized / UX
Posted on:
20/20 Vision – Innovation Game in Action
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 […]
Business Analysis / Ishikawa Diagram / Prioritization / Product Management / Requirements / Requirements gathering / Requirements Models
Posted on:
Why Do Products Fail? – Picking the Wrong User Goals
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 […]
Prioritization / Product Management / Requirements / Requirements gathering
Posted on:
Important Problems – Comparing Products Part 4
If you understand the important market problems, you can make a good product. If you understand how important each problem is, for each group of customers, you can make a great product. If you’re new to this series, go back and start at the first article, we’ll wait for you […]
Product Management / Requirements / Requirements gathering
Posted on:
Market Problems – Comparing Products Part 3
Comparing products without an understanding of the important market problems by which to compare the products is a waste of time. This is the third in a series on comparing products – jump back to the introduction if you haven’t already read the previous articles. Go ahead, we’ll wait, then […]