Understanding the Product: What It Does and Who It Helps
Before you design a screen, learn what the product is, who uses it, and which job it helps them finish.
In short
Before designing a screen, learn what the product is, who uses it and which job it helps them finish.
4 min readFree
What you will learn
Good design starts with a clear picture of the product. In this lesson you will learn how to describe a product in plain words, find the job it does for people, and write down the problem it solves. You do not need a research degree for this. You need curiosity and a few good questions.
The key words below appear again and again in UX work. Read them first.
Key words
- Product
- Anything a company makes to help people, such as an app, a website, or a service.
- User
- Any person who uses the product.
- End user
- The specific group of people a designer builds the product for.
- User experience (UX)
- The whole result and feeling a person has when dealing with a product, from first hearing about it to getting help later.
- User interface (UI)
- The buttons, links, menus, and other parts of a screen that a person sees and uses.
- Job to be done
- The task or outcome a person wants to reach when they use a product.
- Problem statement
- A short written statement that keeps a team focused on one user need.
What is a product for?
A product is more than its screens. The Nielsen Norman Group describes UX as the whole relationship between a person and a product. That relationship includes what the person notices, how they feel, and what they do. UI is only one part of it. A nice-looking button does not help if the person cannot find what they came for.
When you meet a new product, ask three simple questions. What does it do? Who uses it? Why would someone pick it instead of another option?
How do you find the job people hire the product to do?
The jobs-to-be-done idea says people 'hire' a product to do a job for them. Coursera defines a job as the specific task or outcome a customer expects to get done with a product. The job is often practical, but it can also carry feelings and social meaning.
Nielsen Norman Group compares two ways of looking at a task. A task study might show that delivery drivers print directions for every stop. The job behind that habit is getting guidance while driving. Looking at the job can lead to a better answer, such as voice directions, instead of a faster printer.
What are the three kinds of need?
Functional need
Does the product get the job done? This is the practical part, such as saving time or sending money.
Social need
How does using the product affect the way other people see this person?
Emotional need
How does the product make the person feel while they do the job, or after it is done?
How do you write a problem statement?
A problem statement keeps a team focused on one user need.
- 1
Name the user
Pick a real kind of person, such as a busy parent who shops after work.
- 2
Describe them
Add a few facts about their life that matter to the product.
- 3
State the need
Say what they are trying to do and why it matters to them.
- 4
Add the insight
Explain why they have this need, based on what you learned from real people.
Example: A busy parent who shops after work needs a quick way to reorder household staples, because forgotten items cause extra trips to the store.
Why is the product worth using?
A value proposition is a short statement that tells a user why they should use a product or service. To write one, answer two questions. What does the product do? Why should the user care?
Tip
Write the value statement in plain words. If a friend who does not work in tech cannot repeat it back to you, rewrite it.
Check your understanding
Quick check
A person buys a drill mainly to make a hole in a wall. What is the job to be done?
Key takeaways
A product is a tool for a job, used by a real person with practical, social, and emotional needs. Before you design anything, describe the product in plain words, name the job it helps with, and write a short problem statement. These steps give your later design choices a clear reason to exist.
Sources
- Nielsen Norman Group: What Is User Experience (and What Is It Not)?
- Nielsen Norman Group: Personas vs. Jobs-to-Be-Done
- Coursera: Jobs to Be Done: Definition, Examples, and Framework
- Strategyn: Understanding Customer Needs - The First Step in Innovation
- Medium: Annotations on the Google UX Design Professional Certificate course (1/7)
- Medium: Google UX Design Course. Problem Statement, Hypothesis Statements and Value Proposition
Last updated on 17 November 2026
Related lessons
Learn with me
Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.