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.
Category Archives: Product Management
Why Do Products Fail?
Why do products fail? Trying to organize all of the reasons that your product might fail is a Herculean effort. Understanding how your product did, will, or might fail will help you focus on what you need to do next.
Read the rest of the article …
Posted in Ishikawa Diagram, Product Management
Tagged failed products, ishikawa, product failure, Product Management
80 Comments
Rating Your Competition – Comparing Products Part 7
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 :).
Know Your Competition – Comparing Products Part 6
You start with a point of view about what makes a minimum viable product. When your product launches, it is your customer’s point of view that matters. You must understand which problems your customers care about solving, and what solutions are available to your customers today. You need to understand your competition to make informed decisions about your product. This is the latest in a series on comparing products – jump back to the beginning of the series to catch up, we’ll wait.
Read the rest of the article …
Important Customers – Comparing Products Part 5
A good product is one that solves valuable market problems. To be successful in the market, a product needs to solve the problems that the right customers are willing to pay to solve. To know if those customers are willing to pay, you need to understand how they perceive your product relative to alternative solutions. If you’re new to the series, head back to the intro article on comparing products, and catch up with this article, where we look at pulling together the information about which customers are important.
Read the rest of the article …
Important Problems – Comparing Products Part 4
If you understand the important market problems, you can make a good product. If you understand how important each problem is, for each group of customers, you can make a great product. If you’re new to this series, go back and start at the first article, we’ll wait for you right here.
Market Problems – Comparing Products Part 3
Comparing products without an understanding of the important market problems by which to compare the products is a waste of time. This is the third in a series on comparing products - jump back to the introduction if you haven’t already read the previous articles. Go ahead, we’ll wait, then come back.
Who Are Your Customers – Comparing Products Part 2
The first step to comparing products is understanding your customers. This may seem counter-intuitive, but your product’s capabilities are meaningless unless you are comparing them from your customer’s point of view. This article is part 2 in a series on comparing products. Check out part 1, then continue with this article on the first steps of comparing products.
Compare Products Not Specs – Comparing Products Part 1
Recently, the gadget-reviewer crowd has caught on to something we’ve known for a long time. Comparing products is not about comparing specs, it is about comparing how well the products solve problems that customers will pay to solve. That begs the question – how should you compare products? Read on to see the product comparison technique I recommend.
Read the rest of the article …
Agile Estimation, Prediction, and Commitment
Your boss wants a commitment. You want to offer a prediction. Agile, you say, only allows you to estimate and predict – not to commit. ”Horse-hockey!” your boss exclaims, “I want one throat to choke, and it will be yours if you don’t make a commitment and meet it.” There’s a way to keep yourself off the corporate gallows – estimate, predict, and commit – using agile principles.
This is an article about agile product management and release planning.
Posted in Agile, Business Analysis, Prioritization, Process Improvement, Product Management, Project Management, ROI, Requirements, Software development, User Stories
Tagged agile estimation, agile prediction, agile release planning, cone of uncertainty, project planning, release planning
101 Comments
Latest Articles
Comments on all Articles
