【한글자막】 사용자 경험 (UX) : 사용성 및 UX 를 위한 최고의 가이드

If we asked 50 people this question: “What is a browser?”, how many people do you think would give us a correct answer? Does this video challenge your views of how "ordinary" people think about technology?

Copyright belongs to Ji Lee who uploaded it to YouTube. The original file is here: https://www.youtube.com/watch?v=o4MwTvtyrUQ

There are many ways of getting an understanding of your users' context. Here we cover one of the more useful techniques: contextual inquiry. This technique lets you penetrate deep into the world of your users and discover what it is that they actually want to do with your system.

Great field researchers demonstrate 5 key behaviours. Let's review each of those behaviours in turn.

Further reading

• The 5 habits of highly effective field researchers by David Travis
• Site visit interviews: from good to great by Gret Higgins
• The Anatomy of an Experience Map by Chris Risdon
• A collection of experience maps on Pinterest by Remko Vermeulen
• 17 types of interviewing questions by Steve Portigal

The user journey map is just one way you can present your results. Let’s quickly look at some other methods.

There are some situations where contextual inquiry might be problematic, so here I talk about some other methods. These aren’t replacements for contextual inquiry, but if you can’t do anything, you can at least do these.

Three myths about this kind of user research that you might hear.

Does your web site suffer from 'elastic user' syndrome, where you give equal value to every possible user doing every possible task? In this lecture, I explain why “Something for Everybody” means “Everything for Nobody”.

Let's review how we might analyse the data from this field visit.

There are four main benefits of personas:

1. Personas make assumptions about users explicit.
2. Personas place the emphasis on specific users rather than “everyone”.
3. In limiting our choices, personas help us make better design decisions.
4. Personas help the design and development team gain a shared understanding of users.

Let's look at some ways that I’ve seen personas publicised within organisations, so that you can decide which approach would work well for you and your organisation.

Here’s a checklist you can use to decide whether or not your persona cuts the mustard. I’ve used the acronym PERSONA to remind you about the things that you should look out for.

Gift Giver, a gift recommendation system based on an extremely accurate product recommendation technology.

Speak with a minimum of 5 users to find out:

• Is there a need for this system?
• If not, how can you change it so that it meets a need?
• Who are are the main user groups?
• What day-to-day activities do they engage in that’s related to the product?
• What is the workflow (the sequence of activities)?

Make sure you actually observe people, don’t just interview them.

Don’t overthink this activity. Just get out and speak to some users!

To do this activity, you'll need a sheet of flip chart paper, some Sharpies and a pack of sticky notes. You will create a persona for ONE of your user groups that will include:

• A sketch: Show the persona’s context, with a quotation stating the main user need.
• Facts: Descriptive demographic information about your persona.
• Behaviours: How is the persona solving their problem now?
• Needs and goals: What does your persona want to accomplish?

Compare your work with what other students have done on these same projects.

A common design mistake is to assume the design should always be made as flexible as possible. Flexibility has costs in terms of decreased efficiency, added complexity, increased time, and money for development. A focus on users tasks can help us enormously.

So how do you go about identifying red routes? One approach is to identify the frequent and critical tasks.

In 5 minutes, brainstorm 5 red routes for ONE of the following:

• An application that lets you back up your computer over the Internet
• A presentation app (like PowerPoint) that runs on a mobile phone
• An application to help you calculate your taxes
• An application that lets you read online magazines on a tablet device, like an iPad

How do you test a user story to see if it’s any good? Here are four questions you can ask of your user story.

How does your company measure the success of its products and services? Are product teams judged on how easy their products are to use or on how fast the products are completed? You might not think that user experience can be measured, but it can. Here's how.

I want to distinguish between two kinds of hypothesis. The first is the “problem hypothesis”. It’s our assumption about the user need. We need to check this.

The second is the “solution hypothesis”. This is our design that we think meets the user need. We need to check this too. Let’s begin with the problem hypothesis.

Usability: The extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use.

The ISO definition of usability gives us three measures that we can use to assess the usability of our web site. In this lecture we show how to unpack the definition of usability and apply it to usability measurement.

Our second component of usability is efficiency. Let’s look at how we can measure efficiency.

The hardest kind of information to organise is category information as you don’t know the categories that people use. In this case, card sorting is the technique to use. In this lecture, we describe how to run a card sort.

