Sensational headlines aside (I love them I'll admit it), it's critically important to define the amount of time your product's users have to use your application when designing for them.
If I've learned one great lesson from designing for various front office groups at banks (Traders, Salespeople, Researchers, Assistants / Administrators, etc.) is that time is critically important. It may sound simple enough, but it's crucial (as is taking into account the users' attention span). This doesn't just apply to enterprise however, knowing the time your users are willing to commit to clicking around, trying new things in your app, how quickly they could get frustrated etc. is extremely important.
Asking an administrator or assistant user to perform a couple of clicks, import & export, etc. this is generally not a problem, and they will take the time to learn. Same could be said for a user that is in high school or college still and not yet taken by the responsibilities of job + child rearing + friends. They are more interested in a work / life / productivity boost and willing to take the time to get there, generally.
However asking a Trader / Salesperson or any user in a "revenue generating" role where they could miss creating revenues for the business, seconds matter. Generally these revenue generating users are a very smart bunch, but can become easily frustrated and abandon your application immediately if they can't get where they need to go in two clicks or less. While frustrating for us product people, I totally get it, someone has to bring in the revenues for us to build great stuff!
Contrary to this would be a technologist, a smart individual in a non-revenue generating role, who generally will have no issue clicking around and trying to see what kind of value they can get out of the system. Generally these users are more patient (or trying to be, looking at myself here as I place the hammer down that I was about to throw at the screen earlier today).
In summary, really step into the users shoes and define whether having 200 features accessible on one screen matters, or maybe just 3 features placed very explicitly and easily in front of the user. Odds are if it's a "revenue generating" user, they will love you if you just put the 3 features of value to them in the front and nothing else.
How do you handle different types of users and their time? Tell me in comments!