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 […]
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 / 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?
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 / Business Analysis / Product Management / Software development
Posted on:
Product Owner Survival Camp
Product owners are likely to find themselves alone in the organizational wilderness. Their organizations expect them to connect the towers of long-term strategic planning with the frontiers of great new products. Iterative and incremental development of solutions can bring these two worlds together. There’s always a gap between strategy and […]
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 […]
Business Analysis / Ishikawa Diagram / Prioritization / Product Management / Requirements / Requirements gathering / Requirements Models
Posted on:
Why Do Products Fail? – Picking the Wrong User Goals
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 […]
Business Analysis / Ishikawa Diagram / Prioritization / Product Management / Requirements / Requirements Models
Posted on:
Why Do Products Fail? – Picking the Wrong Users
Exploring the reasons that a product might fail in the market is a useful way to triage and assess what you need to do to prevent the failure of your product. Instead of taking the “do these things” approach as a prescriptive recipe for product managers, I’m approaching the exact […]