Notes on "Thoughts on Interaction Design"

10 views
Skip to first unread message

kelleyP

unread,
Oct 27, 2010, 11:51:09 PM10/27/10
to UX Bookclub Denver
10.27.2010 // Thoughts on Interaction Design by Jon Kolko


Next book: Modular Web Design, Nathan Curtis (Nov 17th)
Next-next book: Understanding User Experience (Jan 26th)
_________________________________________________________

THINGS WE LIKED
- liked the contributions from "guest writers"
- good description of the transition from graphic designer to
interaction designer (using design patterns...)
- good notes on collaboration & getting teams to talk/work with each
other
- learned more about Human Computer Interaction (HCI) as a formulated
process
- notes that teams should not confuse project design w/ project
implementation (ux is design & should happen before)


THINGS WE DIDN'T
- lots of thoughts, but not too tactical


NOTES
- "The Bridge Between Development & Design" was good; at CB&P,
developers are not allowed to initially say no
- CB+P does role-playing to teach team members how to talk to each
other (developers vs. designers)
- meeting management can really help get better info from the team
(don't let the developers intimidate the stakeholders)
- "You don't really understand something until you can explain it to
your grandmother." by ???
- part of our role is to dumb it down / make it as simple as possible
- we should be structuring the data closer to the user's mental model
vs. structuring it based on the system's model
- IA concept of reverse pyramid Data > Infomration > Knowledge >
Wisdom is great to keep in mind
- designers are sometimes curators of information
- web design is a little less "cool" for younger designers b/c they're
just so used to using the end product
- doing the UX work/overall strategy/vision before development starts
really aids decision-making

DISCUSSION: What's the difference b/w user experience design &
interaction design?
- some people don't differentiate between those...
- UX is a practice more than a profession; it's more a process than a
specific role
- at MapQuest the "user experience designer" title is more of a way to
bring a process into the organization; people are usually more
information architects
- all of them involve some sort of problem solving...
- on small teams, there doesn't seem to be much different
- creating the bigger vision really need to include more people
- could also be considered a communication designer - visual
communication, processes, team communication, workflows, etc...


Other books
- Snoop - about going to people's houses & workplaces
- see IXDA Colorado Group site for downloadable PDF books


ATTENDEES // What's your favorite Halloween trick or treat?
Terry (Ryan's brother) - taking candy from the kids when they came to
the door
Mike R - favorite treat = big soft sweet-tarts
Mike C - hated getting raisins
Val - loved making caramel apples
Kelley - Popcorn fresh & warm from the state-fair style popper
Ryan - thought it was weird to get cartons of orange juice when trick-
or-treating, also weird to get a beer from a neighbor (when he was 7)

Valeria Price

unread,
Oct 28, 2010, 7:06:37 PM10/28/10
to ux-bookcl...@googlegroups.com
Last night's ice breaker was about your favorite trick or treat.

Here is a dark twist of that from one of my favorite design icons.
Sean Adams of Adams/Morioka in LA.

I love his dry wit!

Also check out the "Baby Doll" post for some campy SNL fun!




--
You received this message because you are subscribed to the Google Groups "UX Bookclub Denver" group.
To post to this group, send email to ux-bookcl...@googlegroups.com.
To unsubscribe from this group, send email to ux-bookclub-den...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/ux-bookclub-denver?hl=en.


Reply all
Reply to author
Forward
0 new messages