Plunging into the waters of UX

Size: px

Start display at page:

Download "Plunging into the waters of UX"

Morgan Parker
5 years ago
Views:

1 Plunging into the waters of UX Maja Engel TCUK 2017

2 UX vs. UI design UX is a journey UI design and technical communication are vehicles for that journey «things» that the user can interact with A UI without UX is like a painter slapping paint onto canvas without thought; while UX without UI is like the frame of a sculpture with no paper maché on it. A great product experience starts with UX followed by UI. Raul Varshney, Foster.fm

3 UX Functions Aesthetics Emotions

4 People don t want a quarter inch drill bit. They want a quarter inch hole People don t care about tools Theodore Levitt They care about goals they can accomplish with these tools!

5 So why products fail? Poorly defined requirements Poorly articulated goals Poor communication Stakeholder interference (usually happens when the first two points are badly defined)

6 Features vs. Goals 80% of users use 20% of features

7 More complex technology = more features BUT Features are expensive so they must add value SO Don t add features and hope someone will use them First figure out the user s goal

8 Prioritize! If everything seems equally important The solutions are not problemtailored Same importance given to the majority of users and edge cases SO Users get annoyed and frustrated

9 Consider the context! Who is the user? What is the social and physical environment of use?

10 Don t assume you re not the user USER RESEARCH (or at least test your assumptions)

11 Behavioural (what people do) Usability testing Qualitative Quantitative Interviews Online survey Attitudinal (what people say they do)

12 Quantitative research Make a survey and send it to a mailing list great starting point if you have no information at all PROs reveals what happens easiest way to gather some info measureable and statistical cheap CONs only proves theories and assumptions does not reveal why something happens large samples required

13 Qualitative research Give a task to the subject and observe how they solve it PROs reveals what happens and why great amount of detail small samples required observe user s behavior and interaction with product CONs takes time and effort to prepare, conduct and analyze subjective and interpretative

14 Research analysis spot behavior patterns (focus instead of edge cases) identify goals and pain points (and thus problems) prioritize things to do (and thus organize production)

impact total allowed points per column = number of features x 3 if column

15 Prioritization matrix score 1-5 per feature for each column (1 =bad, 5 = good) features with the highest scores are the easiest to do and have the biggest impact total allowed points per column = number of features x 3 if column score is higher, review points (it means you ve given similar importance to everything)

16 Flow diagram I begin here I have to do this I reached my goal Make a storyboard Include screens, screen states, compulsory and optional actions

17 6 UX Design Principles Consistent and Conventional Affordances Perceivable and Predictable Fitt s Law Constraints Feedback

18 Consistent and Conventional Don t try to establish new conventions (limited pool of users) Don t underestimate habits Reduce mental effort user should not be wondering if different actions/words mean the same thing

19 Affordances controls (for example, buttons, labels, drop-downs and similar) and visual clues that tell users how a system behaves Powerful can override written instructions Must be discoverable and obvious

20 Perceivable & Predictable What can a product do? What do I have to do? Where should I begin? How long it s gonna take me? How difficult is it? What do I get from it?

21 Perceivable & Predictable Once they learn, make sure users don t have to learn the same thing all over again Avoid surprises or lack of clarity If users can t see a feature they will probably not use it

22 HOW? Chunk information in smaller bits Use field labels Align everything (shortest path to completion) Call to action Visual hierarchy (size, position and colour of elements

23 Fitt s Law Easier and faster to hit larger targets closer to you than smaller targets further away

24 Closely related to Hick s Law The more the options, the longer the task completion

25 Constraints (positive) Limit the number of things the user can do and see to minimize distractions. Each extra piece of information diminishes the importance of what is really important.

26 Feedback (to the user) Let the user know whether what they are doing is ok or not, or that they can go to the next step Users like to know what s going on HOW? micro-feedback (progress bar, breadcrumbs, hints) error handling (what went wrong, where and how to fix it)

27 UX Design Process Checklist 1. Research 2. Define problem 3. Prioritize 4. Map the action flow 5. Design 6. Prototype 7. Test 8. Go back to where the test reveals problems

28 UX requires TEAMWORK

Thank you for your attention Useful resources https://material.io/guidelines/ https://developer.apple.

29 Thank you for your attention Useful resources Don't Make Me Think, Revisited: A Common Sense Approach to Web Usability by Steve Krug Smashing Magazine Nielsen Norman Group

Interaction Design. Ruben Kruiper

Interaction Design. Ruben Kruiper Interaction Design Ruben Kruiper What do you know? What do you think Interaction Design stands for? 2 What do you expect? Interaction Design will be: Awesome Okay Boring Myself I m not a big fan... This