Everyday User experience

942 views

Published on

5 principles I've generally found to be true in designing products for the web and mobile. A slight update/digest version of Creating Positive User Experiences - a talk John Zeratsky and I developed in 2010.

Published in: Design
2 Comments
1 Like
Statistics
Notes
  • It occurs to me that a LOT of the detail in this deck is missing in notes and floating in talk-space. All credit for 1XUX goes to T.A. McCann – at least he's the first person I've heard put it that way. I just wanted to amplify the point while I had the bully pulpit.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Great concise and to the point deck, love the '1XUX', hadn't seen that one before.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
942
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
0
Comments
2
Likes
1
Embeds 0
No embeds

No notes for slide
  • - all that stands between you and 10 mins of breaktime\n- this material is derived from a talk given with john zeratsky a couple years ago at Google I/O; built from years of experience designing web apps from the ground up at both startups and large cos\n- when you create a product you create a UX; might as well make it a good one\n
  • - met my eventual startup cofounders at Andersen; usability, UCD\n- lessons learned from those experiences lead to these principles\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • - engineering is opinionated about user experience\n- ux is technical enough to earn cred with eng\n- PM “walks to the whiteboard” with UX and helps the whole org understand that process is design-driven because they buy into it too\n
  • JZ\n\nCredit to Erika Hall (Designer at Mule Design in SF)\n\ntalk on "Copy as interface"; copy, or text, makes up the majority of the interfaces that we create, but we don't really think about that text very much\n\nshe talks about being "considerate and respectful"\n \nThis is common sense; Basic principle is to design things so that they are courteous and friendly. Put yourself in the mind of your user and walk through your application. which things would piss you off? annoy you?\n1XUX (TA's concept)\n \nContinued on next slide... \n\n
  • \n
  • politeness isn’t just language. It’s convention. Would you start a conversation by walking up to someone and saying what’s your birthdate, home address, and would you like to receive occasional email updates from me?\n\nstripe - payments processing system targeted at frustrated developers\nyou can explore every aspect of the core system without creating an account.\n
  • tripit.com\nstunning insight\nno barriers to entry or proprietary tech here; just legwork\n
  • - Data Liberation\n- FeedBurner redirection\n
  • \n
  • \n
  • People don’t know what you expect - but they know how to get “close”\nDon’t strive to make servers happy – make users happy\n
  • \n
  • \n
  • \n
  • \n
  • Everyday User experience

    1. 1. EVERYDAY USER EXPERIENCE 5 PRINCIPLES FOR YOU +YOUR PRODUCTS TO EMBODY Matt Shobe @shobe
    2. 2. WHY I DO WHAT I DO
    3. 3. SPEEDPERSONALITY AGILITYPOLITENESSPREPARATION
    4. 4. http://www.flickr.com/photos/ajmexico/2394606162/ SPEED IS (NEARLY) EVERYTHING Principle 1: Be Fast.
    5. 5. “Speed is the most important feature. If your application is slow,people won’t use it. I see this more with mainstream users than I dowith power users. I think that power users sometimes have a bit ofsympathetic eye to the challenges of building really fast web apps,and maybe they’re willing to live with it, but when I look at my wifeand kids, they’re my mainstream view of the world. If something isslow, they’re just gone.” — Fred Wilson (Union Square Ventures)     http://bit.ly/fw-speed
    6. 6. http://www.avc.com/a_vc/2011/09/minimum-viable-personality.htmlPERSONALITY IS PERMISSION Principle 2: Be yourself.
    7. 7. Heavy symbolism, manAGILITY ASSUMES THE UNEXPECTED Principle 3: Be agile. (Whatever your process, stay on your toes.)
    8. 8. “We all drive the truck”Assume all external communications will be reblogged, retweeted, otherwise laid bare.Customers demand everything, yet expect the worst. (Confound that expectation.)
    9. 9. DESIGN HAS SPRINT STORIES DESIGN COMMITS CODE DESIGN PAIR-IMPLEMENTSDESIGN SHOULDERS SUCCESS AND BEARS THE WEIGHT OF FAILURE
    10. 10. THE WHEEL OF JUSTICEProduct Management • Engineering • User Experience
    11. 11. POLITENESS IS IN SHORT SUPPLY Principle 4: Be polite.
    12. 12. 1XUX(1st TIME USER EXPERIENCE)
    13. 13. Make it easy to get started.
    14. 14. plans@tripit.comLeverage patterns people already understand.
    15. 15. Make it easy to leave.
    16. 16. PREPARATION SHOWS PATIENCE Principle 5: Prepare for failure!
    17. 17. 1 (312) 555-1212http://www.mywebsite.com/VISA 4388-5752-1234-5678
    18. 18. Kind of old school (circa 2010)
    19. 19. Responsive Design
    20. 20. Responsive Design
    21. 21. SPEEDPERSONALITY AGILITYPOLITENESSPREPARATION
    22. 22. SPEED PERSONALITY AGILITY POLITENESS PREPARATIONTHANK YOU.
    23. 23. SPEED PERSONALITY AGILITY POLITENESS PREPARATIONTHANK YOU. Matt Shobe @shobe

    ×