eftychia: Me in kilt and poofy shirt, facing away, playing acoustic guitar behind head (Default)
Add MemoryShare This Entry
posted by [personal profile] eftychia at 05:26am on 2008-06-08

From the Quotation of the day mailing list, 2007-01-13:

"I should be able to do tasks without learning a complex technology. Right now my clock tells me the time. Maybe it should also tell me the weather. And where my kids are. Today we have to learn tools; I want to make that necessity disappear." -- Donald A. Norman, cognitive scientist, quoted in Wired (issue 6.05). Norman is the author of The Design of Everyday Things.

(submitted to the mailing list by Terry Labach)

[To my friends celebrating it tonight and tomorrow, blessed Shavuot!]

There are 9 comments on this entry. (Reply.)
 
posted by [identity profile] acroyear70.livejournal.com at 10:22am on 2008-06-08
And where my kids are.

I wonder if that's where the idea for the clock in the Weasley's house came from in Harry Potter...
 
posted by [identity profile] smallship1.livejournal.com at 10:29am on 2008-06-08
So he doesn't want the brain to have to learn to do anything.

I hope he never succeeds.
 
posted by [identity profile] metahacker.livejournal.com at 12:50pm on 2008-06-08
This statement is hilarious, given what Don Norman has done.
 
posted by [identity profile] smallship1.livejournal.com at 03:45pm on 2008-06-08
Sorry, I have no idea what he's done, so I'm going purely on the statement as quoted, which seems to me fatuous in the extreme. If he didn't mean what I understood by it--the removal of the necessity for the brain to learn how to do things--then maybe he expressed himself poorly.

Personally, I think the more complex technologies the brain has to master, the more learning it has to do, the better equipped it will be. But that's probably just me.
 
posted by [identity profile] realinterrobang.livejournal.com at 04:32pm on 2008-06-08
I think the more complex technologies the brain has to master, the more learning it has to do, the better equipped it will be.

I'd say that sort of depends. My personal experience with tool-learning falls mainly in the area of literacy, and it's actually sort of scary how the bar for functional literacy keeps getting higher and higher, since inevitably it's going to start leaving more and more people out. At one point, you were considered literate if you could write your name and maybe a few other things. Later on, you had to be able to read text as well as write. Then you had to be able to write as well as you could read, to a certain specified level. Then you had to be able to process complicated information presented in highly abstracted forms (e.g. telling time using more than one system of clock, deciphering maps and transit schedules) as well as read and write to an equal level. Now, it's getting so that the basic definition of functional literacy includes all that and being able to interpret and navigate a computer interface.

Concomitant with that and other similar societal developments has been a lengthening of the period of formal education it takes to create a functioning adult.

That's just one area of tool use, and there are countless others. So from the point of view that most likely we're going to hit a tipping point somewhere, yes, I think there are ample grounds to suggest that one ought not have to learn a completely new skill set every time one has to do a simple task.
 
posted by [identity profile] metahacker.livejournal.com at 04:47pm on 2008-06-08
But that's probably just me.

