Control vs. Competency
Dec. 10th, 2006 11:26 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
elfsDon Norman wrote Emotional Design and The Design of Everyday Thing, and is famous in the design community for his thoughtful approach to physical design. But I have to take a counterpoint to his recent essay, "Simplicity is Highly Overrated". Don has a point about a new washing machine from Siemens that was even more automated, less likely to damage your clothing, than a previous model, and yet despite this incredible automation it had even more controls than the previous model. He called the UI designer at Siemens and asked him about it. "Are you one of those people who wants to give up control, who thinks less is better? Don't you want to be in control?"
And I had to answer, as Don did, "Yes, I think less is better."
I think the second question is fascinating, because I think it contains a hidden bit of misdirection: "Don't you want to be in control?" hides the question, "Control of what?"
Omaha tells me that I'm incompetent when it comes to washing clothes. There's a cheat-sheet of settings next to the washing machine that lets me know what settings are to be set for what sets* of clothes. Programming the washing machine is a competency: I don't want to have to remember all those little details so I have transferred that competency to a small sheet of paper and put it in proximity to the device it controls. The only assurance I need is to know that the paper itself is competent.
Thus the purchasing decision. "Do you want to pay more money for less control?" The assumption here is that I want to be in control of the washing machine, when what I really want is to be competent at washing my clothes. I am willing to pay more money to be more competent. If I transfer that competency to the machine itself, and have to only assess that competency once-- at purchasing time-- then I've freed up important mental resources to do something other than know about how to wash my clothes and I've reduced my own anxiety about getting it right every time I stuff clothes into the machine.
* This sentence reminds me that the word "set" has the most insanely long entry in the dictionary.
And I had to answer, as Don did, "Yes, I think less is better."
I think the second question is fascinating, because I think it contains a hidden bit of misdirection: "Don't you want to be in control?" hides the question, "Control of what?"
Omaha tells me that I'm incompetent when it comes to washing clothes. There's a cheat-sheet of settings next to the washing machine that lets me know what settings are to be set for what sets* of clothes. Programming the washing machine is a competency: I don't want to have to remember all those little details so I have transferred that competency to a small sheet of paper and put it in proximity to the device it controls. The only assurance I need is to know that the paper itself is competent.
Thus the purchasing decision. "Do you want to pay more money for less control?" The assumption here is that I want to be in control of the washing machine, when what I really want is to be competent at washing my clothes. I am willing to pay more money to be more competent. If I transfer that competency to the machine itself, and have to only assess that competency once-- at purchasing time-- then I've freed up important mental resources to do something other than know about how to wash my clothes and I've reduced my own anxiety about getting it right every time I stuff clothes into the machine.
* This sentence reminds me that the word "set" has the most insanely long entry in the dictionary.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
Abstractions that hide my control
Date: 2006-12-11 06:16 pm (UTC)I think I know what's really going on behind the scenes, but I wish the the labels could clearly indicate that this section on the timer knob is timed, this uses the moisture sensor, and the other half of the knob repeats those settings at a different tumble speed, and that the radio buttons are temperature selection.
Or, if it's really the case that I never want to mix and match, consolidate it all into one setting so I don't have to choose "permanent press" in two places, but don't go mid-way and end up hiding functionality from me because the abstraction is allegedly easier to understand.