By the end of this lesson you can
- Explain why a product has to serve both its users and the business that pays for it.
- Separate user needs from business goals and write each down clearly.
- Find the overlap where a design decision helps both, and spot where they conflict.
The idea
Every product exists for two reasons at once. People use it because it helps them do something they care about. A business builds it because it hopes to earn money, save money, or meet a mission. Good design lives where those two reasons overlap.
User needs
A user need describes what a person is trying to achieve and what gets in their way. It is written from the person's point of view and does not mention your product: "I need to know my parcel will arrive before I leave for work" rather than "I need a tracking page".
Business goals
A business goal describes what the organisation wants: more subscribers, fewer support calls, higher order value, more people completing an application on time. Good business goals are measurable and come with a reason ("reduce support calls about delivery by 20% because each call costs £4").
The overlap
The strongest design decisions serve both. Clear delivery tracking helps the customer plan their day and reduces support calls. When a goal only serves the business (hiding the cancel button) it usually costs trust later. When a decision only serves users and ignores the business, it rarely gets built or survives.
Designers are often the people in the room who keep the user's side visible. That does not mean opposing the business; it means showing how meeting user needs is usually the most reliable route to the business goal.
Why it matters in real projects
Designers who only talk about users struggle to get their ideas funded. Designers who only talk about business metrics drift into manipulative patterns. Being able to state both, and to show the overlap, is what lets you argue for good design in terms everyone in the team cares about. It also gives you a way to judge your own ideas: if a design helps neither side, cut it.
A realistic example
A gym chain wants to grow online class bookings. The business goal is clear: increase the share of classes booked through the app from 40% to 60%, because phone bookings tie up front-desk staff.
Interviews with members show a user need the team had not considered: "I want to know if a class is worth going to before I commit an evening to it." Members phoned the desk mainly to ask how busy a class was and whether it suited beginners.
The team adds a short description, a difficulty level and a live "spaces left" count to each class. Members can now decide without calling. Online bookings rise and front-desk calls fall. One change served both needs because the team understood why people phoned in the first place.
Step by step
Collect the business goal
Ask the product owner what success looks like, how it will be measured, and why it matters now.
Collect user needs
Review existing research, support tickets and reviews. Write needs as "I need to... so that..." statements without mentioning the product.
Place them side by side
Make two columns. Draw lines between needs and goals that support each other.
Mark the conflicts
Highlight goals that would work against a user need, such as adding friction to cancelling.
Choose the focus
Pick one or two overlaps to design for first, and write a sentence explaining how each serves both sides.
Common mistakes
Mistake Writing user needs as features ("users need a filter").
Instead Describe the outcome the person wants. The filter is one possible solution.
Mistake Treating business goals as the enemy.
Instead Learn the reason behind each goal. Most can be met by serving users well.
Mistake Accepting vague goals such as "improve engagement".
Instead Ask what behaviour should change, by how much, and how it will be measured.
Check your understanding
Choose an answer, then check it. There is an explanation either way.
Practice exercise
Exercise · about 40 min
Map needs to goals
Choose a product you use weekly, such as a food delivery or banking app, and map its likely user needs against its likely business goals.
Steps
- Write five user needs in "I need to... so that..." form.
- Write three business goals with a measure and a reason.
- Connect needs and goals that support each other.
- Mark one conflict and propose a design that respects the user need.
Deliverable
A one-page map with needs, goals, connections and one proposed design change.
Self-assessment
Tick each item when it is true of your exercise. Be honest; this is for you.
4 items
Summary
- Products have to serve the people who use them and the organisation that builds them.
- User needs describe outcomes from the person's point of view; business goals describe measurable organisational outcomes.
- The best design decisions sit in the overlap.
- Goals that only serve the business tend to cost trust over time.
Further reading
Third-party sources, chosen for reliability. They open in a new tab.
- Learning about users and their needs (opens in a new tab)GOV.UK Service Manual
- UX research cheat sheet (opens in a new tab)Nielsen Norman Group
Your notes
Marking complete updates your course and roadmap progress.