In any other type of product, if it is hard to use, people will look for something better. Whether it is a car, dishwasher, lawnmower or anything else, you would not put up with struggling to figure out how to use it when you can buy something else that is simpler and allows you to get to work, wash your dishes or mow your lawn more effectively.
In light of those facts, you would expect that anyone building a product, whether a physical product or a piece of software, would place ease-of-use at the top of the priority list. However, in may cases that isn't true.
It goes back to the early history of computers when the people using them were the people that created them and they understood and appreciated how difficult they were to program to do anything. So when presented with something complicated, they thought "wow... this must have been really complicated to develop". They were ok with that. But now, computers and software are "magic" to the majority of people. They don't care how complicated they are to develop and don't appreciate the effort (and they are right not to). But people creating software sometimes think that users will understand how difficult a feature is and cut them some slack if the interface isn't as good as it could be. It just isn't true anymore.
I, and other designers I'm sure, would be interested to here success stories from those designers who have overcome the "lets just make it work... we'll make it easier to use later if we have time" mentality. Feel free to comment.
1 comment:
Rob – a few points that spring to mind.
Firstly, cars actually have a pretty badly designed interface, and are a good example of a device where humans make a lot of effort to understand the machine. It’s interesting that cars for disabled drivers often show more innovation in controls (for instance, cars that can be controlled entirely using the hands using a Playstation like controller).
Secondly – don’t blame the programmers. To make a comparison, they are engineers, not architects or car designers. Now of course, a good architect understands engineering, and a good engineer understands architecture, but if you wanted to build a great and usable building, you wouldn’t hire a team of engineers and try to argue them into designing ‘something better’.
And there lies the rub – the problem is that most companies don’t hire on application design experience / make the mistake that it’s about hiring a graphic design artist to change a few colours. They keep hiring engineers and expecting a different outcome.
Post a Comment