3 ms·
To make your application appear complex is just going to increase the barrier to entry. That depends on the customer segment you are targeting. Over-complex d
by michael_dorfman 16y ago
To make your application appear complex is just going to increase the barrier to entry.
That depends on the customer segment you are targeting.
Over-complex design does not drive sales unless you're trying to send all your competitors down a dead end street.
Or, if you're selling "Enterprise Software". I've had to re-design things to be less simple, in order to make them more attractive to customers, and had my staff spend countless hours developing bells and whistles that impressed purchasing VPs in demos, but then were never used by the actual users.
Some customers will take "more features, and a busier looking interface" over "a simple, elegant design that actually does everything you need it to" every time. In my experience, these tend to be the customers who are not users themselves-- but, they often have the purchasing power over thousands of users.
- jacquesm 16y agoThat's kind of the point right? When end users do not drive sales you are likely right, as your experience indicates. But when end users do drive sales (and for most of us here that's day to day life) then a clean interface is key. B2B is different in this respect than B2C, and conspicuous consumption is different from both of those still.
- akshayubhat 16y agobut then were never used by the actual users That's fine, The last thing VP's or management want is an employees coming to them and telling how they "can't" do something due to lack of a feature. Cost of not getting a job done due to lack of a feature is very high compared to cost of adding that feature. And cost of adding a new feature only when a need arises is even higher. It is hard to predict which feature you will actually need over course of time, thus the safest bet is to have as many reasonable features as possible.