Your SlideShare is downloading. ×
0
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
101 Things I Learned In Interaction Design School - Web Directions South
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

101 Things I Learned In Interaction Design School - Web Directions South

3,414

Published on

My presentation from Web Directions South in Sydney Oct 2010. …

My presentation from Web Directions South in Sydney Oct 2010.

See also www.ixd101.com

Published in: Technology, Education, Design
0 Comments
8 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
3,414
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
69
Comments
0
Likes
8
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Right into it
  • (read out)Who knew that?
  • Talk inspired
  • Take that IA’s
  • Won’t find in UX bookI should have learned how to draw a line at Interaction Design SchoolPerhaps I would have learned to draw a line at Interaction Design School, if I had gone to Interaction Design School
  • There was no Interaction Design schoolThere wasn’t even really much designHow many teach you how to draw a line?
  • There was non ixd school,And…Should have been user interface engineerOr usability engineer
  • Or it wanted to be1983XXX usability engineering?
  • We didn’t talk about design.This is HCI / MMI
  • When I returned to Hiser I walked into a debate about “Are we a usability company or are we a design company”I didn’t get itOr course architecture is about engineering and design not engineering vs design
  • NormanPsych 1988 -> design 2002 (post web)XXX build
  • Arhitectures Embraces the fourdiscimplinesAnother example
  • This one not such a 1:1 matchChristopher Alexander talks about this as well if I remember rightly – the path to the reward and glimpses of the reward.
  • So could we write one
  • Could it be writtenTo find out…
  • exercise
  • XXX Quote from Brian Eno
  • anaemic
  • … quality
  • XXX Example from blogIn the book – draw hierarchically
  • Another bookA house is a house is a houseFor us, the pattern of use is still shiftingIs that what we even want?I don’t think we’re at that point. Hard to imagine we will ever be.
  • XXX Example from blog
  • Need wisdomDo we have it. No we have a lack of confidence.Changing job titles. Jockying gurus.Move from engineering to design reflects a maturing of the industry (externally imposed, largely by the web)
  • Move from engineering to design reflects a maturing of the industry (externally imposed, largely by the web)
  • #69
  • Inspired by a suggestion from Dave Malouf (http://davemalouf.com/).
  • NOAt least, I don’t think so.
  • Web design is notIA is notUsability isn’tI say tricky, not hard, because these other activities can be hard if we’re measuring the amount of work.Machine – obvious cause and effect
  • XXX Example from blog
  • Machine – obvious cause and effectPixels get re-usedSame pixel within th same application (let alone across applications) has different purposes.
  • Sometimes I wish our products were made from raw materialsOr that the raw materials we do use were more apparent to us.
  • From Blog
  • Let’s get a few more under our belt?
  • Exactly applies
  • Check it out
  • 90 roll your drawings
  • Transcript

    • 1. 101 Things I (should have) Learned in Interaction Design School<br />Shane Morris (@shanemo)<br />
    • 2. How to draw a line<br />1<br />101 Things I Learned in Architecture School, Matthew Frederick<br />
    • 3.
    • 4. Design an architectural space to accommodate a specific program, experience , or intent.<br />12<br />For the drawing and description, see <br />“101 Things I Learned in Architecture School” by Matthew Frederick<br />http://www.frederickdesignstudio.com/Books/101Things.html<br />101 Things I Learned in Architecture School, Matthew Frederick<br />
    • 5. How to draw a line<br />1<br />101 Things I Learned in Architecture School, Matthew Frederick<br />
    • 6. I didn’t go to Interaction Design School<br />
    • 7. When I started out in this industry…<br />
    • 8. HCI was a science<br />amazon.com/Psychology-Human-Computer-Interaction-Stuart-Card/dp/0898598591<br />
    • 9. The 2 disciplines<br />
    • 10. Engineering vs. Design<br />
    • 11. The 4 disciplines<br />
    • 12.
    • 13. Careful anchor placement can generate an active building interior<br />For the drawing and description, see <br />“101 Things I Learned in Architecture School” by Matthew Frederick<br />http://www.frederickdesignstudio.com/Books/101Things.html<br />87<br />101 Things I Learned in Architecture School, Matthew Frederick<br />
    • 14.
    • 15. To write “101 Things I Learned in Interaction Design School”… <br />
    • 16. ixd101.com<br />
    • 17. Functionality is the enemy of usability <br />When you are handed a functional specification, it is easy to take it on face value, and then work hard to make that functionality as usable as possible. If you are really focussed on usability, then your job starts with critiquing the functionality itself.<br />
    • 18. ixd101.com<br />
    • 19. UPDATE – IXD101.COM<br />Matt Frederick Calls<br />activity<br />time<br />UXA 2009<br />UXA 2010<br />WDS 2010<br />
    • 20.
    • 21. The level of detail in your mock-ups should reflect the level of confidence in your design <br />Mock-ups are prepared as a way of exploring a particular design problem, and in order to communicate your thoughts on a solution to important stakeholders (i.e. users, clients or developers).<br />In the early stages of design, mock-ups should communicate broad concepts and groupings of information or functions. Keeping the details scant at these early stages allows you to progress through iterations quickly and keeps your stakeholders from throwing the baby out with the bath-water by quibbling over colours and button placement.<br />As you progress towards a final design, mock-ups should be rendered in increasingly higher fidelity so that the full detail of your approach is exposed<br />
    • 22. Approach vs. Technique<br />
    • 23. The timeless way of…<br />
    • 24. Play tricks, don't wait for a full-house <br />Deciding when your design is mature enough to put in front of a client is always difficult. Unfortunately, there is a natural tendency to err on the side of holding off for longer than we should.<br />All other things being equal, you should expose your design earlier rather than later - in fact, earlier than you feel comfortable with.<br />Even if you have problems with aspects of the design, it is better to bring your stakeholders over to your side of the problem sooner.<br />To use an analogy from card games; play your design out in small "tricks" don't wait for a "full house", lest you be left with a hand full of great - but now useless - cards when the project moves on without you. <br />
    • 25. To write “101 Things I Learned in Interaction Design School”… <br />
    • 26. The getting of wisdom<br />
    • 27. The getting of wisdom<br />design<br />Design<br />
    • 28. Random unsubstantiated hypothesis<br />For the drawing and description, see <br />“101 Things I Learned in Architecture School” by Matthew Frederick<br />http://www.frederickdesignstudio.com/Books/101Things.html<br />69<br />101 Things I Learned in Architecture School, Matthew Frederick<br />
    • 29. Like buildings, applications break at the joins <br />It’s the journey between pages or screens, not the pages and screens themselves, that can cause the most problems for users. <br />Plus - problems with the journey are the most expensive problems to fix.<br />Design the journey between states first, before designing the states. <br />
    • 30. Have we achieved wisdom in interaction design?<br />NO<br />
    • 31. Interaction design is hard!<br />www.vintagecalculators.com<br />
    • 32. Separation of action and reaction <br />The greater the distance between a user’s action and the system’s reaction, the more you need to emphasise the relationship between the action and the reaction.<br />Distance can be measured in space, or in time.<br />
    • 33. Interaction design is hard!<br />www.vintagecalculators.com<br />
    • 34. Do you know where your pixels come from?<br />Powerhouse Museum Collection<br />http://www.powerhousemuseum.com/collection/database/?irn=28769<br />Gift of Australian Consolidated Press under the Taxation Incentives for the Arts Scheme, 1985<br />
    • 35. Interaction design is hard…<br />BUT we are soft!<br />
    • 36. Architects don’t get to usability test<br />“You can use an eraser on the drafting table or a sledge hammer on the construction site.“<br />Frank Lloyd Wright<br />http://quotesondesign.com/frank-lloyd-wright/<br />
    • 37. Industrial designers don’t get to A/B test<br />
    • 38. Interaction design is hard…<br />BUT we are soft!<br />
    • 39. Landmarks help us know where we are going, and where we have been <br />When we explore a new city, landmarks break our journey into stages. At each landmark we stop, assess where we’ve been, reorient ourselves, and set out again.<br />Landmarks can help with any journey. On a web site, arriving at a page that is markedly different to others marks the end of a stage of the interaction, or the beginning of a new stage. <br />Memorable landmarks that stand out from their surrounds help us form a mental model of where we have been, and where else we can go.<br />
    • 40. To write “101 Things I Learned in Interaction Design School”… <br />
    • 41. To write “101 Things I Learned in Interaction Design School”… <br />…we need greater confidence<br />http://www.cafepress.com.au/jenkramer.145505508#<br />
    • 42.
    • 43. Design with models<br />For the drawing and description, see <br />“101 Things I Learned in Architecture School” by Matthew Frederick<br />http://www.frederickdesignstudio.com/Books/101Things.html<br />72<br />101 Things I Learned in Architecture School, Matthew Frederick<br />
    • 44.
    • 45. Four new books!<br />
    • 46. Roll your drawings for transport or storage with the image side facing out<br />For the drawing and description, see <br />“101 Things I Learned in Architecture School” by Matthew Frederick<br />http://www.frederickdesignstudio.com/Books/101Things.html<br />90<br />101 Things I Learned in Architecture School, Matthew Frederick<br />
    • 47. Thank you<br />101 Things I Learned in Architecture School<br />Matthew Frederick<br />Shane Morris<br />Automatic Studio<br />shane@automaticstudio.com.au<br />@shanemo<br />Ixd101.com<br />

    ×