Can one person be both product manager and product owner? With two people, where are the role boundaries? How should you think about it?
Agile / Product Management / Product Strategy / Requirements / UX
Posted on:
Business Analysis / Kano Analysis / Product Management / Requirements / Requirements Models
Posted on:
Encryption is not Binary
Data protection is not something that a product has or doesn’t have. A product has a degree of data protection. The question is, how much? The more important question is, is it enough?
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.
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 / 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 […]
Product Management / Product Strategy / Requirements / Requirements Models
Posted on:
Classifying Market Problems
Theodore Levitt may have developed the whole product model to help companies compete more effectively with their products. We wrote about the whole product game based on Mr. Levitt’s work. Recently, I’ve been using a variant of this model as a way to view a product and upcoming roadmap items. […]
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.