This is a very interesting piece and I ask myself this query each time I build features.
Users never read manuals but start using the software immediately. They are motivated to get started and to get their immediate task done: they don’t care about the system as such and don’t want to spend time up front on getting established, set up, or going through learning packages. The “paradox of the active user” is a paradox because users would save time in the long term by taking some initial time to optimize the system and learn more about it. But that’s not how people behave in the real world, so we cannot allow engineers to build products for an idealized rational user when real humans are irrational: we must design for the way users actually behave.
Most of the times, the engineering-mind tries to show-off its skill ( but I try and resist the temptation nowadays 😉 ). vtiger will not be All. What I need to know is what you guys want to start working with the product out-of-the-box. Let us face it, you do not have the time to customize the product, learn all the features of the product and then use it. You want to use the product right freaking NOW!
So, it should be sensible if we give only those features that you are going to use all- or at least most-of-the-time. Right?
On the other hand, a related but 180-degree opposite(apposite 😉 view is at follows :-
http://www.iathink.com/2006/12/features_sell_p.html
What should I do?
