So I was at a portfolio presentation of somebody who was interviewing at MAYA for a Senior Interaction Designer's position. He talked about how a set of graphics toolkit was developed to be easy to understand by allowing the tutorial for the toolkit to guide the design. What that means is that you'd write the tutorial FIRST and make it extremely simple and clear for the novice user to understand, THEN develop the toolkit based on the tutorial. If the tutorial becomes too convoluted or lengthy your design needs to change. Kinda interesting in a way cuz I think that directly ties into what happens when one does test-first programming in eXtreme programming situations. I just might make this another requirement for myself. :)


back to the list of latest entries


That sounds like what Don Norman was saying in "The Invisible Computer"--write the manual for a device first, and try to make it fit on one page. The one thing that he helped bring into the world at around that time, the HP CapShare 910/920 scanner, does pretty well in that respect. It’s pretty well-designed, and even shows clear animated instructions on its screen. It was didn’t do that well commercially, but I could apparently make 100% profit if I felt like selling mine on eBay, so I guess he’s been somewhat vindicated. (631)

Joe Hughes - 5/19/2003 10:13:00 PM [ 205.201.10.70 ]


Name
Email
Homepage
Comment
Remember my information