Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

UX > Module 1,2 > Flashcards

Module 1,2 Flashcards

1
Q

What is UX?

A

What it feels like to use a product or system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

3 types of design that make up a great product

A
  1. Functional Design
  2. Aesthetic Design
  3. Experience Design
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

3 ingredients to a successful product

A
  1. Viability
  2. Feasibility
  3. Desirability
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Viability in product terms

A

A product must make money or save money for a business

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Feasibility

A

A product has to be buildable by your own technical team or an external team

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

How do you identify desirability

A
  1. Identify if there is a problem / need for the product
  2. Ensure the product is ACTUALLY solving a problem
  3. 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.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

4 steps in a high-level UX process

A
  1. Research
  2. Design
  3. Build
  4. Test.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

3 main steps in design cycle before building the product

A
  1. Design
  2. Prototype
  3. Validate
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Benefits of design process

A
  1. Creates a clear vision
  2. Easy to visualise product in high fidelity
  3. Ideas can be iterated more cheaply in the design stage than trying to make amendments are the build stage
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Considerations when adding features

A
  1. Each new feature add complexity and makes it less intuitive
  2. Can make an interface become cluttered and crowd out important features.
  3. Features must be well designed for a product to be easy to use.
  4. Don’t add features for the sake of it, features should be limited to what is required.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Dangers of features

A
  1. Features add complexity
  2. Features must be designed - adding time and money to a product
  3. Features must serve a purpose and solve a genuine problem.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Problems with software development

A
  1. Too much focus on features and not on genuine user goals
  2. Failure to follow the proper design process
  3. Failure to produce high fidelity designs
  4. Failure to prioritise
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

A product must be designed with….

A

clear user goals in mind. A clearly defined vision.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Software projects commonly fail due to….

A

No research and no design.
This can lead to large cost and time overruns.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Benefits of low fidelity design

A
  1. Reduces ambiguity - creates a clear vision for all involved
  2. Allow for designs to be validated
  3. Reduces risk of product failure
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

A use case is a ….

A

potential way in which a user may use your product

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

An edge case is a ….

A

rare use case that does not happen frequently

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Progressive disclosure…

A

Only give user the information and features as and when they need it. Do not overload them.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Design Target (3 most important things to know about your user when designing a product)

A

Goals
Context of use
Behaviours

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

Mental model

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

The two types of research data are:

A
  1. Quantitative data
  2. Qualitative data
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

Quantitative data

A

Quantitative data is measurable in numbers and by graphs, producing statistical data

Structured, Numerical, measurable
Gives a broad insight
Objective

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
28
Q

Examples of Quantitative Research

A
  1. Google Analytics
  2. A/B Testing
  3. Multiple choice survey questions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

Qualitative data

A

Unstructured data, not measurable, provides good user’s insights
Subjective, interpretive
Smaller sample sizes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
30
Q

Examples of Qualitative Research

A
  1. Usability Testing
  2. Open-ended survey questions
  3. Focus groups
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
31
Q

Remember …

A

You are not the target audience for your product!

You have too much bias and have too much expert knowledge of the product

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
32
Q

Assumptions are…

A

dangerous!

Don’t assume your user knows everything you do. Assumptions need to be validated.
Less assumptions made means less risk.

33
Q

Contextual inquiry is

A

observing real users using a product as the naturally would.

E.g A family using Heinz ketchup at home

34
Q

Observational research…

A

is more powerful than listening to users talk about a product.

35
Q

Shallow research leads to…

A

shallow insights.

36
Q

In user research surveys…

A

avoid asking users opinions!

37
Q

In surveys don’t ask

A

leading questions!

This leads to bias

38
Q

Usability testing

A

the best way to assess the quality of user experience.

Better to observe than listen!

39
Q

Benefits of usability testing

A
  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
Q

What can you learn from usability testing?

A
  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
Q

Conversion rate

A

The percentage of users to a website that perform a specific task

e.g making a transaction or subscribing to a newsletter

42
Q

Examples of test objectives

A
  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
Q

Benefits of online surveys

A
  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
Q

3 golden survey questions

A
  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
Q

Best time to present survey on the website

A
  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
Q

Likert Scale

A

Strongly disagree
Disagree
Neither agree nor disagree
Agree
Strongly agree

47
Q

Survey advice

A
  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
Q

Depth Interviews are:

A

1-1 conversations with real users / target users

49
Q

Depth interview objectives:

A

1.Understand user goals / problems
2. Understand context of use

50
Q

What not to ask in depth interviews

A
  1. Product / design feedback
  2. Things they might do in the future or hypothetical questions
51
Q

What to ask in depth interviews

A
  1. Ask about their lives and problems
  2. Ask about specific things they did in the past
52
Q

Who you should conduct a stakeholder interview with

A
  1. Anyone with a stake in the project
  2. Anyone feeding requirements
  3. Anybody who provides sign off
53
Q

Purpose of stakeholder interviews

A
  1. Determine what the business problems this product will solve
  2. Determine what business goals this product is expected to help us achieve
54
Q

Objectives of a stakeholder interview

A
  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
Q

Stakeholder brief

A
  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
Q

Card Sorting

A

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
Q

Benefits of card sorting

A
  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
Q

Closed card sort

A

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
Q

A/B Testing

A

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
Q

Multi-variant test

A

When two or more elements are changed

Check which individual elements / combinations produce the greatest results

e.g changing a button, image, CTA

61
Q

Benefits of A/B testing

A
  1. Facilitates improvements, optimisation
  2. Encourages experiments
  3. Validates assumptions (or not)
  4. Data-driven design
62
Q

Competitive Benchmarking

A

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
Q

Categories

A

Before benchmarking decide what categories you want to focus on such as:

Homepage
Search and select
Entering details

(Airline Example)

64
Q

Heuristics

A

Considered as

  • General rules of thumb
  • Characteristics of best practice
  • Criteria to measure against (measure the quality of our product)
65
Q

Heuristics: Software should be polite

A
  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
Q

Heuristics: Usability Heuristics

A
  1. Visibility of system status
  2. Match between system and the real world
  3. Freedom and control
  4. Recognition rather than recall
67
Q

Heuristics: The reservoir of goodwill

A
  1. Don’t force me to do it your way
  2. Save me steps where possible
68
Q

Heurisitc evaluation

A

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
Q

Software should be interested in me

A

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
Q

Software should be forthcoming

A

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
Q

Software should be self-confident

A

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
Q

Software should have common sense

A

E.g Irish Rail website doesn’t assume the user wants to collect their tickets from the station they are departing from

73
Q

Visibility of system status

A

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
Q

Match between system and real world

A
  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
Q

Freedom and Control

A
  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

  1. The software should never lead the user to a dead end - point where they cannot take any further action
76
Q

Recognition rather than recall

A

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

  1. 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
Q

Don’t force me your way

A

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
Q

Don’t waste my time

A

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 (9 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions