According to Nielsen Norman Group's definition, what does 'user experience' encompass?
Choose an answer, then check it.
UX/UI Design · Foundations
Design and the Business of Product Work
On this page 9 sections
In 30 seconds
This lesson is the bridge between design craft and the business side of product work. Everything you have learned so far — user research, personas, wireframes, usability How easily users can accomplish their goals with a product, measured through methods such as usability testing. Full entry → testing — happens inside an organization A group of people who work together toward shared goals and coordinate resources such as money, materials, and skills. Full entry → that pays for the work, schedules it, and expects it to serve its goals. Design happens inside budgets and business decisions. This lesson frames that reality in plain terms; the depth belongs to the Part III subjects that come next: introduction-to-business, accounting, and finance.
Why this matters
Designers who understand only the craft half of product work are caught off guard when budgets, deadlines, and competing priorities enter the room. A wireframe means nothing if the organization cannot afford to build it, and a usability win is hard to defend if nobody can say why it matters to the company. Reading design and business as two halves of the same work changes the conversation: you can argue for good design in the language the organization already uses, and you can see your own work as one activity among many that a product needs. The Part III subjects — introduction-to-business, accounting, and finance — build that second half properly, and this lesson prepares you for them.
The college version
This lesson is a bridge
Everything before this point in the foundations sequence has been the craft half of product work: how to research users, turn findings into personas, sketch wireframes, build prototypes, test usability, and make interfaces clear. This lesson is the bridge from that craft to the business half. It does not teach business or finance; it names the landscape and points to where the depth lives. The subjects that come next in the curriculum — introduction-to-business, accounting, and finance — own that depth. Introduction to business explains how organizations work and what a business is; accounting and finance cover money: how costs are recorded, how budgets are planned, and how spending decisions get made. A bridge carries traffic in both directions: the business subjects will assume you can already think like a designer, and this lesson assumes the business subjects will carry the money questions forward.
Design is a business activity
Products are not built by designers alone; they are built by organizations. An organization coordinates people, money, materials, and information to reach goals, and every product it makes is the result of that coordination. OpenStax's Introduction to Business puts it plainly: production turns inputs — natural resources, raw materials, human resources, and capital — into outputs, which are the products and services customers receive. The textbook's own example is a road bridge: dozens of teams, equipment, and materials arriving on a tight schedule and a specific budget A plan stating how much money an organization can spend on an activity or project, which sets the limits that design work must fit within. Full entry →. Software, apps, and websites are the same kind of work. A design team's research, prototypes, and tests happen inside that schedule and budget, not outside them. Nielsen Norman Group's definition of user experience makes the same point from the other side: UX spans every part of a person's contact with a company and what it offers — the company, not just the screen. High-quality UX, NN/g adds, requires a seamless merging of disciplines including engineering, marketing, graphical and industrial design, and interface design. Design is one discipline among several, inside an organization with goals.
What good design is worth, in plain terms
Good design shows up in product outcomes in general, well-documented ways. The first is adoption The behavior of users choosing to start using a product and continuing to use it over time. Full entry →: people actually start using the product and keep using it. Nielsen Norman Group is blunt on this point — on the web, usability is a necessary condition for survival; if a website is difficult to use, people leave. The second is efficiency In usability, how quickly users can perform tasks once they have learned how the design works. Full entry →: once users have learned a design, how quickly can they perform tasks? NN/g lists efficiency as one of the five quality components of usability, and notes that for internal products, usability is a matter of employee productivity — time lost being confused is time the organization pays for. The third is satisfaction In usability, how pleasant the design is to use, one of the quality components of usability. Full entry →: how pleasant is the design to use, another NN/g quality component. Digital.gov, the U.S. government's design resource, measures usability through usability testing, looking at success rates and customer satisfaction. Notice what this lesson is not doing: it is not computing return on investment, not quoting percentages, and not claiming any specific dollar figure. Quantifying design's value in money terms is real work, and it belongs to the business subjects that come next — this lesson only establishes that the connection exists.
Design work happens inside budgets and decisions
Every design decision is also a business decision, because every design decision costs something and takes time. A simpler form means fewer support calls but two weeks of developer time. A clearer navigation scheme means a calmer flow but a longer testing cycle. An accessibility improvement means a wider audience and a bigger quality-assurance effort. Organizations make these trade-offs constantly, with budgets, timelines, and goals as the frame. Designers do not leave the room when money is discussed; they bring the evidence — what users do, what breaks, what satisfies — and that evidence is what makes the trade-off conversation honest. The mechanics of the money half, how budgets are built, how costs are accounted for, how investments are evaluated, are exactly what the accounting and finance subjects teach. This lesson's job is narrower: to make the frame visible so that the business subjects land on prepared ground.
What comes next, and the honest framing
The curriculum map is short: introduction-to-business, accounting, and finance are the Part III subjects that follow this bridge, and each one takes the business half deeper. Introduction to business starts with the basics — what a business is, how organizations are structured, how they create goods and services. Accounting shows where the numbers come from: how money in and money out is recorded and reported. Finance is about decisions with money: what to spend, what to borrow, what to invest in. None of that replaces design literacy; it completes it. A designer who can run a usability test but cannot read a budget has one half of the job. A manager who can read a budget but cannot watch a user struggle has the other. Design literacy and business literacy are two halves of the same work, and this lesson is the handshake between them.
Eli explains
The same idea, in plain words
Explain it like I’m 10
A product is never just pixels; it is work done by an organization that pays for it, schedules it, and judges it against its goals. Designers bring the craft — knowing what people need and how to make it easy to use. The organization brings the limits: a budget, a deadline, a list of priorities. Good design lives where the two meet: it helps the product reach people, and it earns its place in the plan. This lesson teaches you to see both halves. It does not teach you to build a budget or read a financial statement — introduction-to-business, accounting, and finance come next and go deep. Here, the goal is just to recognize that design decisions are business decisions too, and that the evidence you already collect — what users do, what confuses them, what satisfies them — is exactly the language that connects the two halves.
Picture it like this
Think of a restaurant kitchen. The chef cares about taste, texture, and presentation — the craft. The owner cares about food costs, opening hours, and how many tables turn over in a night — the business. A chef who ignores the owner's numbers may cook wonderful food that slowly bankrupts the restaurant. An owner who ignores the chef sells food nobody wants to eat. The restaurant works only when both halves cooperate: the chef cooks within the budget, and the owner trusts the chef's judgment about what is worth spending on. The designer is the chef, the organization is the owner, and the diners are the users.
Where the picture stops working
The analogy breaks down because a designer is not an employee of one kitchen the way a chef is, and a product is not perishable the way a plate of food is. Design work can be reused, tested, and improved long after it ships, and the owner is usually a team of stakeholders with different goals rather than one person. Still, the core point holds: craft and money have to cooperate, and neither half succeeds alone.
Worked example
Marta works at Nimbus Books, a small online bookstore. Usability tests show that customers abandon the checkout at the address form: it asks for eleven fields, and people make mistakes that produce confusing error messages. Marta redesigns the form with fewer fields, clearer labels, and inline hints. Before anything is built, the team lead asks two questions: how much will it cost, and how long will it take? The developer estimates two weeks; the quarter's budget has room for that, but not for more. To make the case, Marta runs a fresh usability test: six users complete the checkout with fewer errors and finish noticeably faster, and they describe the flow as calmer and clearer. The team approves the two weeks. Notice what happened: Marta's design succeeded because her evidence about efficiency and satisfaction fit the organization's frame of budget and timeline — no return-on-investment formula was needed.
Key takeaway
Design work is business work: products are built by organizations with budgets, timelines, and goals, and design literacy and business literacy are two halves of the same job.
Quick check
3 questions here, of 5 in this lesson’s practice set. Answers stay hidden until you check.
According to this lesson, which three Part III subjects follow the design foundations and own the business and money depth?
Choose an answer, then check it.
A design team proposes a simpler address form for a checkout flow. The product manager asks how the change helps the company. Which answer stays within what this lesson claims about the value of design?
Choose an answer, then check it.
Study tools & related lessonsYou’ll learn to · Common mistakes · Easily confused · Key vocabulary · Related
You’ll learn to
- Explain why design work is a business activity: products are built by organizations with budgets, timelines, and goals.
- Identify the Part III subjects that follow this lesson — introduction-to-business, accounting, and finance — and the depth each one owns.
- Describe the general ways good design affects product outcomes — adoption, efficiency, and satisfaction — without computing return on investment.
- Apply the budget-and-timeline frame to a design scenario, naming where design decisions meet business decisions.
- Analyze why design literacy and business literacy are two halves of the same work for product teams.
- Distinguish what this bridge lesson covers from what the business subjects cover.
Common mistakes
Thinking design ends when the files are handed off.
Design work continues inside the organization's budget and timeline: what ships, what gets cut, and what gets revisited are decisions designers stay part of.
Assuming that 'good design costs more' is the whole story.
The value claims in this lesson are about adoption, efficiency, and satisfaction. Whether a specific change is worth its cost is a question the accounting and finance subjects teach you to answer with evidence.
Treating this bridge lesson as if it already taught the business subjects.
It frames where design meets business; introduction-to-business, accounting, and finance own the depth and come next in the curriculum.
Quoting ROI-style figures without a source.
This lesson deliberately makes no ROI calculations. When a number is needed, the honest move is to learn the measurement methods in the finance subject — or to say the figure is not yet known.
Easily confused
Design craft (the earlier foundations topics) vs. Business literacy (the Part III subjects)
Craft is knowing how to research, design, and test a product well; business literacy is knowing how organizations fund, schedule, and judge that work. This lesson bridges the two.
Adoption vs. Satisfaction
Adoption is whether people start and keep using the product; satisfaction is how pleasant the experience feels. Both are general value claims here, and neither is reduced to a money figure.
This bridge lesson vs. The accounting and finance subjects
The bridge states the frame — design happens inside budgets and decisions — while the subjects that follow teach the mechanics: how costs are recorded, how budgets are planned, how investments are evaluated.
Key vocabulary
- budget
- A plan stating how much money an organization can spend on an activity or project, which sets the limits that design work must fit within.
- timeline
- The planned sequence of dates and milestones for a project's work, such as when research ends and when a release ships.
- organization
- A group of people who work together toward shared goals and coordinate resources such as money, materials, and skills.
- adoption
- The behavior of users choosing to start using a product and continuing to use it over time.
- efficiency
- In usability, how quickly users can perform tasks once they have learned how the design works.
- satisfaction
- In usability, how pleasant the design is to use, one of the quality components of usability.
- usability
- How easily users can accomplish their goals with a product, measured through methods such as usability testing.
- return on investment (ROI)
- A general comparison of money gained against money spent; this lesson mentions the concept but leaves its calculation to the business subjects.
Sources & references
- Usability 101: Introduction to Usability — Nielsen Norman Group
- The Definition of User Experience (UX) — Nielsen Norman Group
- Usability — Digital.gov (U.S. General Services Administration)
- Introduction to Business, Chapter 10 (Achieving World-Class Operations Management) and 12.4 (Supply Chain Management) — OpenStax, Rice University
- Introduction to Business, Section 1.1: The Nature of Business — OpenStax, Rice University
EliExplains lessons are original prose written from the open, credible references above. See Copyright & Licensing.
Researched 2026-08-21
Educational content only. It is not medical, legal or professional advice. Found an error? Tell us.