Simple Technology

Note: This has been sitting around in my drafts for ages, I consider it unfinished but that’s never stopped me from posting something before…

A while ago Adrian mused (lusted?) over Apple TV sets and in the comment to that post, he rightly states that

“Technology should serve it’s purpose and technology should be as simple as it can be without breaking it’s purpose.”

Now, before I go any further I will confirm that what Adrian was really saying was that

“Technology should serve it’s purpose and technology should be as USABLE as it can be without breaking it’s purpose.”

Which is very different from “technology should be simple”. After all, it takes a long time for technology to evolve to a point where it’s considered “simple”. Or maybe it’s the other way around, maybe it’s the time it takes the population to get to grips with a new technology that defines whether something is considered simple, or not.

Anyway, let’s go with the opening statement(s); technology should be simple, it should be open to all who want to use it and should be designed to be usable by whoever buys it.

Nothing much of contention there. Or is there?

By it’s nature, modern consumer technology (and I’m referring directly to the underlying workings of the myriad of electronic gadgets you have in your house) is hugely complex, and I’d suggest that the internals of most of these are both highly technical and likely quite scarily off-putting if presented to the layman. Of course that doesn’t really matter these days as most consumer electrics are considered to be throw away items. That computer printer that isn’t working anymore? Just go and get a new one, they are only £30… that broken DVD player? £25 for a new one, so why bother trying to get the case open to check if there is a loose wire? Technology has shrunk so much that unless you are happy working on tiny circuit boards you are unlikely to even bother trying to fix anything. At that level, the technicality of the product is a barrier that is deemed acceptable by most, a line across which the general punter won’t even consider stepping across.

Ohh and to all my lovely readers who are shaking their heads at this point, remember, you are not a ‘general punter’. You are most likely a geek and bemoan the fact that, these days, most electronic gadgets are completely sealed and glued shut, I hear you, I feel your pain.

At that technical level, most of us are happy to ignore the technology completely. If it’s broken it’s either someone else’s problem, or we replace it. Simple.

The real problems start when technology isn’t designed around the customer, isn’t designed with the user in mind, and that is when the statement that Adrian made – Technology should serve it’s purpose – needs to be revisited. Quite simply a lot of everyday technology isn’t designed with the main purpose in mind. Let’s take an everyday example.

My TV has an internal signal regulator switch which allows it to handle multiple inputs of an Audio/Video nature. It’s smart enough to detect when one of the inputs is turned on, and switches itself to the correct channel to show whatever it is receiving from that input. I can then, with the push of a button, change which input I am viewing. Simple. One little button.

Ohh I’m sorry, too technical? Right, if I’m watching Sky and I turn on my DVD player, the TV switches over to the DVD player, but if I want I can switch back to Sky with the push of a button.

And what is that button called, the one that lets me switch between Sky and my DVD player? If you are lucky it’s usually labelled “A/V”. Well I say lucky, but it’s not hugely obvious what that means, is it? Not to a lot of people at least. Sure you can learn what it means, but ultimately you’ll store that information as “pushing that button changes between Sky and my DVD player”. You may remember that it means Audio/Video, but why should you have to? Re-labelling this as “Switch Inputs” would be best but that’s a bit cumbersome for a remote control, but even S/I might be better? I don’t have a good answer for this but A/V just isn’t right… but mind you, the weird symbol I have on my TV isn’t right either, in fact it’s so wrong I had to check the documentation to find out what it meant!

But, just to flip this all on it’s head, maybe, just maybe, A/V IS the right label for that button.

I suggested, in a comment to Adrian’s post, that perhaps technology needed to retain some barriers in an effort to minimise the impact of unleashing technology on non-techie type people. Gosh, how horrible am I. How exculsive. What a techno-snob!

Let me be slightly more specific then, I think in certain instances, barriers are required and should remain long past the ‘early adopter’ stages and into the life of a technology. A good example, in my opinion, is the trend towards convergence shown by most of the large ‘gadget’ manufacturers over the past few years. Do I really need a kettle that can talk to my fridge, and a fridge that can re-ordered milk when my supplies run low (ok, the latter might be useful, I’m always forgetting to remember the milk… I should really note that down in my to do list you know…)

During the life of most technologies a central equilibrium is found and that will suit the majority of consumers (even if it isn’t the ‘best’ technology). The most obvious example is the, now ubiquitous, iPod. It is not as feature rich as other MP3 players but being well-designed (and well marketed) it is usually what most consumers think of when you say “MP3 player” (remember, dearest blog reader, that you are probably more technically aware than most). The very fact that the iPod DOESN’T have a radio, and DOESN’T let you record are barriers. Adding those features would raise the technical level for usage to a point that, I can only presume, Apple aren’t comfortable with. OK, maybe it’s just because it doesn’t fit with their business plan for the iPod.

I guess what I’m really arguing here is that early adopters are good things, and that products don’t (shouldn’t?) always have to be simple and usable until they reach a critical mass.

I could also say that I’m arguing that product design should be left to designers, not techies, but that to get a product to the point of being easily accepted then sometimes it’s good to have a few barriers in the way, then once the kinks are ironed out THEN it can become a consumer product??

Of course it all really depends on what you class as technology.