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 / 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?
Product Management / Product Strategy
Posted on:
Customer Churn and SaaS
Software as a Service is not a one and done transactional offering. A product or business built on SaaS is built on the subscription model – recurring revenue is half of what drives the business (and valuation). The other half is the rate of growth of that recurring revenue. Customer […]
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 […]
Agile / Product Management
Posted on:
Agile Through a Matrix Lens
“Agile” is something most teams do wrong*, without realizing they’re doing it wrong. A good 2×2 matrix acts as a lens, helping to convert information into insight. Let’s apply this lens to agile as applied within a company, and see if it helps people decide to do things differently.