<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Do not be afraid to remove features</title>
	<atom:link href="http://www.goodproductmanager.com/2008/02/17/do-not-be-afraid-to-remove-features/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.goodproductmanager.com/2008/02/17/do-not-be-afraid-to-remove-features/</link>
	<description>A blog with tips on product management and related topics. Written by Jeff Lash, a product manager in St. Louis, MO</description>
	<lastBuildDate>Sun, 07 Mar 2010 10:14:56 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: &#187; Blog Archive Feature Un-creep: simplification at a price&#8230; &#124; KiteTail: innovation management for growth</title>
		<link>http://www.goodproductmanager.com/2008/02/17/do-not-be-afraid-to-remove-features/comment-page-1/#comment-8906</link>
		<dc:creator>&#187; Blog Archive Feature Un-creep: simplification at a price&#8230; &#124; KiteTail: innovation management for growth</dc:creator>
		<pubDate>Thu, 19 Jun 2008 04:22:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/2008/02/17/do-not-be-afraid-to-remove-features/#comment-8906</guid>
		<description>[...] Product Manager has a well written article on how to address feature removal from your product: Do not be afraid to remove features. Looking at Twitter traffic on this topic, Netflix product manager should be reading Jeff&#8217;s [...]</description>
		<content:encoded><![CDATA[<p>[...] Product Manager has a well written article on how to address feature removal from your product: Do not be afraid to remove features. Looking at Twitter traffic on this topic, Netflix product manager should be reading Jeff&#8217;s [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How Feature Creep Can Hurt Your Brand</title>
		<link>http://www.goodproductmanager.com/2008/02/17/do-not-be-afraid-to-remove-features/comment-page-1/#comment-7552</link>
		<dc:creator>How Feature Creep Can Hurt Your Brand</dc:creator>
		<pubDate>Sun, 16 Mar 2008 21:58:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/2008/02/17/do-not-be-afraid-to-remove-features/#comment-7552</guid>
		<description>[...] Do not be afraid to remove features [...]</description>
		<content:encoded><![CDATA[<p>[...] Do not be afraid to remove features [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://www.goodproductmanager.com/2008/02/17/do-not-be-afraid-to-remove-features/comment-page-1/#comment-6664</link>
		<dc:creator>James</dc:creator>
		<pubDate>Tue, 19 Feb 2008 09:13:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/2008/02/17/do-not-be-afraid-to-remove-features/#comment-6664</guid>
		<description>Great post, Jeff. I&#039;m glad this is finally out there in black and white. Feature creep is something I personally detest. And removing features is such a foreign concept to most product development mindsets.  I think it was Tom Kelly from IDEO that even said that innovation can happen by removing features. 

I was contemplating feature fatigue the other day (See Gene Smith&#039;s posting on this: http://tinyurl.com/ywrbum) while looking at images of a Swiss Army knife. Advertisements of the knives almost always have every blade expanded to show product capability. That&#039;s good for sales. But in the long run it&#039;s the fact that you can collapse them all that makes it value and usable to us. Most products don&#039;t have that kind of balance, and instead stuggle between adding features for sales appeal versus long-term usability.

That said, as an interface designer I also feel that it should be possible to communicate information or present features in such a way that doesn&#039;t overwhelm people. But that depends on the level of control given to the designer (often short-term business needs trump design decisions) as well as how the product is developed (&quot;dripping&quot; features in over years can make it hard to end up with a consistent, clean design). 

Still, there&#039;s a point when feature creep becomes ridiculous. Like the comedian Steven Wright says, &quot;You can&#039;t have everything--where would you put it?&quot;</description>
		<content:encoded><![CDATA[<p>Great post, Jeff. I&#8217;m glad this is finally out there in black and white. Feature creep is something I personally detest. And removing features is such a foreign concept to most product development mindsets.  I think it was Tom Kelly from IDEO that even said that innovation can happen by removing features. </p>
<p>I was contemplating feature fatigue the other day (See Gene Smith&#8217;s posting on this: <a href="http://tinyurl.com/ywrbum)" rel="nofollow">http://tinyurl.com/ywrbum)</a> while looking at images of a Swiss Army knife. Advertisements of the knives almost always have every blade expanded to show product capability. That&#8217;s good for sales. But in the long run it&#8217;s the fact that you can collapse them all that makes it value and usable to us. Most products don&#8217;t have that kind of balance, and instead stuggle between adding features for sales appeal versus long-term usability.</p>
<p>That said, as an interface designer I also feel that it should be possible to communicate information or present features in such a way that doesn&#8217;t overwhelm people. But that depends on the level of control given to the designer (often short-term business needs trump design decisions) as well as how the product is developed (&#8220;dripping&#8221; features in over years can make it hard to end up with a consistent, clean design). </p>
<p>Still, there&#8217;s a point when feature creep becomes ridiculous. Like the comedian Steven Wright says, &#8220;You can&#8217;t have everything&#8211;where would you put it?&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gregggallagher</title>
		<link>http://www.goodproductmanager.com/2008/02/17/do-not-be-afraid-to-remove-features/comment-page-1/#comment-6650</link>
		<dc:creator>gregggallagher</dc:creator>
		<pubDate>Mon, 18 Feb 2008 14:24:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/2008/02/17/do-not-be-afraid-to-remove-features/#comment-6650</guid>
		<description>Excellent post, Jeff on the trade-offs and the thinking behind them that needs to take place in a &quot;zero-based planning&quot; approach to product design. As you know, one of the biggest challenges will be when a product feature still has some value to some subset of the customer base, and the benefits derived from leaving it out (lower costs, added flexibility for incorporating other features, etc.) are not totally clear/measurable so as to make the trade-off evaluation clear-cut.

Reminds me of the old joke as to why it only took  god six days to create the world....because he didn&#039;t have an installed base to deal with....</description>
		<content:encoded><![CDATA[<p>Excellent post, Jeff on the trade-offs and the thinking behind them that needs to take place in a &#8220;zero-based planning&#8221; approach to product design. As you know, one of the biggest challenges will be when a product feature still has some value to some subset of the customer base, and the benefits derived from leaving it out (lower costs, added flexibility for incorporating other features, etc.) are not totally clear/measurable so as to make the trade-off evaluation clear-cut.</p>
<p>Reminds me of the old joke as to why it only took  god six days to create the world&#8230;.because he didn&#8217;t have an installed base to deal with&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul M. Banas</title>
		<link>http://www.goodproductmanager.com/2008/02/17/do-not-be-afraid-to-remove-features/comment-page-1/#comment-6617</link>
		<dc:creator>Paul M. Banas</dc:creator>
		<pubDate>Mon, 18 Feb 2008 02:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodproductmanager.com/2008/02/17/do-not-be-afraid-to-remove-features/#comment-6617</guid>
		<description>Knowing when to say when is probably the least developed, but most essential, skill of any product manager.  Consumers will pay more for added value from a new product, but not much more.  

What you outline in point #2 is a bit trickier.  Taking away something that the consumer has gotten used to, even if it isn&#039;t a critical component, opens you up to questions of why they even buy or use your product in the first place.

Your advice on how to mitigate this danger is very sound , though.   

Obviously, it is always easier if the product manager has a clear product strategy to begin with.  Then they know what features truly add value and can sell products at the best possible cost to the consumer, without having to do the risky job of removing benefits later on.</description>
		<content:encoded><![CDATA[<p>Knowing when to say when is probably the least developed, but most essential, skill of any product manager.  Consumers will pay more for added value from a new product, but not much more.  </p>
<p>What you outline in point #2 is a bit trickier.  Taking away something that the consumer has gotten used to, even if it isn&#8217;t a critical component, opens you up to questions of why they even buy or use your product in the first place.</p>
<p>Your advice on how to mitigate this danger is very sound , though.   </p>
<p>Obviously, it is always easier if the product manager has a clear product strategy to begin with.  Then they know what features truly add value and can sell products at the best possible cost to the consumer, without having to do the risky job of removing benefits later on.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
