The thing isn’t broken, the design is

[dc]

I thought this report was interesting: half of all “malfunctioning” products are in full working order, it’s just that the poor bloody customers can’t figure out how to operate the devices. Even worse for them, companies frequently dismiss them as ‘nuisance calls.’ It was a nice touch that the study being reported involved giving managers products to use over a weekend:

The managers returned frustrated because they could not get the devices to work properly.

A nice glow of Schadenfreude there.

This report didn’t surprise me, nor did Elke den Ouden’s conclusion that Most of the flaws found their origin in the first phase of the design process: product definition — which I take to mean that they never clearly worked out what it was they were trying to do with the thing. I’ve been thinking for a long time that many examples of modern technology have been designed by people who have given no thought to how real people would interact with the devices.

Take digital cameras. I have a nice wee digital camera which I got for nothing because a friend got so fed up with trying to get it working that he thrust it at me, saying Here, take the bloody thing, I never want to see it again. Now, I have (it seems) some sort of talent in sitting down with a bit of technology and figuring out how to use it without too much difficulty. It didn’t let me down here: within five minutes of trying to get the camera working, I had taken several pictures and transferred them to the PC. I mention this, though, not to show technologically challenged my friend is (though he really is), but to show that I have little problems most of the time with technology and software. (It is ironic that I regularly advise people like my friend to RTFM while I have hardly ever read a manual myself.) Yet not so long ago, a bunch of us were looking at another digital camera — I think it was at l_zinkiewicz’s leaving drinkies do — and none of us could figure out how the thing was supposed to work. We might as well have been trying to read quipu when were prowling through those menus.

It seems to me there are two basic problems with a lot of modern kit:

1. It has been designed by people who have a fixed idea about how they would use it, without considering whether or not it would even occur to someone who hadn’t been involved in that process to use it in that way.

2. There is huge over-reliance on icons. Most icons are completely meaningless to anyone seeing them for the first time, yet a lot of kit (and software — but at least you might get tooltips there) has nothing but icons to indicate what you are supposed to do. This was, by the way, the problem with that camera. Little or no text, just a lot of obscure wee icons.

All of which is a pain, and it irritates me that, for example, my mother got a mobile phone a while back which is almost unusable because of a hideously badly designed menu system (she has to enter a number manually every time she wants to call it). I do worry, though, about the application of such design techniques in areas such as aviation, or the military, or car design.

Comments

[wibbble]

If someone has physical access they don't /need/ your passwords: they can simply boot the machine from a LiveCD and access everything as root - or just open it and remove the HD.

Mac OS X, by default, disables root - sudo's available, but you can't log in as root. 'Administrator' users (including the first user, by default) are in the wheel group, so they can sudo.

Multiple instances of X11, and switching between them, is certainly something that's been around *nix for years, but it's definitely beyond the install-and-forget kind of thing you're talking about. The big strength of Mac OS X isn't so much that it's introducing never-heard-of-features, it's that it's making them effortlessly to use.

[tanngrisnir.livejournal.com]

Sorry, I didn't put it very clearly. Yes, I know that if someone has access to the machine they can do what you say (in fact, I did it myself to one of my hard drives after a catastrophic double crash — and come to think of it, it wasn’t that simple, since you had to know how to set permissions) — what I actually meant was that most of the people you need to worry about getting unwanted access to your machine don’t have a sufficient level of knowledge to do that. For them, having a password restriction is a good safety measure.

There was the case of the guy whose laptop was stolen on the Tube. The gits who stole it clearly were stymied by the fact that it didn’t boot Windows, and then demanded a password. They left it on the Tube in disgust and he got it back, intact and with his data secure.

It used to be the case that you just couldn’t install Linux in such a way that it could boot without having to enter a login and password. I don’t know which distro had the bright idea of allowing direct boot into a user session, but I think it is foolish. I suppose we should be grateful for the small mercy that those distros which put up a menu of users on the login screen don’t include root there.

Actually, the switching between different sessions isn’t beyond the install-and-forget thing. It’s sitting there in the KDE menu, and a helpful dialogue comes up to tell you what’s going on if you don’t already know.

I am not only impressed at how effortless these new distros are, I am actually surprised.

[wibbble]

You're not the only one that's surprised. :o)

I'll be sticking with Mac OS X, though, for any machine I need to interact with directly. I was planning to get an AMD64 machine later on this year so that I could work on some stuff locally, but it would probably be a box without a monitor.