It's a typical reaction when faced with this quote. Hell, I had that reaction at first, too: he's just dumb, and too lazy to figure out how to do things. (Though I didn't go so far as to wish him ill. That seems...petty.) The reaction seems especially common among people whose job it is to figure out complex technologies. "Why simplify things? Learning to use a new tool well is an art in itself -- and rewarding. Besides, afterward I know how to use this tool so well, I can do new cool things with it."

But there's an important distinction to be made: spending your time learning to use a tool for a task helps you do your task, and is time invested in doing your task (or new tasks) well. Time spent learning how to overcome your tool's shortcomings so it can help you do your task is time wasted: that is an extra task added on top of the thing you were already trying to do.

Ease of use is *really* hard to design. It's so hard that you rarely see it, because when it works it's invisible. (Hence his later book, "The Invisible Computer".) It's so hard that we're surrounded by counterexamples, things which mistake simplicity for usability, or resort to constraining the user's actions to ones which the designer made easy.

Norman theorized and, more importantly, explained carefully, how to design things such that they help you do what it was you were trying to do in the first place. He's not dumb; he's lazy, which is why he (e.g.) spends a tremendous amount of time working on his books so that they're understandable. I commend them to you, especially the one mentioned above...though the insights in them may seem too obvious when you read them, for the above reason!
 
posted by [identity profile] dglenn.livejournal.com at 06:38pm on 2008-06-08
Spend more time learning underlying skills and advanced techniques, and less time learning interfaces -- ideally one should only have to spend the time learning the tools/interfaces when there really is no way to design a sufficiently powerful yet non-novel interface for the problem domain.

Ideally, I don't want to even notice my tools ... well, beyond noticing that I'm more powerful with them, of course. Sometimes this does require learning a non-obvious interface well enough to master it and then stop thinking about it -- the vi text editor was an example where that paid off for me, but I've been using that one tool, in a variety of contexts, for nearly thirty years now, so that makes those first few months worth it. I shouldn't have to think about how to use the tool I'm using every time I pick up a new tool though; only when a) it's going to pay off like vi did (okay, that and driving a car are extreme cases, but you get the idea) and the complexity of the problem is such that a simpler tool won't give me enough power.

When I pulled my DSLR out of the box, I stuck a lens on it, noted a switch with positions marked 'Off', 'On', and a non-obvious symbol (which became clearer when I went looking for a control to do what it turned out to do), and a mode-selector switch that had mostly-familiar (from film cameras) markings. So I turned it on, pointed it at Perrine, pressed the shiny silver button that was in the expected, natural, and ergonomic location for a shutter release, and the LCD panel on the back lit up with a picture of my cat. No new learning. Good design.

When I wanted to do something with more control than that, I din't have to figure out a new way to do things; I only had to see where the controls were -- once I found the aperture and shutter speed controls, everything I had already learned about photography was immediately applicable. The tool became transparent. As I remarked on a Pentax-users mailing list, for most things I didn't notice needing any new skills with the DSLR, which (significantly for this anecdote) has both more automation and more control than any of my film cameras; it just made applying my existing skills easier and faster. I didn't really have to spend much time Learning The Tool -- thinking about the tool instead of the problem -- until I started wanting to do something odd with it. That's very good design but not quite great design: with truly great design, "much" in the previous sentence would have been "any".

Note that I did still need skillz, ones that I'd learned on film cameras. Here's the point: those skills had everything to do with the problem and relatively little to do with the tool.

I am happiest when I don't notice my tools. I have an idea, I decide to will the idea into reality, and it just happens, as easily as thinking about taking a drink of water turns into the glass arriving at my lips. I don't think about how to operate my hand until I am injured; I don't think about how to operate a pen until it malfunctions. Not every tool has as simple an interface as a ball-point pen, but the more transparent the tool -- the more it becomes simply an extension of my will, as my muscles are -- the better.

I'd rather spend the time learning problem-skills than tool-skills.
 
posted by [identity profile] leiacat.livejournal.com at 05:23pm on 2008-06-08
Actually, what he generally wants is that when presented with a new environment, any reasonably sane person should be able to figure it out without undue stress. So, things that look like they ought to be "on" buttons happen to be "on" buttons, door handles that look like they ought to be pulled don't turn out to need twisting and pushing, and the tea kettle handle is on the opposite side of the spout.

The un-set clock on the VCR is such a cliche because there _are_ so many people who never bothered to figure it out, because they have what they consider to be better things to do. If you're standing in line at an ATM, the last thing you want is for the guy in front of you to spend 5 minutes figuring out the interface - you want it easy enough that your time isn't spent on his learning curve.

And if you want your clock to tell you the weather, I bet you want it to be quicker and more efficient than logging onto a computer to check it, or then turning on the TV to the Weather Channel - otherwise, the tool is simply not as useful.

It's not about not learning anything, it's about everyday tasks being simple enough that you can spend your energy on things you'd rather be doing.
 
posted by [identity profile] dglenn.livejournal.com at 06:51pm on 2008-06-08
This brings to mind what Eric Raymond refers to as "the Rule of Least Surprise": when designing a tool, make it behave in the least surprising manner possible (for your target user group). Building a car? Install a steering wheel, not a tilt controller unrder the seat; don't switch the accelerator and brake pedals around.

To amplify your VCR example a bit: I have four VCRs, one of which only works as a tuner any more. The clocks are set. But I have to know four different procedures for setting the clock, three different sets of steps for programming them to record a show. I decided it was worth it to me, that it wasn't THAT big a deal to figure it out, but there's no good reason that I should have had to figure it out four times. (Actually, since I have four methods to keep straight, none of them completely 'stick'; I wind up figuring out all four again each time the power goes out or DST starts/ends.)

Links

January

SunMonTueWedThuFriSat
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24
 
25
 
26
 
27
 
28
 
29
 
30
 
31