How to measure the value of design when it's not a product

Every few years, an executive asks for the ROI of design. The design team scrambles to produce a number, the number is either incredible or unbelievable depending on the audience, and six months later somebody asks again because the answer didn't actually settle anything.

The ROI framing is the wrong one for most design work. Not because design is uniquely unmeasurable, but because the question assumes design produces a thing that can be priced. In most product organizations, design is a function that shapes the product. The product gets priced. Design's contribution to the product is harder to separate out.

What you can measure

There are specific cases where design produces something with a measurable financial outcome. A flow redesign that increased conversion by a measurable amount. A pricing page that performed against a tested variant. An onboarding revision that reduced support load by a quantifiable number of tickets.

These are real. They should be documented. They also tend to be the work that gets cited every time the ROI question comes up, which produces a misleading picture. The cases where design's contribution can be cleanly isolated are the cases that lent themselves to A/B testing. Most design work doesn't fit that frame.

You can also measure proxies. Time-to-market for new features when the design system is in place. Engineering rework rate when designs go through a particular review process. Support volume on areas that received accessibility remediation. These are weaker than direct revenue numbers but they capture work the revenue numbers miss.

What you can't cleanly measure

Most of what design does is more diffuse. A coherent visual system that makes the product feel reliable. Interaction patterns that don't have the failure modes the cheap alternative has. Information architecture that lets a feature land without overwhelming the user.

The contribution of these is real and large. The measurement is hard because the counterfactual isn't accessible. What would have happened without design? You can't run the experiment where you ship the same product without design and compare.

This is the part of the conversation where executives push back and ask for the number anyway. The honest answer is that there isn't one, and the substitute is qualitative judgment from people who can see the difference. That's an unsatisfying answer, and most design leaders give up on it and produce a fake number instead.

The cost-of-not-having-it frame

The frame that works better than ROI is what the organization can't do without functioning design. Not the financial benefit of having it. The failure mode of not having it.

A company without design coherence ships features that look like they came from different products. A company without accessibility practice ships things that get pulled when a customer complains. A company without design system investment slows down on every new feature because every team is rebuilding the same components.

These costs are real, and they're often easier to point at than the upside benefits. The redesign that increased conversion is a single event you can cite. The slow accumulation of design debt that makes every quarter harder is a pattern. Patterns are harder to ROI but easier to recognize.

When the question comes up, redirect: "What would we need to be able to do that we currently can't, and what's the design investment that would unblock it." That's a question with an answer. ROI usually isn't.

What about design systems specifically

Design systems are the one area where the ROI question can be answered with numbers that hold up. Engineering time saved on common patterns. Reduced design time on standard surfaces. Faster onboarding for new engineers and designers.

The numbers tend to be defensible because the comparison is real: there's a before-state where teams built components from scratch, and an after-state where they didn't. The savings can be estimated by looking at how often the components in the system get reused and what the marginal cost would have been to build each instance.

This is one reason design systems get prioritized in cost-conscious environments. They make a case the rest of design work can't easily make. It's also one reason they sometimes get over-prioritized at the expense of the design work that creates the underlying need. A design system is downstream of having something worth systematizing.

The honest conversation

The version of this conversation that works is one most design leaders avoid having. It goes something like: "Most of what design does is going to be visible in qualitative outcomes. Coherence, usability, accessibility, brand strength. Some of it will be visible in metrics, and we'll measure those. We're not going to be able to tell you the ROI of design as a function because the function doesn't have a separable output. We can tell you what we're working on and what we'd need to be able to take on more."

Executives who push back on that are looking for a number they can put in a slide. Executives who accept it understand what design actually is. The conversation tells you which kind you're working for.