HTML

stream121
Product Management :: Product Marketing


12 April, 2023

The tough end of product management - sunsetting or cannibalising a product

Sunsetting a product (elegantly) is far harder than creating a product. And cannibalising a existing product with a new one is the hardest of all.

New product development is easy. If it was house-building, you get to choose the brick and where you're going to put it. With sunsetting, it's like putting a wrecking ball through someone's home and expecting them to like it. 

You could say that agile / continuous delivery is the ongoing process of product replacement. True - but the replacement is only modestly different and hopefully better. The cannibalisation that I am referring to is the line-in-the-sand-never-to-return replacement.

Why so hard? An example of the unintended complexities of sunsetting a product
Once upon a time, my management team (inc. me) made a decision to terminate a product: the product had revenue and customers who loved it, but the market's requirements were increasing and the product's market position was being eroded. The investment required to bring the product back into the forefront of the market was significant and ultimately, the returns were better elsewhere in the product portfolio. 

In considering all the ramifications of no longer selling the product, I realised that one of the sales team, let's call her Elspeth, got about 50% of her commission from the sales of this product, as all leads were passed to her. As a result of the (correct) decision to close down the product, she would most probably quit and I thought she was someone that we should keep.

I went to the Head of Sales and pointed this out. He agreed and, as a result, he initiated a territory reassignment, which - and stop me if you've ever been through one of these experiences (*) - took weeks to design / approve / discuss with affected parties etc. 

In the meantime, as the product manager, I oversaw many operational decisions about the product too. I had to try and keep sales going, but approve as few contracts as possible without pissing off Elspeth too much. For example, I had to throw down lots of impediments to each sale: “There's no capacity to deliver that", "Technically, those requirements are challenging", "Ah, that customer will require new functionality that's planned for the next quarter." etc

This, of course, made Elspeth furious - she could see her targets / commission draining away. Complaints were made up and down the company about how I was obstructing every sale. Technically this wasn't true, I approved some deals in order to keep the wheels turning without making it SUPER obvious that sales and delivery was grinding to a halt. Indeed, Elspeth started to believe that I had a personal vendetta against her.

Eventually the territory reassignment plan was all agreed, Elspeth had some new turf carved out for her. She was given some commission for the sunset product sales that she should have won. And finally, we could implement the sunset plan - a plan that had plenty of moving parts in itself: letting existing customers know, properly killing deals in the pipeline, changing the website, redoing sales & budget forecasts, internal comms, etc.  What a lot of stress. And Elspeth finally forgave me!

(*) Territory realignments are painful because: 
  • What happens to deals where the customer is just about to sign? 
  • What about that tacit knowledge of the customer's business and relationship that the sales team has generated?
  • What do you do with commission for deals have been initiated by one sales gal but closed by another? Does credit go to the initiator or the closer or both - and in what ratio? 
This becomes harder when sales revenue is recurring as in SaaS businesses.

Other scenarios: 
  • What about pilot or pathfinder deals - deals that prove a concept with the expectation that future business would result? 
  • When the SaaS revenue is highly variable or seasonal?

Easy cannibalisation 
Swapping out an old product with a new product is easy if the new product is bigger and better in every way and cheaper than the existing product. If the product is more immature, has less functionality (at go-to-market), has a different pricing structure than the old product - what a surprise - you may encounter market resistance. 
  • "You haven't finished the product that you sold me X years ago." 
  • "I can't run my business without features X, Y and Z." 
  • "What? How much more? Are you mad or am I hard of hearing?"
What about internal resistance? Yes, there can be no shortage of that either. If you change the price / pricing structure, it can destroy existing deals in the pipeline (sales, account management & customer support hate you) if the price is more expensive. If the price is cheaper, then sales, account management and finance hate you, as revenue plunges.

Some recommendations from someone that has gone through hell:
  1. Make sure you have the big picture justifications absolutely nailed and bombproof.
    1. Expressions like "Trust me, it's hard" and "It's been decided - it's very complex" will undermine (product) management in the mid-term, never mind the long-term.
  2. Understand your customer base - and the outliers. Handle the outliers with great care - the customers themselves and the internal teams that support them.
  3. Do NOT assume that you will convert every existing customer to the new product.
    1. List out the customers that are most likely to flee and make sure that EVERYONE understands that these accounts are at risk and assume that you'll lose some. 100% conversion is simply naïve.
    2. Make sure that execs are fully onboard if these customers threaten to flee - and they are briefed when they get calls from furious customers (and colleagues).
    3. If it is obvious that the outlier customers might flee, then is the company OK with it? (I mean really???)
  4. Make sure that someone (it may not be product management) has done the analysis of which colleagues might leave (that the company actually needs).
    1. This is super difficult, as some of the reasoning behind sunsetting a product might be associated with technology and skills sets. 
    2. There is an implicit assumption that colleagues will blindly follow an executive decision. The very people that you want to retain for their business knowledge may flee because their product / technology has been jettisoned. 
  5. If you think that product managers should communicate (and they should!), then DOUBLE OVER-COMMUNICATE when sunsetting a product.
    1. Herein lies the hard part of sunsetting a product - a decision to cull a product may require a rapid execution in order that the process doesn't spiral out of control. However, the very people that you need to consult to make a competent decision may be sufficiently ill-informed to advise you.
