1.
UI for Alien Cowboys Matt Jones The Disappearing Organisation

2.
UI for alien cowboys or, easy user-centred practices for designing emerging applications

3.
Three things you’ll leave with… <ul><li>What user centred design is </li></ul><ul><ul><li>And why it is useful </li></ul></ul><ul><li>Easy ways to incorporate user -centred design </li></ul><ul><ul><li>Tricks and tips that don’t take long, and deliver results </li></ul></ul><ul><li>How to marry user-centred design with emerging technologies and methodologies </li></ul>

4.
Two (maybe three) parts <ul><li>Overview of user-centred design methods </li></ul><ul><li>Practical tips and tricks </li></ul><ul><ul><li>Working on a design exercise </li></ul></ul><ul><li>If there’s time: </li></ul><ul><ul><li>Specific challenges of </li></ul></ul><ul><ul><ul><li>Mobile </li></ul></ul></ul><ul><ul><ul><li>MMORPG Gaming/Play </li></ul></ul></ul><ul><ul><li>Some future trends </li></ul></ul>

5.
First though… What’s an alien cowboy?

6.
One thing to always remember

7.
We are Aliens.

8.
We are aliens <ul><li>We are not our audience </li></ul><ul><ul><li>Geoffrey Moore’s Adoption Curve from his book “Crossing the Chasm” </li></ul></ul><ul><li>We are not our audience </li></ul><ul><ul><li>Geeks forgive </li></ul></ul><ul><ul><ul><li>Computers, not people </li></ul></ul></ul><ul><li>We are not our audience </li></ul><ul><ul><li>Even if we are building for other builders </li></ul></ul>Geoffrey Moore’s Adoption Curve: Don Norman Remix : http://www. jnd .org

9.
“Crossing the Chasm” Geoffrey Moore’s Adoption Curve: Don Norman Remix : http://www. jnd .org WE ARE ALL HERE SOMETIMES WE ARE HERE

10.
“Crossing the chasm” Geoffrey Moore’s Adoption Curve: Don Norman Remix : http://www. jnd .org [ UNDERSTANDING CONTEXTS OF USE CREATES BRIDGES ACROSS THE CHASM

11.
First though… What’s an alien cowboy?

12.
I am a cowboy <ul><li>I am lazy </li></ul><ul><li>I like things which don’t take long but give good results </li></ul><ul><li>I like approaches, but dislike processes </li></ul><ul><ul><li>Processes or methodologies used creatively can get you to unexpected and delightful end results </li></ul></ul><ul><ul><li>But they can also become dogmatic and destructive </li></ul></ul><ul><ul><li>“ Things are useful as long as they are useful” </li></ul></ul><ul><li>I think this is pretty common (are you a cowboy too?) </li></ul><ul><li>This tutorial will focus on approaches and tips that appeal to the cowboy in me </li></ul>

13.
okay...

14.
Part 1: Overview of User-Centred Design

15.
What is User-Centered Design? <ul><li>“ User-Centred Design (UCD) is an approach to design that grounds the process in information about the people who will use the product. UCD processes focus on users through the planning, design and development of a product.” </li></ul><ul><li>Usability Professionals’ Association </li></ul><ul><li>http://www.upassoc.org </li></ul>

16.
Main Benefits

17.
Macro & Micro macro micro What to build What will solve the problem What will sell How to build How to solve the problem How to sell What will people use How will people use What/Why? How?

18.
Enlarging markets <ul><li>Inclusive design </li></ul><ul><ul><li>Design for extremes of market (old, young, less able) </li></ul></ul><ul><ul><li>Utility and desirability for everyone in between </li></ul></ul><ul><ul><ul><li>E.g. Good Grips </li></ul></ul></ul><ul><li>See your product/service in terms of an ‘ecology’ </li></ul><ul><ul><li>Apple’s iLife </li></ul></ul><ul><ul><ul><li>Arguable… </li></ul></ul></ul><ul><ul><li>Sony’s “sunrise to sunset” view </li></ul></ul>

