Interaction design -- lecture planning.

[moshez]

I've promised to give a talk about Interaction Design for a local group of "intellectual interest" people. I have great passion about it, I have some knowledge of it -- but only some. I will be collecting links in this post, and if you have more links, research points and other miscellenia, please comment!

I plan to do all the talk design right here in this post, as in general I believe in working in the open.


http://www.interaction-design.org/

http://www.asktog.com/basics/firstPrinciples.html

http://www.ixda.org/en/

http://www.user.com/

http://www.cooper.com/

http://www.joelonsoftware.com/

http://www.joelonsoftware.com/items/2007/08/18.html

http://headrush.typepad.com/

http://www.lukew.com/ff/archive.asp?tag&interaction+design

http://www.interaction-design.org/encyclopedia/

http://moishelettvin.blogspot.com/2006/11/windows-shutdown-crapfest.html

http://www.joelonsoftware.com/items/2006/11/24.html

http://www.joelonsoftware.com/items/2006/11/21.html

http://www.joelonsoftware.com/articles/FB4.5.html

http://www.joelonsoftware.com/design/index.html

http://www.joelonsoftware.com/design/1stDraft/00.html

http://www.joelonsoftware.com/design/1stDraft/01.html

http://www.joelonsoftware.com/design/1stDraft/02.html

http://www.joelonsoftware.com/uibook/chapters/fog0000000057.html

http://producingoss.com/

Plan:
* What is interaction design?
* Definition 1
* Definition 2
* Wait, isn't that UI design? (it's the same thing. But "UI design" means you are thinking of designing your user interface. The user cares about his interaction. You commited the classic blunder of forcing the implementation on the user)
* Why is software hard to use?
* Good design principles
* Affordability
* Predictability
* Experimentability
* It is hard
* What do people expect?
* But "it's easy enough"
* Easy to implement program model
* Impedance mismatch
* Who does it?
* How is a company built: Research, Development, Marketing, Product Management
* Research: works on eliminating future barriers. Unless specifically UI barriers, irrelevant
* Development: Codes from spec. Even UI people code from spec.
* Marketing: see what is needed to win in the market, plan future of product.
* Product management: Specify features. Intermediate between marketing and development.
* OK, but who does interaction design?
* Nobody...
* (Sometimes someone does it even though it's not their job -- easier in start-ups)
* How bad is it?
* Shutdown menu
* Pilot deaths
* Are you sure dialogs
* Cell phones that don't turn on
* But when it's good, it's really really good
* iPod
* Google
* Gmail
* Affordance
* Thinking about butts
* Or hands, or fingers.
* Generating correct metaphores
* Making the user feel smart
* Experimentability
* Undo
* Eliminate dangerous features
* Make it obvious dangerous things are dangerous
* Predictability
* Just because MS does it (or Apple...)
* If it looks like a duck, it should be a duck
* Principle of least surprise
* Less important than experimentability, when they collide
* Iterative development
* Usability testing
* The 5-person rule
* Goals of usability testing
* Case studies: the shutdown menu
* Case studies: iPod clicker
* Case studies: USB port
* Case studies: PS/2 port
* Case studies: microphone port
* Case studies: mile-dimensioned targets
* Case studies: snapping and resisting windows
* Case studies: wizards
* Case studies: modal windows
* Case studies: how Scott Adams deleted 500 user comments