1
Q
What is UX?
A
What it feels like to use a product or system
2
Q
3 types of design that make up a great product
A
- Functional Design
- Aesthetic Design
- Experience Design
3
Q
3 ingredients to a successful product
A
- Viability
- Feasibility
- Desirability
4
Q
Viability in product terms
A
A product must make money or save money for a business
5
Q
Feasibility
A
A product has to be buildable by your own technical team or an external team
6
Q
Desirability
A
There has to be a need or a want for the product. It has to be solving a problem and make the users want to reuse the product.
7
Q
How do you identify desirability
A
- Identify if there is a problem / need for the product
- Ensure the product is ACTUALLY solving a problem
- Ensure the product solves the problem in a way that creates a great experience for the user. A product cannot just solve the problem functionally.
8
Q
4 steps in a high-level UX process
A
- Research
- Design
- Build
- Test.
9
Q
3 main steps in design cycle before building the product
A
- Design
- Prototype
- Validate
10
Q
Benefits of design process
A
- Creates a clear vision
- Easy to visualise product in high fidelity
- Ideas can be iterated more cheaply in the design stage than trying to make amendments are the build stage
11
Q
Considerations when adding features
A
- Each new feature add complexity and makes it less intuitive
- Can make an interface become cluttered and crowd out important features.
- Features must be well designed for a product to be easy to use.
- Don’t add features for the sake of it, features should be limited to what is required.
12
Q
Dangers of features
A
- Features add complexity
- Features must be designed - adding time and money to a product
- Features must serve a purpose and solve a genuine problem.
13
Q
Problems with software development
A
- Too much focus on features and not on genuine user goals
- Failure to follow the proper design process
- Failure to produce high fidelity designs
- Failure to prioritise
14
Q
A successful product must…
A
Solve a genuine problem and be better than the existing solutions.
Follow every step of the product development lifecycle.
15
Q
A product must be designed with….
A
clear user goals in mind. A clearly defined vision.
16
Q
Software projects commonly fail due to….
A
No research and no design.
This can lead to large cost and time overruns.
17
Q
Benefits of low fidelity design
A
- Reduces ambiguity - creates a clear vision for all involved
- Allow for designs to be validated
- Reduces risk of product failure
18
Q
A use case is a ….
A
potential way in which a user may use your product
19
Q
An edge case is a ….
A
rare use case that does not happen frequently
20
Q
A product designer must prioritise…
A
the most common use case. Features to facilitate this use case must be front and centre and stand out to user.
Edge cases must be given less priority in the design process.
21
Q
Progressive disclosure…
A
Only give user the information and features as and when they need it. Do not overload them.
22
Q
Rules for prioritising:
A
Focus on the things that most people do most often. The features must be the most prominent on the product
23
Q
Design Target (3 most important things to know about your user when designing a product)
A
Goals
Context of use
Behaviours
24
Q
Paradox of Specificity
A
Design for a small number of use cases. Less worked involved and a more specific product is created.
The cabin bag is an example of a product designed for a small number of uses cases but ended up having huge mass market appeal.
Users prefer simple products that are really good at just doing one thing well.
25
Mental model
A users idea of how a product should work.
The design model must match a user's mental model.
When a user's mental model and the design model of a product do not match, it leads to friction between the user and the product
26
The two types of research data are:
1. Quantitative data
2. Qualitative data
27
Quantitative data
Quantitative data is measurable in numbers and by graphs, producing statistical data
Structured, Numerical, measurable
Gives a broad insight
Objective
28
Examples of Quantitative Research
1. Google Analytics
2. A/B Testing
3. Multiple choice survey questions
29
Qualitative data
Unstructured data, not measurable, provides good user's insights
Subjective, interpretive
Smaller sample sizes
30
Examples of Qualitative Research
1. Usability Testing
2. Open-ended survey questions
3. Focus groups
31
Remember ...
You are not the target audience for your product!
You have too much bias and have too much expert knowledge of the product
32
Assumptions are...
dangerous!
Don't assume your user knows everything you do. Assumptions need to be validated.
Less assumptions made means less risk.
33
Contextual inquiry is
observing real users using a product as the naturally would.
E.g A family using Heinz ketchup at home
34
Observational research...
is more powerful than listening to users talk about a product.
35
Shallow research leads to...
shallow insights.
36
In user research surveys...
avoid asking users opinions!
37
In surveys don't ask
leading questions!
This leads to bias
38
Usability testing
the best way to assess the quality of user experience.
Better to observe than listen!
39
Benefits of usability testing
1. It is the best way of assessing the quality of a user experience
2. Presents products from the user's perspective/view point
3. Unites stakeholders behind a common cause
4. Challenges / validates any assumptions that have been made
5. Produce a variety of user research data
6. Helps build a consensus about features amongst a product team
40
What can you learn from usability testing?
1. What a user is trying to do (Primary, secondary and tertiary goals)
2. What users do (behaviours)
3. The context of use
4. How the product is helping users achieve their goals
5. How the product facilitates common behaviours
6. Pain points in the product
7. How our product compares to competitors
8. Determine if the product is desirable through user's reaction
41
Conversion rate
The percentage of users to a website that perform a specific task
e.g making a transaction or subscribing to a newsletter
42
Examples of test objectives
1. Determine why conversion rates are below average
2. Why people are dropping out during certain processes
3. How we can speed up our booking process / checkout etc
4. Determine why up-sell and cross-sell modules are under performing.
43
Benefits of online surveys
1. Easy way to gather data
2. Both quantitative and qualitative data obtained
3. When a large number of people respond it's a powerful tool
4. Unambiguous (not subjective) - when well structured appropriate questions have been asked
5. Cheap and easy to run
44
3 golden survey questions
1. Why did you visit this website / use our app today?
You can learn goals from this
2. Were you able to complete your task today? If no, why?
Are people able to do what we want them to be able to do on our product
3. What improvements would you make to our website?
45
Best time to present survey on the website
1. After the user has completed a couple of tasks
2. At the end of the process e.g after checkout
DON'T ask your users to do something immediately
46
Likert Scale
Strongly disagree
Disagree
Neither agree nor disagree
Agree
Strongly agree
47
Survey advice
1. Ask golden questions
2. Never ask more than 10 questions
3. Keep questions on one screen / page
4. Don't ask redundant questions - only ask genuinely useful questions
48
Depth Interviews are:
1-1 conversations with real users / target users
49
Depth interview objectives:
1.Understand user goals / problems
2. Understand context of use
50
What not to ask in depth interviews
1. Product / design feedback
2. Things they might do in the future or hypothetical questions
51
What to ask in depth interviews
1. Ask about their lives and problems
2. Ask about specific things they did in the past
52
Who you should conduct a stakeholder interview with
1. Anyone with a stake in the project
2. Anyone feeding requirements
3. Anybody who provides sign off
53
Purpose of stakeholder interviews
1. Determine what the business problems this product will solve
2. Determine what business goals this product is expected to help us achieve
54
Objectives of a stakeholder interview
1. Understand the business
2. Understand the business goals
3. Understand problems with the current product
4. Understand the competitive landscape
5. Build relationships with stakeholders
55
Stakeholder brief
1. Write a summary after the meeting
2. Focus on what was agreed
3. Call out any contradictions for discussion
4. Get it signed off after resolving contradictions
Benefits:
1. Gives your project focus, clarity
2. Shows stakeholders you are listening
3. Can refer back to this document in times of back-out
56
Card Sorting
Participant organises content into groups that makes sense to them and gives the group a label
- more than one group
- no groups called "Other' "Misc" allowed
Used to understand a user's mental model
57
Benefits of card sorting
1. Understand users mental models
2. Understand users vocabulary and the terminology they use
3. Gives you confidence - that the website or product will make sense to users as it is based off real user feedback
58
Closed card sort
Content groups are already labelled - this is used to test users mental models and that they sort the products into the expected categories
Used to validate / invalidate structure
59
A/B Testing
When 50% of users visit a site give show them Option A and when the other 50% visit show them Option B
After a certain amount of time has pasted, check to see which option had the greatest number of conversions
60
Multi-variant test
When two or more elements are changed
Check which individual elements / combinations produce the greatest results
e.g changing a button, image, CTA
61
Benefits of A/B testing
1. Facilitates improvements, optimisation
2. Encourages experiments
3. Validates assumptions (or not)
4. Data-driven design
62
Competitive Benchmarking
Reviewing competitors to:
1. Understand how they are solving the user problem
2. Understand what they are doing well so that we can emulate (copy)
3. What are they not doing well that we could improve
4. What conventions have been established that we need to follow
63
Categories
Before benchmarking decide what categories you want to focus on such as:
Homepage
Search and select
Entering details
(Airline Example)
64
Heuristics
Considered as
- General rules of thumb
- Characteristics of best practice
- Criteria to measure against (measure the quality of our product)
65
Heuristics: Software should be polite
1. Software should be interest in me
2. Software should be forthcoming
3. Software should be self-confident
4. Software should have common sense
66
Heuristics: Usability Heuristics
1. Visibility of system status
2. Match between system and the real world
3. Freedom and control
4. Recognition rather than recall
67
Heuristics: The reservoir of goodwill
1. Don't force me to do it your way
2. Save me steps where possible
68
Heurisitc evaluation
Rate your software in terms of each of the heuristics, giving it a score out of 5 and adding in a comment where it fails to meet these standards
69
Software should be interested in me
Software should be personal
Software should know my name
Learn my preferences over time
Bad Example: Gmail doesn't recognise my name or auto-suggest it at the end of your email
Gmail doesn't recognise that you've sent emails to a friend outside your organisation multiple times - still raises alert that this account is outside of your org
70
Software should be forthcoming
Bad Example: ATM waited till after the user had selected €20 to tell that that there were no €20 notes available
ATM did not provide the reason why or tell the user what WAS available
- User should not have had the option select unavailable amounts
- ATM should have presented what options were available
71
Software should be self-confident
User should not be constantly presented with dialogue boxes asking the user if they are sure after they've completed an action e.g deleting a sheet from excel
Good Example: Google Drive - when a user has deleted something they are given an feedback confirming it has been deleted and an option discretely at the bottom of the screen to undo this
Software should be confident - not always assuming the user has made a mistake
72
Software should have common sense
E.g Irish Rail website doesn't assume the user wants to collect their tickets from the station they are departing from
73
Visibility of system status
Software should indicate to the user what is going on / how far in a process it is
Good example: Gmail has "Sending..." appear at the top of the screen after the user has hit sent on an email followed by "Your message has been sent"
AppStore: shows a progress bar, download status and percentage of download
Software should provide user an indication of progress
74
Match between system and real world
1. Don't use terminology that users are not familiar with - system must use language the user can understand
2. Don't provide user with excess jargon
E.g receipt has too many data points (Gross tax etc) - confuses user by providing too much data
75
Freedom and Control
1. If user makes mistakes - they should not be punished
Bad example: clicking the back button on a banking website - user gets kicked out of session for security reasons - user should have an option to go back without being removed from session. This is frustrating for the user
Goof example: User sheets allows user to undo an action e.g when they've deleted a file
2. The software should never lead the user to a dead end - point where they cannot take any further action
76
Recognition rather than recall
User is more likely to recognise something than recall it
Don't force your user to recall specific information
Example:
1. Provide a picture in a contact list - easier to recognise who to call
2. Banking app: when viewing a specific account don't just provide the 4 final digits, also provide a bank balance to make it easier for the user to recognise which is each account
77
Don't force me your way
Important for a software to maintain/increase goodwill with the user
i.e don't inconvenience the user for no good reason
Example: Don't force the user to format data
Software should reformat it for the user
e.g formatting dates / phone number blank spaces
This will irritate user and diminish goodwill
78
Don't waste my time
Saving user steps where possible with increase users goodwill with a software
Users are busy and multi-tasking - won't give software 100% attention
Bad Example: Amazon - all credit card info and billing and delivery address info is all based in Ireland, yet when setting up a new delivery address Amazon defaults to the United Kingdom - user has to scroll through a long picker to select Ireland - takes time and many additional steps for the user to have to scroll through that list
E.g Otterbox UK setting address automatically to Andorra on the GB UK site
Good Example: Kayak booking app - automatically sets departure location to current location
Bad Example: FT times: doesn't provide user with correct keyboard when entering email address
UX
flashcards
Decks in class (9)
# Cards
