2026-07-12 · 10 min read · Raw Drafts / UX / Systems
Every Interface Contains a Business Model
How business goals become buttons, defaults, friction, notifications, and everyday user behaviour.
I found the sentence in an otherwise forgettable article about user experience design. The article moved through the standard topics: user research, information architecture, visual design, interaction design, testing, and iteration. It included a few mathematical formulas, some loosely relevant Python examples, and the familiar prediction that artificial intelligence would transform the profession. Then, almost casually, it defined UX as the combination of user needs, technical implementation, and business goals. That sentence was more revealing than anything else in the article.
Designers often speak about users as though they are the centre of the design process. We interview them, observe their behaviour, map their journeys, document their frustrations, and test whether they can successfully complete a task. The language of UX implies that the experience belongs to the user and should therefore be designed in the user's interest. Yet the user is rarely the only party whose goals shape an interface. The company may want more subscriptions, longer sessions, lower support costs, more behavioural data, fewer cancellations, or more frequent purchases. Engineers must work within existing systems, budgets, platform restrictions, and deadlines. UX is the place where all of these pressures are translated into something a person can see, touch, and respond to.
A business goal usually begins as an abstraction. Increase retention. Improve conversion. Reduce churn. Lower customer-service costs. Collect more first-party data. These phrases appear in strategy documents, quarterly presentations, dashboards, and meetings. Eventually, however, they become concrete. “Increase retention” may become a streak, a daily reminder, or a feed with no natural ending. “Improve conversion” may become a larger purchase button, a preselected plan, or an offer presented with artificial urgency. “Reduce churn” may become a cancellation process filled with surveys, warnings, alternative offers, and repeated confirmations. “Lower support costs” may become a chatbot that does everything possible to prevent the customer from reaching a human being. The interface is where the business model touches the user.
The strategy inside the screen
Most people never read a company's annual report, investor presentation, or internal product roadmap. They encounter the organization through smaller decisions. Is the full price immediately visible? Can they use the service without creating an account? Which option is selected by default? Can they reject tracking as easily as they can accept it? How many steps are required to cancel a subscription? Is a human support agent accessible, or hidden behind several layers of automation? These decisions are usually presented as questions of usability, but they are also expressions of commercial strategy.
When a company wants users to spend more time inside an application, designers may introduce autoplay, infinite scrolling, notifications, badges, streaks, and unfinished tasks. When a company wants richer behavioural data, it may ask for consent at moments when the user is impatient, distracted, or eager to continue. When a company wants to reduce operational costs, it may replace direct assistance with documentation, then replace documentation with search, and eventually place a chatbot between the customer and the organization. Each design decision expresses a priority. The designer translates the language of management into sequences of user behaviour. The spreadsheet becomes the screen.
The myth of perfect alignment
UX education often depicts user needs, business viability, and technical feasibility as three overlapping circles. The ideal product is located neatly in the centre. The diagram is comforting because it transforms conflict into geometry. It suggests that the correct answer already exists somewhere in the overlap and that a sufficiently organized workshop will uncover it. Real products are less harmonious. A user may want to complete a task quickly and leave, while the business wants the user to remain active. A user may want to disclose as little personal information as possible, while the company wants a detailed behavioural profile. A user may prefer to purchase something once, while the company wants recurring revenue. A customer may want a clear answer from a human being, while the organization wants to provide support through the cheapest available channel.
Sometimes these interests align. A faster checkout can benefit both the customer and the retailer. Clearer information can reduce user mistakes and customer-support costs. Accessibility improvements can expand a company's market while making the product usable by people who had previously been excluded. A trustworthy service can build long-term customer loyalty without relying on manipulation. The problem is that alignment is often treated as an automatic feature of design rather than an outcome that must be demonstrated.
When user and business goals conflict, the interface becomes the place where that conflict is resolved. Someone decides how much friction the user should face, which information should be emphasized, what should remain hidden, and how much pressure is considered acceptable. These decisions may arrive in the form of wireframes, design-system components, microcopy, or experiment results, but they are still decisions about power. A cancellation button placed deep inside an account menu is not merely a navigation choice. It determines how easily the customer can withdraw from a commercial relationship.
The user is not always the customer
The phrase “user-centred design” also hides an awkward question: who is the product actually designed to serve? On an advertising-supported platform, the user creates content, provides attention, produces behavioural data, and increases the value of the network. The advertiser provides the revenue. The platform must therefore serve several groups whose interests do not always coincide. Users want connection, entertainment, recognition, or information. Advertisers want attention and influence. The platform wants activity, predictable behaviour, and measurable revenue.
The resulting experience reflects all three. The feed is enjoyable, but it has no natural ending. The notification is informative, but it also brings the user back into the system. The recommendation is relevant, but it also determines which products, creators, and ideas become visible. The service is free, but attention, content, and behavioural data are converted into commercial resources. This is why many digital products feel both useful and exhausting. They provide genuine value while continually guiding the user toward actions that benefit the system.
Design as behavioural infrastructure
Interfaces can therefore be understood as a form of behavioural infrastructure. A city influences behaviour through roads, signs, barriers, lighting, public transport, and zoning. Software influences behaviour through defaults, rankings, permissions, friction, rewards, and feedback. A platform decides what is easy, what is difficult, what is prominent, and what remains out of sight. It determines which actions appear normal and which require extra effort.
A default setting can shape millions of decisions without asking anyone to make an active choice. A ranking system can determine which creators, products, or political opinions receive attention. A notification can define what feels urgent. A form can decide which identities and situations the system recognizes. A disabled button can establish what the user is permitted to do. The most powerful design choices often appear mundane because the system does not announce that it is guiding behaviour. It simply creates a path of least resistance and waits for the user to follow it.
This is why the ethical discussion around UX cannot be limited to obvious dark patterns. Deceptive interfaces are only the clearest version of a broader reality: all interfaces influence behaviour. Navigation directs attention. Defaults reduce the likelihood of alternative choices. Friction discourages certain actions. Rewards encourage repetition. The important questions concern the direction of that influence, the interests it serves, and the user's ability to recognize or resist it.
The designer as an intermediary
Designers often describe themselves as advocates for the user within an organization. That role can be real and valuable. Research can reveal harms that executives and engineers have overlooked. Usability testing can expose failures that internal teams have normalized. Accessibility work can make products usable by people who would otherwise be excluded. Designers can challenge assumptions and demonstrate that a decision which looks efficient internally creates confusion, anxiety, or unnecessary work for the customer.
At the same time, designers are employees, contractors, and consultants. Their work is funded by organizations with goals of their own. This places the designer in an uncomfortable position. They may understand the user's frustration while being asked to optimize the system producing it. They may be asked to make an unpopular policy feel friendlier, smoother, or easier to accept. They may improve the experience of a process whose underlying purpose remains questionable.
A well-designed surveillance system is still a surveillance system. Friendly language does not make a cancellation obstruction less obstructive. A conversational chatbot may still function as a wall between the customer and the help they need. Good craft can make a system easier to use, but craft alone does not determine whether the system deserves to exist in its present form. Designers need to examine the intention and structure of the system they are improving, not only the quality of their execution.
Business goals are not the problem
The existence of business goals is not itself a scandal. Products need resources. Employees need salaries. Infrastructure, support, maintenance, and development all cost money. A product without a sustainable economic model may disappear, leaving its users with nothing. The problem begins when business goals are treated as neutral, inevitable, or naturally compatible with the interests of the user.
Words such as engagement, personalization, conversion, and retention illustrate the ambiguity. Engagement may describe meaningful participation, but it can also mean compulsive use. Personalization may make a service more relevant, but it may also require extensive surveillance. Conversion may help a person make a useful purchase, or it may pressure them into accepting something they do not need. Retention may indicate lasting value, or it may result from making the exit unnecessarily difficult. A metric describes the outcome an organization wants, but it does not explain whether the method used to reach it respects the user.
A responsible design process should therefore make conflicts visible rather than hiding them inside the language of optimization. It should ask who benefits from a particular decision and who carries the cost. It should identify the behaviour the interface is trying to produce and consider whether the user can reasonably refuse. It should distinguish friction that protects users, such as a confirmation before deleting important data, from friction that protects the company from the user's freely made decision. It should ask what the interaction would look like if the user fully understood the commercial objective behind it.
These questions belong inside UX work. They are as important as typography, task completion, accessibility, conversion rates, and design-system consistency. They also require designers to understand more than interfaces. Designers need to understand organizational incentives, revenue models, labour, regulation, data collection, and the consequences of the systems they help construct.
The business model is already there
Every interface contains a theory of how an organization creates value. Sometimes the theory is obvious. A retailer wants to sell products. A bank wants deposits and loans. A streaming service wants subscribers. Sometimes it is concealed beneath the language of convenience, community, personalization, or innovation. In either case, the business model appears in the details. It appears in what the product asks from the user: money, time, attention, data, content, labour, or dependence. It appears in what the system makes easy and what it makes difficult. It appears in what the interface remembers, rewards, hides, interrupts, and refuses.
An interface is never only a surface. It is also a contract, a policy, a sales strategy, and a behavioural environment compressed into something that looks like a screen. The next time an application asks you to enable notifications, create an account, continue scrolling, accept all cookies, or reconsider cancelling, the interaction may appear insignificant. Behind it sits an organization with a goal. Someone translated that goal into a design, and now the design is asking you to act.
AI authorship note
This essay began with Kris Haamer's reaction to a generic UX article that openly listed business goals alongside user needs and technical implementation. AI supported synthesis, drafting, editing, and implementation. Kris is responsible for the editorial direction, the argument about interfaces as expressions of organizational incentives, and the decision to publish it.