Most people and teams conflate prioritizing and sequencing of work. Prioritization is the process of deciding what is important to do, and sequencing is deciding what order to do it in. Shaping a product strategy involves both. First you decide which problems are important to solve. Then you decide which […]
Business Analysis / Kano Analysis / Marketing / Prioritization / Product Management / Product Strategy / Requirements / Requirements gathering / Requirements Models
Posted on:
Market Problem Framing Example
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 […]
Agile / Prioritization / Product Management / Product Strategy / Project Management / Requirements / Requirements Models / Software development / User Stories
Posted on:
Agile at Scale – Outcome Driven (or Broken)
An organization attempting to use agile processes at scale must be outcome driven – without intentionality the system of delivery breaks down and operates no better than waterfall.
Agile / Prioritization / Product Management / Product Strategy / Software development
Posted on:
Features do not a Product Roadmap Make
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, […]
Kano Analysis / Personas / Prioritization / Product Management / Requirements / Requirements Models
Posted on:
You Don’t Know Jack (or Jill)
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.
Agile / Kano Analysis / Prioritization / Product Management / Product Strategy / Requirements / Requirements Models / Software development
Posted on:
Good Enough
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.
Communication / Kano Analysis / Prioritization / Product Management / Requirements / Requirements Models / Software development
Posted on:
Opposite Views of a Product Roadmap
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 […]
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 / Interface Design / Ishikawa Diagram / Kano Analysis / Prioritization / Product Management / Requirements / Requirements Models / ROI / Software development / UX
Posted on:
Why Do Products Fail? – Forgetting that Users Learn
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 […]