19.
Sunrise to sunset: evolve ideas in the market Market Creation Market Penetration Market Domination NOON Market Expansion Market Saturation Market Exhaustion SUNRISE Mid morning Mid afternoon SUNSET

21.
Diagram from “Digital Dreams: The work of the Sony design centre” Paul Kunkel

22.
Benefits to Cowboys of User-Centred Design process <ul><li>Removes the power politics of development: </li></ul><ul><ul><li>Externalises issues </li></ul></ul><ul><ul><li>Allows constructive discussion </li></ul></ul><ul><li>Shared frame of reference for all team members </li></ul><ul><ul><li>User research information can introduce </li></ul></ul><ul><ul><ul><li>Shared language </li></ul></ul></ul><ul><ul><ul><li>Shared goals </li></ul></ul></ul><ul><ul><ul><li>More multidisciplinary approach </li></ul></ul></ul>

23.
Some notable approaches

24.
Some notable approaches <ul><li>Cooper </li></ul><ul><ul><li>Persona Driven Design </li></ul></ul><ul><li>ISO standard </li></ul><ul><ul><li>ISO 13407 </li></ul></ul><ul><ul><li>ISO 18529 </li></ul></ul><ul><li>UPD </li></ul><ul><ul><li>User Participatory Design </li></ul></ul><ul><li>Adaptive Design </li></ul>

25.
Cooper’s Persona Driven Design

26.
Alan Cooper <ul><li>Alan Cooper </li></ul><ul><ul><li>Persona driven design </li></ul></ul><ul><ul><li>“ Cooper's personas are simply pretend users of the system you're building. You describe them, in a surprising amount of detail, and then design your system for them.” – Meg Hourihan* </li></ul></ul><ul><ul><li>Primary personas </li></ul></ul><ul><ul><ul><li>Dictate focus, scope </li></ul></ul></ul><ul><ul><ul><li>“ Target audience” </li></ul></ul></ul><ul><ul><li>Secondary personas </li></ul></ul><ul><ul><ul><li>On periphery of target market </li></ul></ul></ul><ul><ul><ul><li>Might even be ‘anti-customers’ </li></ul></ul></ul><ul><ul><ul><ul><li>People you will never satisfy </li></ul></ul></ul></ul>* http://www.boxesandarrows.com/archives/002330.php

27.
ISO standards on Human-Centered Design

28.
ISO standards for UCD ISO 13407 / ISO 18529 <ul><li>Very high-level ‘umbrella’ definition of user-centred processes </li></ul><ul><li>A pretty useful overview: </li></ul><ul><ul><ul><li>Understand and specify the context of use </li></ul></ul></ul><ul><ul><ul><li>Specify the user and organisational requirements </li></ul></ul></ul><ul><ul><ul><li>Produce design solutions </li></ul></ul></ul><ul><ul><ul><li>Evaluate designs against requirements </li></ul></ul></ul><ul><li>Useful to quote to the sort of people who like ISO standards </li></ul>

29.
User Participatory Design

30.
UCD… or UPD <ul><li>Sometimes UCD is referred to, or seen as specialised sub-discipline: </li></ul><ul><ul><li>User PARTICIPATORY design </li></ul></ul><ul><li>A set of methods for close cooperation with end-users </li></ul><ul><ul><li>In product/service creation </li></ul></ul><ul><ul><li>User interface development </li></ul></ul><ul><ul><li>Often very good for internal / enterprise-specific projects </li></ul></ul><ul><li>Very compatible with XtremeProgramming thinking </li></ul><ul><ul><li>“ The Customer is Always Available” </li></ul></ul><ul><ul><ul><li>http://www.extremeprogramming.org/rules/customer.html </li></ul></ul></ul>

31.
Ask the users? Are you crazy?

32.
iiiiiiiiiiiinnnnnpuuuuttttt! users * The users are just one input into a successful design… biz tech

33.
Research, analysis and synthesis Users Research Analysis & Synthesis Designer(s)/Builder(s) X

