Comments on: Guest Post: To Kill a Product: Why, When and How, Part 2/3

By: Guest Post: To Kill a Product: Why, When and How part 3/3 | On Product Management

Mon, 05 Jul 2010 13:17:39 +0000

[...] Part 2 When?: When is it time to kill a product? Part 2 offers up six areas to keep an eye on for telltale signs. It’s examining these areas that will help product managers build the case to kill or keep a product. [...]

By: While you were out: Top GUEST posts of the summer from ON PM « On Product Management

Wed, 09 Sep 2009 02:41:41 +0000

[...] kill a product: Why, When, and How (3 parts, Chris Brown, VP PM at [...]

By: Titus Osikoya

Titus Osikoya — Thu, 03 Sep 2009 14:27:21 +0000

I was refered her by someone on LinkedIn Question and answer. I appreciate this post a lot.

Thanks Chris

By: Guest Post: To Kill a Product: Why, When and How, Part 1/3 « On Product Management

Fri, 28 Aug 2009 19:32:08 +0000

[...] This post is contributed by Chris Brown, Vice President of Product Management at Apartments.com. This is the first in a three-part series that takes an in-depth look at that process and makes its own set of recommendations on why, when and how to kill a product. (Part 2, “When”, is here.) [...]

By: Robin den Buurman

Robin den Buurman — Fri, 28 Aug 2009 07:26:37 +0000

Again a very usefull post. Thanks. As PM I like to sink off atleast 15 products that are in my opinion not feasible but need strong arguments to let go of that revenue.

By: Chris Brown

Chris Brown — Thu, 27 Aug 2009 21:41:29 +0000

Another great comment, Dheeraj. Thanks! In Part 3 I talk about the communication aspects. Great catch on the regulatory bodies, which in my industry I don’t have to give too much consideration to, but can be critical in others. You’ll see that I do recommend early and frequent communication with your legal department, which would undoubtedly take regulation into consideration.

Thanks again,
Chris

By: Olav de Swaaf

Olav de Swaaf — Thu, 27 Aug 2009 20:02:36 +0000

RT @pgabes: Reading: Part 2: When to kill a product http://bit.ly/3zoQrg

By: Pieter Gabes

Pieter Gabes — Thu, 27 Aug 2009 18:46:18 +0000

Reading: Part 2: When to kill a product http://bit.ly/3zoQrg

By: Dheeraj

Dheeraj — Thu, 27 Aug 2009 05:22:48 +0000

Chris,

That is a great table. It covers most of the key things that product managers and business heads consider. There are some other aspects as well that merit mention:

The people factor:

The dev, test and program management team are often galvanized around a product, its technology and plans for future versions. Killing a product might involve re-skilling costs at one end and might serve as a great breather for a burnt-out team. This is a soft cost that really adds up.

Communicating the right message to people who refer:

When killing a product, sales is often engaged in talking to new prospects, building new channel alliances or educating channels etc. Often people (past clients mostly) who have been championing your product for free also need to be taken into account. This is a diverse set and tackling it takes time. However it is vital to take your voluntary brand ambassadors along.

Regulatory bodies:

If your product is serving the Government, getting clearances for a phase out is a real pain even when everyone realizes the benefits.

By: Chris Brown

Chris Brown — Thu, 27 Aug 2009 02:22:57 +0000

RT @onpm: Part 2of3 of my guest post: WHEN to kill a product: http://tr.im/killproduct2of3 Thanks @onpm! #leadership #prodmgmt #prodmktg