Comments on: “Release Early, Release Often” vs. Seth Godin http://www.tonywright.com/2007/release-early-release-often-vs-seth-godin/ Pathologically Entrepreneurial Wed, 30 Jun 2010 20:10:32 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: make sure you heard about Seth Godin « tips and tricks for web startups http://www.tonywright.com/2007/release-early-release-often-vs-seth-godin/comment-page-1/#comment-1502 make sure you heard about Seth Godin « tips and tricks for web startups Wed, 17 Jun 2009 21:24:42 +0000 http://www.tonywright.com/2007/release-early-release-often-vs-seth-godin/#comment-1502 [...] you didn’t hear het about Seth Godin, make sure you do now by reading some of the following artickles, and make sure to subscribe for his blog! In the first place, it [...] [...] you didn’t hear het about Seth Godin, make sure you do now by reading some of the following artickles, and make sure to subscribe for his blog! In the first place, it [...]

]]> By: Anonymous coward http://www.tonywright.com/2007/release-early-release-often-vs-seth-godin/comment-page-1/#comment-37 Anonymous coward Mon, 23 Apr 2007 07:25:40 +0000 http://www.tonywright.com/2007/release-early-release-often-vs-seth-godin/#comment-37 The problem with release often is that you should have a policy on deprecating lightly used features ... Once a feature is out there and is being used .. Its hard to deprecate it. Even if the usage is low. There might be some pain for the user to have the feature pulled out from him/her. If you do not deprecate, you end up with gloat So whats wrong with this approach 1) Too much clutter. The hallmark of great UI is simplicity. How can u have simplicity, If you have a huge bunch of features, most of which do not get used ? 2) The customer is left with a bad taste in his mouth ... With most of the stuff not working right, the first time. This hurts your reputation too. 3) nobody wants to be a lab rat ... The problem with release often is that you should have a policy on deprecating lightly used features … Once a feature is out there and is being used .. Its hard to deprecate it. Even if the usage is low. There might be some pain for the user to have the feature pulled out from him/her. If you do not deprecate, you end up with gloat

So whats wrong with this approach
1) Too much clutter. The hallmark of great UI is simplicity. How can u have simplicity, If you have a huge bunch of features, most of which do not get used ?
2) The customer is left with a bad taste in his mouth … With most of the stuff not working right, the first time. This hurts your reputation too.
3) nobody wants to be a lab rat …

]]>