Definition
Design and business describes the relationship between what a product does for the people using it and what it must do to keep existing. That relationship is not automatically hostile and not automatically harmonious. A revenue model is a set of standing incentives, and those incentives act on design decisions continuously, usually through metrics rather than through instruction. Nobody typically asks a designer to make cancellation harder. A target is set, the flow with the fewest exits performs best against it, and the harder flow ships. Understanding the mechanism is what allows a designer to intervene at the point where it operates — the framing of the goal and the choice of measure — rather than objecting at the end, when the objection reads as taste.
Why It Exists
The subject exists because designers work inside commercial organizations and are paid from revenue their work influences. Pretending otherwise produces two recognizable failures. The first is the order-taker, who treats business goals as given and optimizes whatever is put in front of them, and who is therefore the most efficient possible route to a manipulative product. The second is the moralizer, who objects on principle without evidence or alternatives, is gradually excluded from the decisions that matter, and then attributes the resulting product to everyone else. The discipline exists to make a third posture available: engaging with the commercial logic seriously enough to argue inside it, with data, alternatives, and an account of long-term cost that a person with a revenue target can actually use.
Examples
- →Subscription products are rewarded for retention, which aligns with real usefulness over months but also rewards obstructed cancellation and auto-renewal that is easy to forget.
- →Advertising-funded products are rewarded for attention, which aligns with genuinely engaging content and also with infinite scroll, autoplay, and notifications timed to interrupt.
- →Transaction products take a share of each exchange, which aligns with trust and completion but rewards fees disclosed late in a checkout rather than in the first price shown.
- →Enterprise licensing is bought by an administrator rather than a daily user, which rewards configurability and reporting for buyers while the people who use the product all day have no purchasing power.
History
Design's commercial role has always been double-edged. Industrial design in the twentieth century was employed both to make manufactured goods genuinely better and to accelerate replacement through styling cycles, a tension that critics of the period named directly. In software, the rise of free consumer services funded by advertising shifted the customer relationship: the person using the product was no longer the one paying for it. As instrumentation and experimentation matured, design decisions became testable against revenue in short cycles, which strengthened whatever the chosen metric happened to reward. In 2010 Harry Brignull coined the term dark patterns for interfaces deliberately designed to trick people into choices they did not intend; he later favored the term deceptive design. In the years since, regulators in several jurisdictions have taken active interest in deceptive design, particularly around consent, subscription cancellation, and pricing disclosure.
In Modern Design
Contemporary practice treats the business model as something to be designed with rather than around. Designers are expected to know how their product earns, which metric their team is held to, and what that metric quietly rewards. Much of the useful work happens in metric selection: a team measured on time in app will build differently from one measured on tasks completed, and both numbers are equally easy to collect. Experimentation makes any short-term lift visible while long-term erosion of trust remains invisible, so the honest practitioner argues for counter-metrics, longer measurement windows, and qualitative evidence alongside tests. Deceptive design is now also a legal and reputational risk, not only an ethical one, which gives a designer a second, more portable argument when the first one is not persuasive in the room.
Real-World Example
Consider a team asked to reduce cancellations in a consumer subscription. The available levers are well known: bury the cancel link, add confirmation steps, present a discount, require contacting support. Each reliably reduces cancellations in the next quarter, and any of them will win a test. A designer arguing only that this feels wrong will lose to a number. A designer who instead examines who cancels finds, in many products of this kind, two distinct groups: people whose circumstances changed and who will not return regardless, and people who stopped receiving value in a specific, identifiable week. Obstruction taxes the first group and postpones the second. Proposing work on the second week — the point where value collapsed — reframes the target from retention-by-friction to retention-by-worth, and it is an argument stated in the language the business already uses.
Key Principles
- →Know precisely how your product earns money, because that model is acting on your design decisions whether or not you acknowledge it.
- →Argue at the level of the goal and the metric, not at the level of the final screen, because that is where the outcome is actually set.
- →Name the places where user benefit and business benefit genuinely align, and defend them as strongly as you resist the places they diverge.
- →Recognize deceptive design by its mechanism: an interface arranged so the choice a person would make on reflection is harder than the one the company prefers.
- →Bring evidence, alternatives and an account of long-term cost, since a position without an alternative is rarely treated as a position.
- →Remember that short experiments measure short effects; erosion of trust appears on a timescale most test windows cannot see.
Why it matters
Most of what people find degrading about modern software was designed deliberately by competent practitioners under commercial pressure, not produced by incompetence. That fact is uncomfortable and also encouraging, because it means the decisions are reversible by the same kind of people. A designer who understands the commercial machinery can find the arguments that actually move it: that obstructed cancellation generates chargebacks and regulatory exposure, that consent harvested by confusing defaults is fragile when scrutinized, that a product people recommend costs less to grow than one people are retained into. None of this makes the tension disappear. There are real cases where the user's interest and the company's interest do not reconcile, and the honest description of the job includes deciding, sometimes, how much of that you are willing to build.
Then vs Now
Then
Commercial pressure reached design slowly, through sales figures and styling cycles. A manufacturer could shorten a product's useful life through fashion, but the feedback loop took seasons and the mechanism was visible to anyone who looked at a showroom.
Now
Pressure arrives weekly through metrics and experiments. Any change that lifts a chosen number can be validated in days, while the costs it imposes on trust, attention or consent accumulate over years and appear in no dashboard the team owns.
Try it yourself
Pick a subscription you currently pay for and attempt to cancel it, documenting every screen until you either finish or decide to stop. Count the steps, note each attempt to redirect you, and record how the options were worded and which was made visually easiest. Then find where you originally agreed to the renewal terms and how that was presented. Write a short account of what a person in a hurry would most likely do at each step and what the company gains from that behavior. Finally, write the single change that would most improve the flow for users, and estimate honestly what it would cost the business in the next quarter and what it might return over two years. That last estimate is the argument you would actually have to make at work.