Tag Archives: sunset

Agile and Product Mgmt – Year in Review

I committed this year to write 52 blogs and I did it!  There are 16 on my previous employers website and 36 on www.runyanconsulting.com.  As I look back and review and reflect on the posts, here are my favorites.

Product Management Blogs

I am very passionate about Product Management and I think it is sometimes an undervalued skill set.  Where I have a chance, I always try to share the strategic and practical benefits that come from having great product management resources.  This year, I wrote a five part series about how to Launch a Product and recently completed a 3 part series on how to sunset or decommission a product.

Image Source: http://www.greenbiz.com/

Image Source: http://www.greenbiz.com/

 

Agile Blogs

I am equally passionate about Agile because I have seen how it can improve people’s job satisfaction and raise the level of productivity and effectiveness for the whole organization.  This category was harder to choose my favorites, so I came up with four.  First, there was a series on creating an Agile Culture and what it really means for management.  This series generated some controversy, which I love because it means we are talking about important things.  Next, I am surprised that many organizations are not familiar with Fist of Five.  We use the Agile technique all the time and it is a difference maker in driving productive conversations.  Many organizations also  struggle with how to incorporate Agile into the day-to-day business, so I offered three options for incorporating bugs and maintenance into your Agile teams.  Finally, I am a big believer in the sacredness of the Sprint and I believe that organizations that are disciplined enough to honor a sprint commitment will typically be more successful than those who are loosey-goosey with the guidelines.

Other

Finally, I care deeply about leadership and family so some of my blogs were dedicated to those topics.  One that has been particularly fun is documenting our evolution to an Agile Family.  We have learned (and laughed) a lot together.  Also, I spent some time really thinking about Innovation and what drives an innovative spirit in some people but not others.  This particular blog might be my favorite of the year.

I hope you have enjoyed some of these blogs and maybe learned something new.  I know that I have learned with each post and I am grateful to have the opportunity to continue growing and exploring new ideas.  What is in store for 2014?  Who knows for sure, but it is going to be a great year!

 

Sunsetting a Product: Pricing

It may sound odd that you need to consider pricing when sunsetting a product or platform but you do – at least in some form.  This is the final installment in a series on decommissioning or sunsetting a product.  First you must get data to know exactly what the situation is; second, you must craft your communication plan, and finally, you need to consider the financial implications.

Refunds

If you are truly turning a service off, or ‘going dark’, you may have to consider whether refunds will be required for your existing customers.  If your business model is one of pre-payment, then you need to look into contractual obligations, notice periods and financial true-ups.  The potential impact of refunds may even dictate your sunsetting strategy, so you can minimize pay outs.

Let’s consider an example.  The company charges annually for the following year.  For example, on November 1st, you are charged fordollar_sign2 November 1st to October 31st of the following year.  The company will need to research the month with the highest number of renewals and you might base your decommissioning date based on that information to minimize the refunds.  If sunsetting this product is a large and complex effort, you might consider a rolling project where customers are moved off of the product or platform as their services expire contractually.  This approach can take up to a year to complete, but that might be ideal in certain circumstances.

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?