Slashdot Mirror
Shuttleworth Suggests 1-Way Valve For User Experience Testing
darthcamaro writes "No surprise but Ubuntu's Mark Shuttleworth has come out swinging in favor of the Linux desktop. Speaking at Linuxcon yesterday he detailed the things that he thinks Linux requires in order to win the desktop wars. Those include: co-ordinated software releases, better quality and design, some user experience testing and oh yeah, a dose of 'shut the f*** up' too. During his keynote, he extended an invitation to any open source application to submit their software for testing by user-experience experts. The sessions would be recorded for posterity, and the developer would not be able to interact with the user. "'If the developer is in the room, they have to say nothing. It's the shut the f*** up protocol,' Shuttleworth said. 'You sit and watch someone struggle with the software that you've so lovingly produced.'"
I've done a bit of software dev here and there, and I've never had the luxury of being near the users when they first prop it open.
For that reason, I've developed a habit of showing a beta to a nearby co-worker, or a friend, and ask them "Check this out."
And when they say "What is it?" - I haven't done my job right.
I wanted to tell NetworkManager to do something specific (IIRC, use a specific DNS server rather than the one handed out by the DHCP server on my DSL gateway, but it's been a year or so) and couldn't. When I opened a ticket about it, it was closed WONTFIX with the notation that the idea behind it was zero-configuration and adding the ability to configure it to do this was therefore unacceptable.
I want gnome-terminal not to eat my right-clicks. People have been asking for that for *years* and are constantly told that the Gnome developers know better than they do about what they need.
... as a developer.
They basically have labs with one-way mirror. User is left alone in a sound-proof room and given a set of tasks to perform. Everything is recorded (including facial expressions and sound), and any developer can take a look at the test either from the adjacent room or from his/her workstation (using Windows Media Player). The only input the user gets is when he gets so confused he can't accomplish the task from the list. In which case the person conducting the test just says "next task" and that's it.
The experience is really humbling. You just realize that people out there are FAR, FAR less experienced with computers than you thought, and even working their email client is a challenge for most.
You make your assumptions on the basis of what's convenient for you. Guess what, people out there are not you, and what's good for you is torture for them (the inverse is often true, too).
We ended up redesigning the entire chunks of the UI sometimes, some features got cut, some scenarios overhauled. And in the end we still didn't do enough of usability testing (IMO), but such is life in commercial software development - you work against an arbitrary schedule.