The Value of Design
Design is often justified by aesthetics or user happiness metrics. But its real value runs deeper — and understanding that changes how you argue for it in any room.
Every designer I know has been in this meeting: the one where someone asks, politely or not so politely, what design is actually worth. The question usually comes dressed in the language of ROI or headcount justification, but underneath it is something more uncomfortable — a genuine uncertainty about what design does that could not be done cheaper, faster, or simply by asking a developer to “make it look nice.”
It is a fair question. We should have better answers for it.
What Design Is Not
Design is not decoration. I say this not to be dismissive of decoration — there is real value in things being beautiful — but because conflating the two makes it very easy to cut design when times are tight. If design is lipstick, it is the first thing that goes. If design is structure, cutting it makes the building fall down.
Design is not a single stage in a process. The common misunderstanding is that design happens after the requirements are set and before engineering begins — a layer of paint applied to a pre-existing shape. In reality, the most valuable design work happens before requirements are written, when there is still room to ask whether the problem being solved is the right problem.
Where the Value Actually Lives
The value of design concentrates in a few specific places.
Reduced rework. A decision made with design input at the beginning of a project costs almost nothing to change. The same decision made at the point of implementation costs a week. The same decision made post-launch costs a month and introduces technical debt. The cost of not designing early is enormous, but it is distributed across time and across teams, so it rarely appears on any single budget line.
Increased adoption. Products that are hard to use get abandoned. This is obviously true of consumer software but it is equally true of internal tools, enterprise platforms, and public services. The NHS estimates that confusing prescription labels contribute to thousands of medication errors annually. The cost of those errors vastly exceeds the cost of a designer spending a week on typography and hierarchy.
Trust and retention. Design communicates competence. A platform that looks considered signals that the people behind it are also considered. This is not a purely aesthetic effect — it shapes whether users trust that their data is handled carefully, whether they complete forms, whether they return.
Making the Argument
The challenge is that most of these effects are downstream and distributed. Design prevents problems more often than it solves them, and prevention is notoriously hard to put in a slide deck.
The best approach I have found is to work backwards from cost. Take a single usability problem — a checkout flow with a 40% drop-off, a support queue where 30% of tickets ask the same question — and calculate what fixing it is worth. Then show that the fix is a design fix. Then show what it cost in designer time.
That is not the whole picture of design’s value. But it is a picture the right people can read. And sometimes, getting into the room is the first design problem you have to solve.