This lecture shows a screencast of an online card sort in progress, so you can see how it works. You can take part in the study via this link: https://demo.optimalworkshop.com/optimalsort/webusability

How do you analyse the data from a card sort?

You analyse card sort data with agglomerative monothetic clustering. It sounds complicated, but conceptually it's quite straightforward. In this lecture, we describe this analysis method. You can play with the analysis tool here: https://demo.optimalworkshop.com/optimalsort/shared-results/webusability

You’d know a spreadsheet anywhere — formula bar at the top, grid below — no matter what company made it. Or an e-mail program, a word processor or a Web browser. I’m going to call these things “idioms” or if you prefer “design patterns”.

Progressive disclosure is a fundamental principle of interaction design that allows you to simplify your user interface. It exploits a basic law of psychology known as Hick’s Law, but I like to think of it as a reverse strip tease. Here's why.

Basic user interface controls like radio buttons, checkboxes, scrollbars etc — are the building blocks of a design's "language". Here's how to use these controls correctly.

One of the problems with small controls is that they fall foul of Fitts’ Law. According to Fitts’ law (named after the psychologist Paul M Fitts), the time required to rapidly move to a target is a function of the distance to and the size of the target.

Why is Afghanistan always top in a country drop down menu?

People have certain expectations about where objects will be in an interface. Let's look at web pages as an example.

Visual design is often dismissed as eye candy. In fact, we can use four key principles of visual design to create more usable interfaces. These principles are Contrast, Repetition, Alignment and Proximity.

Form labels: should they be left aligned, right aligned or top aligned?

Paper prototyping is one of the best methods we have of rapidly mocking up and testing our design idea with users. In this lecture, I explain what paper prototyping is (and what it isn't).

Watch this example of a paper prototype being used to test out an early design concept.

Copyright belongs to channy who uploaded this file to YouTube. You can view the original file here: https://www.youtube.com/watch?v=GrV2SZuRPv0

Once you get past the paper phase, there are dozens of electronic tools you can use for prototyping.

Develop a paper interface for your application based on one of your user stories and your primary persona. Your design should comprise a sequence of 4-6 screens (one screen per step).

There are a few flavours of usability testing, but there are two main ones that I want to tease out. These are “formative tests” and “summative tests”.

Before reviewing how to moderate a usability test, I wanted to mention the different ways that people tend to carry out formative usability tests.

One of the first steps in running a usability test is to explain to the participant about thinking aloud. You want participants to keep up a narrative that explains what they are looking for, where they are confused and any decisions they are making.

Sometimes it's hard being a usability test moderator. You need to make sure you keep a poker face.

This video makes the point in a humorous way.

Copyright belongs to Guy Collins Animation who uploaded the file to YouTube. You can view the original file here: https://www.youtube.com/watch?v=fa9DLxDtPtc

Testing a paper prototype is different to testing a live web site. This lecture explains the different roles.

A good observation is something you see or hear. It’s not your guess at what’s behind the problem, no matter how sure you are.

You can use affinity sorting or a flowchart to prioritise usability problems.

This video shows an example of a student running a usability test of her 'Find My Pet' prototype.

In collaboration with Rolf Molich, Jakob Nielsen created 10 principles or "heuristics" you can use to evaluate your interface.

Do design elements such as objects and actions have the same meaning or effect in different situations?

Is appropriate help information supplied and is the information easy to search and focused on the user’s task?

You shouldn't just do a heuristic evaluation on your own — you need to have multiple evaluators. Here's why.

How do I get started with users? I know this can be a difficult prospect for people who work in an organisation that hasn’t done much user research in the past. So here are 5 tips for getting your users involved.

I want to remind you to build your career. So here are some tips to help you build your career inside your company.

Here's an example of how one student (Aaron Christopher) presented the results of his design activity as a portfolio entry.

See how another student approached the Gift Giver project on this course and presented it as a portfolio entry. 

Are your curious what a UX portfolio looks like? Do you want to know what makes a good portfolio? In this video, I review 6 different UX portfolios that people submitted to me through the course Facebook group. This is a long lecture (almost an hour) and pretty much a course in itself, so you only need to view this lecture if you are specifically interested in creating a UX portfolio.

Here's a summary of the key points from the portfolio review. Use this as a checklist to evaluate your own portfolio.

I hope you'll leave a review of the course in the Udemy interface but please also complete this short survey which provides more detailed feedback for me on what you liked and what can be improved.