Tag Archives: data

Building a Product Owner – Existing Backlog

Product Owners – like great products – must be developed.  While some skills are innate, others must be learned and organizations tend to throw new Product Owners into the mix without adequate information. In this blog series, we have explored new product owners who are assigned to new products and those owning a system migration.  Now we are going to explore a new product owner who takes over an existing product with a robust product backlog.  In some respects, one might think this is the easiest of the three scenarios but it comes with its own set of challenges.  Here are some tips for how to get started.

1. Get to know your customers

The first step to get your arms around an existing backlog is to understand your current customers.  To do this, you need both

Backlog in Jira Agile

Backlog in Jira Agile

qualitative and quantitative information.  Data is always your friend.  How many customers do you have?  Are they profitable?  Are they the ideal customers that you want to attract?  Once you understand the numbers, now you need to actually talk to customers.  Schedule interviews with key customers – both happy ones and those that are frustrated.  Use your strong product management skills by asking open ended questions.  My favorite is “What keeps you up at night?”  Let your customers talk or complaint or suggest – wherever the conversation goes can be valuable.  Knowing who is buying your product is very important.

Sunsetting a product: Get Data

As a Product Manager, one of the efforts that we are often asked to consider is the decommissioning or sunsetting of a product or platform.  It is not always a fun task, but it is very important to the business.  This blog series is dedicated to the steps that a strong Product Manager needs to consider when researching this kind of issue.  The first and most important thing to do is to get data.

If ever there was a project that should NOT be executed based on gut feel, this is it.  You need data to make sure you make the most sunsetprudent decision possible.  There is no way to sunset a product without upsetting some aspects of your business, so this is not something that should be taken lightly.  What kind of data do you need?

Customer Analysis:

You need solid data from the financial and CRM systems of the company to answer the following questions:

  1. How many customers are impacted?
  2. How important are those customers?
  3. What other services have they purchased?
  4. What prices are they paying?
  5. What is their lifetime value?