34.
Designer-Centred Design…!

35.
Ask the users? Are you crazy? “ If you ask the public what they think they will need, you will always be behind in this world. You will never catch up unless you think one to ten years in advance and create a market for the items you think the public will accept at that time.” Akio Morita, Sony

36.
NOT user-centred till ‘mid-afternoon’ Market Creation Market Penetration Market Domination NOON Market Expansion Market Saturation Market Exhaustion SUNRISE Mid morning Mid afternoon SUNSET Entry with technology Drive with design Diversify with marketing, and Some UCD…

37.
Adaptive Design

39.
Stewart Brand: “How buildings learn” Sketch by Dan Hill http://www.cityofsound.com/

40.
Dan Hill: “Designing for adaptation”

41.
Adaptive Design + Emerging Tech Great basis / investment for rapid cycles of emerging tech!

42.
To sum up UCD.

43.
UCD: summing up <ul><li>Drives </li></ul><ul><ul><li>Acceptance </li></ul></ul><ul><ul><li>Makes utility obvious </li></ul></ul><ul><ul><li>Desirability </li></ul></ul><ul><li>If commercial </li></ul><ul><ul><li>Enlarges market and return on investment </li></ul></ul><ul><ul><li>Reduces risks </li></ul></ul><ul><li>If not, enlarges ‘ecosystem’ </li></ul><ul><ul><li>For emerging tech, this increases in importance </li></ul></ul><ul><ul><ul><li>If people ‘get it’ then they are more likely to play with it </li></ul></ul></ul><ul><ul><ul><ul><li>Adaptive design is the best candidate here because… </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Most human behaviour changes slower than technology – a good anchor in rapidly changing tech environment </li></ul></ul></ul></ul><ul><li>A number of approaches but with one common aspect </li></ul><ul><ul><li>Context of use </li></ul></ul>

44.
Looking out from the screen at the world…

45.
To understand people’s mental models of the world and design technology to solve their problems “ The files are in the computer?”

46.
The practical

47.
Tricks and tips <ul><li>We’re going to design </li></ul><ul><ul><li>A recipe aggregator </li></ul></ul><ul><li>Using some of the most useful tricks and tips I’ve found </li></ul><ul><ul><li>Itch++ </li></ul></ul><ul><ul><li>Market mapping and persona building </li></ul></ul><ul><ul><li>The value sieve </li></ul></ul><ul><ul><li>Use your illusion </li></ul></ul><ul><ul><li>Flowcrash </li></ul></ul>

48.
Not to be taken as a substitute for a full user-centred project… These are tricks and tips that, if you only have time to do a little design work before you build, will get you good results

49.
The Brief.

50.
The brief for the recipe aggregator <ul><li>Goals </li></ul><ul><ul><li>Can be used in the kitchen </li></ul></ul><ul><ul><li>Can be accessed in the supermarket </li></ul></ul><ul><ul><li>Can find recipes from key ingredients </li></ul></ul><ul><ul><ul><li>“ What’s left on the shelf?” </li></ul></ul></ul><ul><ul><li>Can share recipes easily with others </li></ul></ul>

51.
Caution...

52.
= No speaking alien! Use of excessive jargon, mention of RDF, XML, or anything that the benefit can’t be explained once and easily to a user (or causes geek religious wars) will be punished by a fine Which will be a beer fund…!

53.
Break... please be back at 3:30pm...

54.
The Brief.

55.
The brief for the recipe aggregator <ul><li>Goals </li></ul><ul><ul><li>Can be used in the kitchen </li></ul></ul><ul><ul><li>Can be accessed in the supermarket </li></ul></ul><ul><ul><li>Can find recipes from key ingredients </li></ul></ul><ul><ul><ul><li>“ What’s left on the shelf?” </li></ul></ul></ul><ul><ul><li>Can share recipes easily with others </li></ul></ul>

