Designing FOR User Experience

Notes de l'éditeur

1. Thanks to Ryan Solutions, Inntopia, and mTrip Thanks to the ski industry
2. It’s a relationship. It’s pervasive – it colors future interactions Can’t be completely controlled
3. Designing for UX is a balance between sweating the big stuff and the small stuff.
4. Not “affordable”.A knob affords twisting and pushing. Which is different than opening a door. That’s function.
5. Doing it right: Flickr, Vimeo, Mailchimp Shout out to Jay Peak: ads, door hangers
6. Sympathy creates new standards: open-source technology, responsive web design, gestural interfaces Help new guests find their way to the hill, from home, from the highway, from the parking lot.
7. People FREAK OUT when things change. Gmail’s about to change to focus more on the mail experience.
8. Everyone’s an expert. There’s no one solution. Let the numbers decide.
9. HUGE challenge. Design, development, budget, Q.A., content strategy. I’m not here to sell you on an approach.
10. Help the user. Guide the user. Don’t Trap the user. Quality of interactive experience plays a role in purchase decisions. Has a lasting psychosomatic impact user’s ultimate satisfaction with the product.
11. Make sure your team feels empowered to improve UX. Provide feedback that speaks to specific rationale. “Because Bob likes it.” is NOT a good reason to do something.
12. This conversation has died down a bit. But it’s worth noting.
13. Has become the standard for modern web design. But thinking critically about it helps produce an better end result. Don’t default to it.
14. Browsing on mobile is only ONE possibility. What about arriving from a social media app, or email link? Many sites and blogs are being built mobile-only.
15. Two different animals. But you cannot afford to ignore your mobile web presence. An app alone is not a mobile strategy. Can they work together?
16. We’ve been doing this all along. We just didn’t know it. Wordpress widgets are another example.
17. We’re actually not using as many graphics these days anyway. CSS effects, image sprites, 24-bit pngs (alpha channels), flexible background images.
18. We got really good at designing with Helvetica. Reduces load time and workarounds, but creates a slew of new issues.
19. Where do we start.
20. This is becoming a standard part of your research process. Plenty of dev folks here to help with analytics.
21. What can you infer from analytics? What anecdotal evidence do you have?
22. You don’t know what every user needs. But you can build a few common scenarios and build a flow to suit.
23. I know, I know. Navigation grows out of control for a number of reasons. This is your chance. Don’t blow it!
24. Not a huge difference, but a style guide can be strictly visual, while a pattern library is usually coded, contextual, semantic.
25. New methods, new challenges, new roles.
26. Let’s talk about what you can do to prepare for a redesign.
27. I start my project kickoffs with this question. Other questions: Why should a guest choose you? Why would a guest NOT choose you? What could cause this process to fail? Who are the stakeholders? Who’s doing day-to-day maintenance? What are their proficiencies?
28. Don’t bury your head in the sand. You know your organization. Be realistic. Restrictions are fine. They give us structure. As a designer I don’t mind having my hands tied. Go ahead. Please. Tie my hands.
29. Content Strategy is a buzz word too, but for good reason. Someone has to figure out how to tell the story.
30. Copywriting isn’t just the body of the page. It’s navigation. It’s helpful calls to action that set a proper and honest expectation for an action. (affordance)Don’t say “submit” on a button. Who the hell wants to submit? Say “Save now” or “Next Step” or “OK I’m Done”. But don’t be too cute either.
31. Make a guest feel safe. Confident. Secure. Reduce their instinct to panic and they’ll enjoy their time more.
32. Good Design can only happen once you’ve covered all the angles.
33. Thanks.