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 strategy. Understanding how problems are framed in your market is critical to developing a successful product strategy.
Continue reading Market Problem Framing Example
Taking agile, a process otherwise optimized for small, cross-functional, collaborative teams and making it work at scale is fascinating. You have to change some elements, and retain others, as you redefine the context. Being outcome driven, is one element you must retain – or even elevate in importance, or you fundamentally break the system of delivery
Continue reading Agile at Scale – Outcome Driven (or Broken)
Last month, Mike Smart of Egress Solutions and I gave a webinar for Pragmatic Marketing on product roadmapping when working inÂ agile environments. We had a great turnout of over 1500 people in the session – with not nearly enough time to answer all of the questions.
One attendee asked, “Please explain how a prioritized list of features is not a roadmap?”
A fantastic question, which we did not see in time to answer during the call.
Continue reading Features do not a Product Roadmap Make
You’ve got some shiny new segmentation data about prospective customers; how much they earn, where they are located, how old they are. How does that help you make decisions about your product? You know this information, but you don’t really know your audience, or why they might become your customers.
Continue reading You Don’t Know Jack (or Jill)
We hear a lot about building products which are “good enough” or “just barely good enough.” How do we know what “good enough” means for our customers? Â No one really tells us.
Continue reading Good Enough
Your product roadmap is a view of what you areÂ building right now, in the near future, and in the more distant future. Â Or is your roadmap a view ofÂ why you are building whatever you’re building right now, in the near future, and in the more distant future?
Your roadmap is both – but one is more important than the other – and product managers need to be able to view the roadmap both ways.
Continue reading Opposite Views of a Product Roadmap
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?
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