56.
= No speaking alien! Use of excessive jargon, mention of RDF, XML, or anything that the benefit can’t be explained once and easily to a user (or causes geek religious wars) will be punished by a fine… Which will be a beer fund…!

57.
Even cowboys can pass ISO standards… <ul><li>Understand and specify the context of use </li></ul><ul><ul><li>Itch++ </li></ul></ul><ul><ul><li>Market mapping and persona building </li></ul></ul><ul><li>Specify the user and organisational requirements </li></ul><ul><ul><li>The value sieve </li></ul></ul><ul><li>Produce design solutions </li></ul><ul><ul><li>Use your illusion </li></ul></ul><ul><li>Evaluate designs against requirements </li></ul><ul><ul><li>Flowcrash </li></ul></ul>

58.
Understanding context of use – real way… <ul><li>Before each the cowboy tips, I’ll outline some of the ‘pro’ methods </li></ul><ul><li>Contextual Inquiry </li></ul><ul><ul><li>A mile in their shoes </li></ul></ul><ul><ul><li>Shadowing </li></ul></ul><ul><li>Ethnography </li></ul><ul><ul><li>User diaries </li></ul></ul><ul><ul><li>Pager studies </li></ul></ul><ul><ul><li>Interviews </li></ul></ul><ul><ul><li>Build real personas </li></ul></ul>Contextual inquiry / interview by Lodestar, ltd. for BBC iCan project.

59.
Itch++

60.
Framework to ask yourself questions* Familiar Context With Others One paragraph of an experience relating to the brief for each… Alone Unfamiliar Context * This is even more useful if you can get someone else to ask you the questions and record your responses

61.
Itch++: 15 minutes <ul><li>10 minutes writing </li></ul><ul><li>5 minutes presentation </li></ul><ul><li>If you want to pair, and interview: that’s great… </li></ul><ul><ul><li>but self-organise! </li></ul></ul>Familiar Context With Others Alone Unfamiliar Context

63.
Market Mapping & Persona Building

64.
Mapping users’ characteristics practical ideas Business decision… An example from my past… working on a design for an online home improvement store

65.
Words to describe each user profile <ul><li>A: Practical, functional, does chores, room has to look okay but not confident in design </li></ul><ul><li>B: More interested in design, less confident in technical abilities </li></ul><ul><li>C: Always has projects on the go, hobbyist </li></ul><ul><li>D: Creates a look, less involved in project execution, most interested in creative, trends </li></ul>practical ideas A B D C

66.
Who are they? It helps! <ul><li>A: Mike, early 40s, depends on wife Louise’s opinion for design. Two kids, his wife is expecting a third </li></ul><ul><li>B: Jane, early 30s, has partner, busy, relies on friends and other people for advice </li></ul><ul><li>C: Jack, single, quite confident in abilities and taste. Shops around and reads lots of magazines, focusing on DIY titles: Better Homes, Changing Rooms </li></ul><ul><li>D: Lucy, single, in her 50s, out-sources doing, shops around, reads lots of magazines, style and end result oriented. Reads lots of magazines, broad lifestyle, Habitat, IKEA, BHS </li></ul>practical ideas A B D C

67.
Take personas and contexts to arrive at concepts/features for BBC iCan project.

69.
Understanding context <ul><li>Understand and specify the context of use </li></ul><ul><ul><li>Itch++ </li></ul></ul><ul><ul><li>Market mapping and persona building </li></ul></ul><ul><li>Specify the user and organisational requirements </li></ul><ul><ul><li>The value sieve </li></ul></ul><ul><li>Produce design solutions </li></ul><ul><ul><li>Use your illusion </li></ul></ul><ul><li>Evaluate designs against requirements </li></ul><ul><ul><li>Flowcrash </li></ul></ul>

70.
The value sieve

71.
A value / complexity sieve “ The feature prioritisation is based on the user research and the business strategy, along with the initial technology estimates. I like doing this prioritisation exercise in person with all the stakeholders so all viewpoints can be factored in. It’s a seminal meeting and the results guide the rest of the project.” - Victor Lombardi http://www.noisebetweenstations.com

