Helping teams to shift from a task-focus to writing user stories requires a different approach than simply introducing user stories as a new tool. You have to adapt the existing practices, by changing how teams think about and discuss the work they do. “Change from…” is different for people than […]
Agile / Product Management / User Stories
Posted on:
How To Make Your Product Special
When evaluating a product, a customer may see the product as special, adequate, inadequate, or awful. What is uncomfortable for product teams is they have no control over how the customer sees the product. They only have influence. What teams need to learn is how to approach creating the product […]
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 […]
Personas / Product Management / UX
Posted on:
Progressively Elaborated Users
You may not need a persona right now. But you absolutely must be user-centric. Explore a pragmatic approach to understanding your users – particularly when scaling agile or transforming from waterfall.
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.
Business Analysis / Product Management / Requirements / Requirements Models / User Stories
Posted on:
Outside-In User Story Example
Being “outside-in”, “outcome-based”, and “market-driven” is particularly important for creating successful products. The problem is that just saying the words is not enough to help someone shift their thinking. For those of us who are already thinking this way, the phrases become touchstones or short-hand. For folks who are not […]
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?
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.