Finally, best wishes - bridging the chasm between old and new products, especially if it involves repricing is the toughest job in product management!

24 January, 2023

Product Management for Corporate Glue AND Lubricating Oil

Product Managers have a fascinating, all-encompassing role. They can be called many things, CEO of the product, Janitor, Super User. See Product Manager is a janitor basically.

All other business functions are well understood: 
  • Engineering develops the product
  • QA assures that the product 
  • Sales converts a product into justifiable business value for each customer
  • Marketing communicates the product proposition to a market of similar users / buyers
etc

But what do Product Managers do? 

  • Product managers are frequently the glue that keeps the rest of the business functions inside a technology organisation stuck together. They fill in the cracks in between all these business functions.
  • And they are the corporate 'oil' that lubricates other business functions within the company, making each function more efficient and in better harmony with each other.

Example
The next version of the product is coming. It's in Engineering. Product Management has defined the requirements of the product and during the build cycle, it assists with dilemmas and issue resolution.

QA is shaping up to receive the product, but this new version is more sophisticated than the previous version. The QA team need to understand the common use cases / user flows in order to write system / regression tests. They rely on Product Management for guidance.

Marketing is familiar with existing positioning, but this latest release opens up new markets and positioning. They rely on Product Management for guidance: what are the USPs? what are the best use cases? how should it be positioned and to whom? 

Sales may not be able to help for lots of reasons - they want to sell the existing products, not ones that aren't on the price list yet. The rest of the company is dependent on the Sales team selling the existing product in suitable volumes in order to pay the salary bill each month - you really want them sticking to the knitting and selling what's in the warehouse now, not yet-to-be-proven products still on the production line.

Additionally, they have had limited exposure to it: feature and functions aren't well understood yet, positioning isn't developed, use cases and case studies are embryonic at best

Account Management and Support want to know what's different about the new product and how can it be positioned to existing customers and how can they benefit most from it. Is it as good as the existing product? Can existing customers try it before they buy it etc? What the known limitations?

So, often it is the product manager / marketer that goes prospecting for beta customers and manages the beta programme(s) to their successful (hopefully!) conclusions. See the The challenge of beta programmes and Product Launch vs Release vs General Availability vs Deployment.

As a result, it is Product Management who is at the heart of technology product company, acting as its glue and the oil - and that's not contradictory!





09 January, 2023

ChatGPT for product management

With the release of OpenAI’s ChatGPT at the very end of November last year, there has been an explosion of enthusiasm. Here’s their trajectory to a million users!


(Thanks to Azeem Azhar of Exponential View)

Initially, the response was ‘Look at this cool poem that ChatGPT wrote.’ Thankfully more considered use cases are now developing.

So here are my thoughts on how ChatGPT can help Product Managers:
Broad Use Cases Use Cases for Product Management
Summarisation of a long body of text Summarising large amount of texts for requirements analysis
chatGPT is surprisingly competent at summarising text eg for condensing a whole list of free-form product requests from customers into a couple of pithy themes.
And the inverse, extrapolation of short body of text. Writing product descriptions for product marketing.
a. Reinterpreting features to benefits
b. Rewriting product marketing copy for particular audiences
Variation of an existing body of text Wearing your product marketing hat, you have written some descriptive words, but they need some help or the body of text needs to be shorter to fit into a text box on the website or on your PowerPoint.
Initial research into a topic or industry As Product Managers, we spend a lot of time trying to make sense of a market / customer / technology / product / service. I can see myself using chatGPT as a great start to understanding the four walls of a market.

Market research: what do I need to know about XYZ? What’s new and important in the XYZ sector? Who has the competitive advantage and why in XYZ sector?

It’s great a high-level summaries, but not good enough for the details that matter.


As always the devil is in the details, but at least it gives the Product Management some boundaries and some structure to start with. And you would never submit the output from ChatGPT as your completed, best thoughts, BUT it does provide a start and save on that first half hour / blank canvas problem / writer's block when you’re wondering where to start from.

ChatGPT for managers

One great advantage is that it can create consistency when you have review or compare work from multiple teams. By getting your teams to start with ChatGPT's output, then at least all the teams have started from the same point with their use case (not using a template).

What it won't do effectively?

Some have claimed that it could be used to write product requirements. Nope – well, not to a meaningful level and certainly not good enough to give to a developer.

Cute Use Cases

Side Notes on OpenAI
  • Who are their investors - it's always useful to know where the money flows. 
  • Y Combinator
  • Peter Thiel (founder of Paypal)
  • Reid Hoffman Foundation (founder of LinkedIn)
  • Khosla Ventures 
  • Elon Musk did invest, but has now sold off his stake
  • Microsoft Ventures ($1bn investment in 2019 + MS has built a supercomputer in Azure to support OpenAI ML research)

OpenAI have more complex corporate structure than most: there is for-profit corporation OpenAI LP and its parent company, the non-profit OpenAI Inc. AND in 2019, OpenAI transitioned from non-profit to "capped" for-profit, with profit cap set to 100X on any investment. (Source: Wikipedia)