72.
How to use the sieve <ul><li>High Complexity / High Value: </li></ul><ul><ul><li>“ It's important to include these features, and because they're hard let's address them first so we have enough time and find any unknown snags.” </li></ul></ul><ul><li>High Complexity / Low Value: </li></ul><ul><ul><li>“ They're hard and no one thinks they're important, so try to leave them out.” </li></ul></ul><ul><li>Low Complexity / High Value: </li></ul><ul><ul><li>“ Definitely include these, but give them lower priority.” </li></ul></ul><ul><li>Low Complexity / Low Value: </li></ul><ul><ul><li>“ These features can be put on a reach list, to do if resources permit. Or left until a future phase. Or you can re-examine them to see if your original values are accurate.” </li></ul></ul>

74.
Understanding context <ul><li>Understand and specify the context of use </li></ul><ul><ul><li>Itch++ </li></ul></ul><ul><ul><li>Market mapping and persona building </li></ul></ul><ul><li>Specify the user and organisational requirements </li></ul><ul><ul><li>The value sieve </li></ul></ul><ul><li>Produce design solutions </li></ul><ul><ul><li>Use your illusion </li></ul></ul><ul><li>Evaluate designs against requirements </li></ul><ul><ul><li>Flowcrash </li></ul></ul>

75.
Use your illusion

76.
‘ User Illusion’ – Alan Kay

77.
Medium and message Harry Beck...

79.
Jakob does it… “ Card Sorting to Discover the Users' Model of the Information Space” Jakob Nielsen, May 1995 http://www.useit.com/papers/sun/cardsort.html

80.
Use your illusion: 30 minutes <ul><li>5 minutes writing your imagined features to a fairly granular level, but nothing too detailed </li></ul><ul><ul><li>remember, you will be fined for using jargon! </li></ul></ul><ul><li>5 minutes arranging the cards into the system as you think it will be organised AS A USER EXPERIENCE </li></ul><ul><ul><li>STOP! We’re going to take a snapshot… this should take 5 minutes or so </li></ul></ul><ul><li>Swap your cards with someone else </li></ul><ul><li>5 minutes – organise the cards you’ve received into a system that makes sense to you, given the brief </li></ul><ul><ul><li>STOP! We’re going to take another snapshot – another 5 minutes </li></ul></ul><ul><li>Then, we’ll spend 5 minutes looking at the results </li></ul>

82.
Understanding context <ul><li>Understand and specify the context of use </li></ul><ul><ul><li>Itch++ </li></ul></ul><ul><ul><li>Market mapping and persona building </li></ul></ul><ul><li>Specify the user and organisational requirements </li></ul><ul><ul><li>The value sieve </li></ul></ul><ul><li>Produce design solutions </li></ul><ul><ul><li>Use your illusion </li></ul></ul><ul><li>Evaluate designs against requirements </li></ul><ul><ul><li>Flowcrash </li></ul></ul>

83.
Paper prototyping Courtesy Marc Rettig: http://www.marcrettig.com/

84.
Fast, cheap and out of control Courtesy Marc Rettig: http://www.marcrettig.com/

85.
“ But I can code quicker than I can draw” Courtesy Marc Rettig: http://www.marcrettig.com/ <ul><li>You can’t. Try it. </li></ul><ul><li>You don’t have to draw well – anyone can draw well enough to get results </li></ul><ul><li>You will get nitpicking at a coded prototype, not answers </li></ul><ul><li>But the biggest problem with coded prototypes… </li></ul>

86.
You will not want to destroy it…

87.
Flowcrash

