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
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
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 Churn is the loss of existing customers and the slope that makes growing a subscription business an uphill climb.
Continue reading Customer Churn and SaaS
Fundamentally, product management requires you to assess, synthesize, and prioritize the needs which drive the creation of your product in the context of three main objectives: desirability, viability, and feasibility. While laudable, these objectives are too abstract to be actionable. That’s where the five lenses come in (I could not resist the Buzzfeed-styled title).
Continue reading You Won’t Believe What These Five Lenses Can Show You About Your Product
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, “Please explain how a prioritized list of features is not a roadmap?”
A fantastic question, which we did not see in time to answer during the call.
Continue reading Features do not a Product Roadmap Make
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.
Continue reading Good Enough
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. It is a powerful way to share a perspective on your product with the rest of the team, and frame conversations about where best to invest.
Continue reading Classifying Market Problems
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.
Continue reading Whole Product Game
Are product managers really involved in strategic discussions, or are we just order takers? Adrienne Tan has poked the beehive and started a great discussion with this article. Joining in from here, hopefully adding folks to the conversation. Check it out, and chime in here or on the brainmates blog.
At this point in the product comparison series, you know who your customers are, which problems are important to them, and which products compete to solve those problems. It’s time to score the competing products and see how the solutions your product provides (or will provide) will stack up. This is the latest in a series on comparing products, jump back to the start of the series if you came here first, but hurry up :).
Continue reading Rating Your Competition – Comparing Products Part 7