4 ms·

"I really value unfiltered end user input. No third party customer contact is going to tell you that the user looked for "Export" under the "File" menu instead

"I really value unfiltered end user input. No third party customer contact is going to tell you that the user looked for "Export" under the "File" menu instead of where you had it the very first time they used the product. You have to watch over the users shoulder of have video." To clarify, the users first impression or actions are a one time only event that you want to capture as a developer because they won't do it the same ever again. The analogy I use is: Suppose the carpet on the door sill of your cubical is unglued so it sticks up a little. The very first time you walk over the threshold you may trip. After that, you unconsciously lift you foot a little higher every time you go into you cubicle. In your role as a product designer, you want to avoid "tripping" the user if at all possible. When I'm working on a GUI, I want it to be "invisible" to the user - it just works. I rarely succeed 100%, but I try. The developer who says "the user is doing it wrong" should re-access their attitude. (I've developed CAD programs, solid modelers, oscilloscopes, etc. Basically, tools for technical people.)

DJHenk 6y ago
I think the amount of times the user is allowed to trip should be proportional to the intensity with which the user is going to use the tool. If the tripping enables advanced use, of course, which is not the case in your example. First time use is completely different than prolonged use. Efficient use is not necessarily the same as ease of discovery. The first time I rode a bike, I fell off. Does that mean bikes are badly designed? I get the feeling most designers who make an effort only look at that first time use. I get it, if the user comes around only once a month, your product should be super easy en intuitive. But if it is used daily, your product is a tool and is allowed to require skill to master. If the end result is better in some way. Either because it is more efficient, or because it takes time before one sees that there is actually more logic in that interface than you thought the first time you used it.

DJHenk 6y ago

I think the amount of times the user is allowed to trip should be proportional to the intensity with which the user is going to use the tool. If the tripping enables advanced use, of course, which is not the case in your example. First time use is completely different than prolonged use. Efficient use is not necessarily the same as ease of discovery. The first time I rode a bike, I fell off. Does that mean bikes are badly designed? I get the feeling most designers who make an effort only look at that first time use. I get it, if the user comes around only once a month, your product should be super easy en intuitive. But if it is used daily, your product is a tool and is allowed to require skill to master. If the end result is better in some way. Either because it is more efficient, or because it takes time before one sees that there is actually more logic in that interface than you thought the first time you used it.