88.
Using paper prototypes for rapid testing <ul><li>Design paper screens for your system </li></ul><ul><ul><li>Include buttons, drop-downs, widgets… </li></ul></ul><ul><ul><ul><li>Simulate them all with stickies for ease of repositioning and re-use </li></ul></ul></ul><ul><li>Make sure there are two of you who know how the design works </li></ul><ul><ul><li>One of you will facilitate </li></ul></ul><ul><ul><li>One of you will play the computer </li></ul></ul><ul><li>Go grab a colleague or family member who hasn’t seen your design </li></ul><ul><li>Facilitator: ask them to complete tasks based on the goals of your design </li></ul><ul><li>Computer: serve up the screens as per the ‘flow’ of the design you did. Be neutral! Emotionless! </li></ul><ul><li>Record what you learn, and redesign there and then </li></ul><ul><li>Retest! </li></ul>

89.
The end?

90.
Two (maybe three) parts <ul><li>Overview of user-centred design methods </li></ul><ul><li>Practical tips and tricks </li></ul><ul><ul><li>Working on a design exercise </li></ul></ul><ul><li>If there’s time: </li></ul><ul><ul><li>Specific challenges of </li></ul></ul><ul><ul><ul><li>Mobile </li></ul></ul></ul><ul><ul><ul><li>MMORPG Gaming/Play </li></ul></ul></ul><ul><ul><li>Some future trends </li></ul></ul><ul><ul><li>Discussion…? </li></ul></ul>

91.
Mobile

92.
Marc Rettig sums up the main challenge well

93.
Contextual inquiry is key <ul><li>Understanding the real attention deficits that your application will suffer </li></ul><ul><li>Understanding the in-between times in real life, where your service or product might be a boon </li></ul><ul><li>Understanding the audio, visual and interaction constraints your design will operate under </li></ul><ul><li>Walk a mile in mobile shoes… </li></ul>

94.
A trick pioneered by Palm / Handspring too…

95.
For mobile… <ul><li>The world is more important than the screen </li></ul><ul><ul><li>Invest in studying the world </li></ul></ul><ul><ul><li>It’s not that easy to hack </li></ul></ul><ul><li>Products and services are </li></ul><ul><ul><li>Used in social situations </li></ul></ul><ul><ul><ul><li>Study the social patterns of use </li></ul></ul></ul><ul><ul><ul><li>Social interactions more valuable that screen interactions </li></ul></ul></ul><ul><ul><ul><ul><li>Prada… a cautionary tale… </li></ul></ul></ul></ul>

96.
Further at Etech <ul><li>Christian Lindholm </li></ul><ul><ul><li>Nokia UI pioneer </li></ul></ul><ul><ul><li>“ Art-of-Logic: Experience Making, the Nokia Way ” </li></ul></ul><ul><ul><li>Track: Untethered Date: Wednesday, February 11 Time: 2:45pm - 3:30pm </li></ul></ul><ul><ul><li>http://conferences.oreillynet.com/ cs/et2004/view/e_sess/4864 </li></ul></ul>

97.
Gaming/Play MMoRPGs

98.
From a conversation with Stewart Butterfield <ul><li>Looking at “Play” as a broad category </li></ul><ul><ul><li>In addition to the activity (chess, rugby, Quake) </li></ul></ul><ul><ul><li>A way of trying on another mode of relationship or identity </li></ul></ul><ul><ul><ul><li>Children play the limits of the relationships. They have violence, sexuality, power dynamics in their games. Exploring the kinds of ways they can have relationships with their peers </li></ul></ul></ul><ul><ul><ul><li>Even if we are friends - when we play we become competitors. </li></ul></ul></ul><ul><ul><li>Control over identity is the most important control </li></ul></ul><ul><ul><li>In most apps like online banking or search the user’s character or personality is kind of irrelevant because task overrides </li></ul></ul><ul><ul><li>But in worlds of “Play” ways in which people come together (place/channel) and identify each other/self are key </li></ul></ul>

99.
UIs that get out of the way of the players and their relationships Drag and drop to establish chats and ad-hoc groups Visualising relationships in ‘heads-up’ displays From http://www.gne.net

100.
Future trends

101.
Next-gen mobile Bigger screens, more whizzy features Same old messy world.

102.
More ‘embodied’ interaction

