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 strategy. Understanding how problems are framed in your market is critical to developing a successful product strategy.
Continue reading Market Problem Framing Example
Understanding your users is critical to developing good products.Â A “complete” understanding is sometimes required, and always comes at a cost.Â A contextualized understanding is valuable but less so, and costly but less so.Â Even a shallow understanding of your users provides value by preventing some dysfunctional behaviors.Â Â You do not always need to develop personasÂ before developing products.
Continue reading Progressively Elaborated Users
You know you’re a product manager when this image causes more than a chuckle. A few random thoughts inspired by this Rorschach test of product management concepts from sunk cost fallacy to intentionality.
Continue reading Product Management Synapses
The pop-culture concept of a silver bullet – a simple solution to a hard problem – is a dangerous idea. Â It can be used to over-promise, and doom a team to under-delivery. Â When an executive, too far removed from what makes creating productsÂ hard thinks of “agile” as a silver bullet it becomes difficult to manage expectations.
Continue reading The Potential of Agile
Taking agile, a process otherwise optimized for small, cross-functional, collaborative teams and making it work at scale is fascinating. You have to change some elements, and retain others, as you redefine the context. Being outcome driven, is one element you must retain – or even elevate in importance, or you fundamentally break the system of delivery
Continue reading Agile at Scale – Outcome Driven (or Broken)
Assumptions are interesting things – we all make them all the time, and we rarely acknowledge that we’re doing it. Â When it comes to developing a product strategy – or even making decisions about how best to create a product, one of these assumptions is likely to be what causes us to fail. Â We can, however, reduce the chance of that happening.
Continue reading Playing Whack-A-Mole With Risk
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 there yet, these may sound like platitudes or empty words. Â I know many people who want to switch their rolesÂ from “do these things” to “solve these problems.” Â They have to change their organizations. Â This example may help get the point across.
Continue reading Outside-In User Story Example
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 that go with it. Â Solving for bothÂ the outside-in needs andÂ the inside-out goalsÂ is critical.
Continue reading Minimum Valuable Problem
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?
Continue reading Professional Services and Improving Your Product
Product owners and product managers. Â Two roles, often done by one person. Â Together, the productÂ people need to take an organization’s strategy, figure out the appropriate product strategy, and convert that into actionable work for the delivery teams to create the right product. Â What does the product manager own, and for what is the product owner responsible?
Continue reading Product Owner Manager – Alone Together