[jman73]

Hey - I think we disagree on the basic premise. I don't think most features are there because the clients "need them". The point of the post is that many are there because they think they need them, and thus, through a sales process they were "required". Of course, one size does NOT fit all... many specialized apps do require more features... but in general, you can kill features, especially if based on data that shows nobody really uses them.

[omh]

"Killing" a feature before it's rolled out would be great, but it's hard to start talking a potential customer out of a feature request if there's a chance it will put them off your product. Doubly so if it's a salesperson talking to them who doesn't have detailed technical experience.

And killing features after is always a problem. If you've got lots of users then some of them are probably using every single feature, no matter how dumb it is.

[jman73]

Totally agree... but again, point of the post was that when you are selling bottom up, and your "customer" is the end user, you are less locked by a singular buyer who think that something is required. No doubt that this approach can cause some friction, and it is way easier before release... but it can be done...if the primary goal is user experience.

[ido]

    if the primary goal is user experience.

That's a pretty big if :)

[jman73]

totally agree... but that's the if the post rides on!