103.
Converts… This holiday, my two sisters - who to my knowledge had never played a console game before - got addicted to EyeToy…

104.
Discussion

105.
That’s all... Thank You for your time and energy

106.
Further study: Web <ul><li>Mark Rettig: http://www.marcrettig.com </li></ul><ul><ul><li>Interaction design history in a teeny little nut shell http://www.marcrettig.com/writings/ rettig.interactionDesignHistory.2.03.pdf </li></ul></ul><ul><ul><li>Design for small screens: http://www.marcrettig.com/writings/rettig,SmallScreens.pdf </li></ul></ul><ul><ul><li>Interface Design in Seven Weeks: Marc Rettig </li></ul></ul><ul><ul><ul><li>http://loop.aiga.org/content.cfm?ContentID=83 </li></ul></ul></ul><ul><li>AdaptivePath: </li></ul><ul><ul><li>http://www.adaptivepath.com/ </li></ul></ul><ul><li>AskTog: Bruce Tognazzini </li></ul><ul><ul><li>http://www.asktog.com/ </li></ul></ul><ul><li>Carolyn Snyder on paper prototyping: </li></ul><ul><ul><li>http://www.snyderconsulting.net/paperprototyping.htm </li></ul></ul><ul><ul><li>http://www-106.ibm.com/developerworks/library/us-paper/?dwzone=usability </li></ul></ul><ul><li>UsabilityNet.org: EU funded resource centre </li></ul><ul><ul><li>http://www.usabilitynet.org/home.htm </li></ul></ul><ul><li>User-Centred Design & “Agile” methodologies: Anthony Colfelt </li></ul><ul><ul><li>http://www.colfelt.com/blog/cat_agile_development.shtml </li></ul></ul>

107.
Further study: Books <ul><li>General </li></ul><ul><ul><li>About Face, The Inmates Are Running the Asylum : Alan Cooper </li></ul></ul><ul><ul><li>Don't Make Me Think: Steve Krug </li></ul></ul><ul><ul><li>The Design of Everyday Things: Donald Norman </li></ul></ul><ul><ul><li>The elements of user experience: Jesse James Garrett (http://www.jjg.net/elements/) </li></ul></ul><ul><ul><li>Observing the User Experience: Mike Kuniavsky </li></ul></ul><ul><ul><li>Information Architecture: Christina Wodtke </li></ul></ul><ul><ul><ul><li>Christina also has a great reading list at http://www.eleganthack.com/reading/ </li></ul></ul></ul><ul><li>Mobile </li></ul><ul><ul><li>Information Appliances and Beyond: Bergman </li></ul></ul><ul><ul><li>Mobile Usability: Lindholm, Keinnonen, Kiljander </li></ul></ul><ul><ul><li>Handheld Usability: Scott Weiss </li></ul></ul>

108.
Further study: Organisations/Events <ul><li>ACM SIGCHI, the ACM's Special Interest Group on Computer-Human Interaction </li></ul><ul><ul><li>http://sigchi.org/ </li></ul></ul><ul><ul><li>CHI2004: April 24-29 th , Austria </li></ul></ul><ul><ul><ul><li>http://www.chi2004.org/ </li></ul></ul></ul><ul><ul><li>DIS2004: Designing Interactive Systems, August 1-4, Cambridge, Mass </li></ul></ul><ul><ul><ul><li>http://sigchi.org/dis2004/ </li></ul></ul></ul><ul><li>AIGA-Experience Design </li></ul><ul><ul><li>http://www.aiga.org/content.cfm?Alias=experiencedesign </li></ul></ul><ul><li>ASIST </li></ul><ul><ul><li>Information Architecture summit: March 21-23, 2003 Portland, Oregon </li></ul></ul><ul><ul><ul><li>http://www.asis.org/Conferences/IA03/ </li></ul></ul></ul><ul><li>AifIA: The Asilomar Institute for Information Architecture </li></ul><ul><ul><li>http://www.aifia.org/ </li></ul></ul>

109.
Send me questions... [email_address]