Skip to content
BENIBIX Learn

User Experience

Design how it works, not just how it looks · 83 terms

Sort
Compare

UX Basics

14

What UX means, how easy a product is to use, and how its content and steps are laid out.

How it feels to use a product, from start to end. UX design shapes it.

How well people can use something to get a task done.

How fast a new user learns to do the main tasks in a product.

How the pages of a site are sorted and named. It helps people find things.

How easy it is to find things on a site or in an app.

The clues a link or label gives about what sits behind it.

A drawing of all the pages on a site, and how they link up.

A diagram of the steps a person takes to finish one task.

The way through a task when each step works and nothing goes wrong.

A rare case a design must still deal with. No signal and an empty list are two.

What a person believes about how something works. They act on it.

Planning a whole service. That means the screens people see and the work done behind them.

A map of a service in rows. It runs from what customers see to the work behind.

How a person feels about a whole company. It runs from the first ad to the last call.

UX Research

33

Ways to learn what users need: asking, watching, sorting and mapping.

Learning about the people who will use a product. What do they need?

Research Methods

21

The ways to study users: watching them work, testing a design, or asking them to keep notes.

A talk with one user. You learn what they need and what goes wrong.

Watching real people try real tasks. You see where they get stuck.

In a test, people say out loud what they think as they use the product.

A test people do on their own. A tool records it, and no host is there.

A test led live by a host, who watches and asks why.

A quick test with strangers in a cafe or a hallway. It takes minutes.

Users sort topics on cards into groups. It shows how they expect things to be organized.

A few experts check a design. They use a short list of rules.

You watch people work in their own place. You ask questions as they go.

People write notes on how they use a product. They do it for days or weeks.

A test of a site's menu words. People use a plain text menu with no design.

A test of where people click first when they try to do a task.

A test that shows a screen for five seconds. Then it asks what people remember.

Recording where people look on a screen, and for how long.

A replay of a real visit to a site. It shows each click and scroll.

A picture of one page. The colours show where people clicked or scrolled.

A talk with the team that owns a project. It asks about goals and limits.

Breaking a user's job into small steps. It shows where people may get stuck.

A team steps through a task as a new user would. They ask four questions at each step.

A full check of a live product for problems. It ends in a ranked list of fixes.

People see two or more designs and pick the one they like. Then they say why.

Research Synthesis

7

Turning what you learned from users into groups, people and a clear problem to solve.

A made-up person who stands for a group of real users. Research shapes them.

A picture of each step a person takes with a firm. It shows how each step feels.

A four-box chart of what a user says, thinks, does and feels.

You sort research notes into groups that go together. Then the big themes show.

A short line. It says who has a problem, what it is and why it counts.

Notes from many talks, sorted into a few clear lessons. The team acts on them.

One person, one product and one goal, told as a short story.

UX Metrics

4

Numbers that show how well people use a product: done or not, how fast, and how it felt.

A survey of 10 lines. It gives a product one ease score from 0 to 100.

The share of test users who finish a task, like 8 out of 10.

One question asked after each task: how easy was that? People answer from 1 to 7.

How long a person takes to finish one task in a test.

Wireframes and Prototypes

5

Plans and models of a screen, from rough boxes to something you can click.

A plain plan of a screen. It shows where things go, with no colors or pictures.

A still picture of a screen that shows how it will really look. Nothing clicks.

A model of an app that people can click. You test an idea before you build it.

Screens drawn on paper that people test by tapping. Someone swaps the pages.

How close a design is to the finished product. Rough is low, polished is high.

Interaction Patterns

14

How a product shows what can be done and answers each tap, for good or for ill.

How an app answers when you tap, type or swipe. Each act gets a reply.

What an object lets you do, like a handle you can pull.

A clue that shows what you can do, like a push sign on a door.

How a product shows what just happened after you act.

A tiny moment built round one task. The heart that pops when you like a post is one.

Show the basics first. Keep the rest one tap away.

A trick in a design. It pushes you to do a thing you did not mean to do.

Making mistakes hard to make, so there is less to fix later.

It takes back the last thing you did. A slip is never final.

How a product helps new users get started and reach their first win.

Designing for how a product makes people feel. How it works counts too.

Adding points, badges and streaks to tasks that are not games, to make them feel more fun.

An interface you use by chatting, by text or by voice.

An interface you use by speaking. It answers you out loud.

UX Writing

3

The words on screens, like buttons, hints and errors, and how to plan them.

Writing the words in an app or a site. Think of buttons, hints and error notes.

The tiny bits of text in an app, like button words and hints.

Working out what facts people need, and the best way to show them.

UX Laws

14

Findings from psychology that predict how people choose, aim and remember on a screen.

Speed and Effort

8

Findings about how long people take to choose, aim and wait, and how much they can hold.

Big, close targets are faster to hit than small, far ones.

The more choices there are, the longer it takes to pick one.

How much thinking a task takes. Too much and people give up.

People can only hold a few things in mind at once. Group them into chunks.

Too many choices make people stop. Some pick nothing at all.

A fast reply keeps people going. Under a second, they get much more done.

Every task has some hard part. Either the product or the user must carry it.

People speed up as they get closer to a goal they can see.

Perception and Memory

6

Findings about what people notice, what they expect, and what they remember later.

People spend most of their time on other sites. They expect yours to work the same way.

People think a nice-looking app is easy to use. Even when it is not.

The one thing that looks odd is the one people see and recall.

People remember the first and last things in a list best.

People judge a visit by its best part and by its end.

Tasks left undone stick in the mind more than tasks that are done.