The ROI of design: what the evidence shows and how to measure it

Last updated: July 2026

The ROI of design is the measurable business value that design decisions produce: revenue growth, retention, conversion, and lower cost to operate. The evidence is unusually strong. McKinsey tracked 300 companies over five years and found that top-quartile design performers grew revenue 32 percentage points faster than their industry peers (The Business Value of Design, 2018). This post covers what design ROI means, the research behind it, and how to measure it in a shipping product.

Key takeaways

• Top-quartile companies in the McKinsey Design Index grew revenue 32 percentage points faster and total shareholder returns 56 points faster than industry peers over five years.
• The DMI Design Value Index found that design-led companies outperformed the S&P 500 by 211% over ten years.
• Forrester measured a 301% ROI on IBM's design thinking practice, with design and alignment time cut by 75% and design defects halved.
• Four metrics carry most design measurement: conversion rate, retention, task completion time, and engagement.
• Returns concentrate at the top: McKinsey found the market barely distinguishes average design from below-average, but pays the top quartile disproportionately.

What is the ROI of design?

The return on investment of design is the measurable value that design contributes to a business. Every design decision, from a reworked onboarding flow to a simplified data table, either moves a business number (conversion, retention, operating cost, revenue per user) or it does not. Design ROI is the discipline of knowing which, before and after the work ships.

In practice, design ROI lives at the intersection of two forces that often pull apart. Users ask for one thing; the business is focused on growth or cost-efficiency. Good design finds the point where both are served, and the returns show up as lower churn, higher conversion, and loyalty that compounds. Design that serves only one side of that equation, however polished, does not produce a return.

The definition matters because design is still widely bought on taste. In McKinsey's research, more than 40 percent of companies said they do not talk to their end users during development, and over half admitted they have no objective way to assess what their design teams produce. A function that is not measured gets funded last and cut first. The research below is the case for measuring it.

How strong is the evidence for design ROI?

Three independent research programmes reach the same conclusion from different angles: companies that treat design as a measured business function outperform companies that treat it as a styling pass.

Study	Finding	Scope
McKinsey, The Business Value of Design (2018)	Top-quartile design performers grew revenue 32 percentage points faster and shareholder returns 56 points faster than industry peers over five years	300 listed companies, two million+ financial data points, three industries
DMI Design Value Index (2015)	Design-led companies outperformed the S&P 500 by 211% over ten years	16 US public companies meeting six design-management criteria
Forrester, Total Economic Impact of IBM's design thinking practice (2018)	301% ROI over three years; design and alignment time cut by 75%	Four enterprise clients interviewed plus 60 executive survey responses

What the numbers actually say

The McKinsey result carries the most weight because of its method: two million pieces of financial data and more than 100,000 recorded design actions across medical technology, consumer goods, and retail banking. The correlation held in all three industries, which suggests the effect is not a software-sector artefact. It applies whether the product is a device, a service, or an app.

The sharpest detail hides in the quartiles. Revenue and shareholder-return differences between the fourth, third, and second quartiles were marginal. The market pays for design excellence, not design adequacy. Being slightly better than average returns almost nothing; reaching the top quartile returns the full 32 points.

What the numbers do not say

All three studies measure correlation, not causation. Companies that run design rigorously tend to run everything rigorously. That does not weaken the practical conclusion, because the mechanisms McKinsey identified (measuring design like revenue, cross-functional teams, continuous user testing) are operational habits, and operational habits can be adopted.

How do you measure the ROI of design?

Measure design the way you measure any investment: pick the business metric the design change is supposed to move, record the baseline, ship the change, and compare. Four metrics cover most product work:

1. Conversion rate: the share of users who complete a target action, such as sign-up, purchase, or activation.
2. Retention: whether the change keeps users coming back, read as churn or cohort retention.
3. Task completion time: how fast users get through the workflows the product exists to serve.
4. Engagement: depth of interaction with the features the change touched.

The instrument layer is A/B tests, funnel analytics, and session data. The discipline that separates measurement from theatre is the baseline: record the metric before the redesign, define the attribution window before you ship, and resist the urge to credit design for lifts that coincided with a pricing change or a traffic spike. A number without its baseline is a press release, not a measurement.

McKinsey documented an online gaming company where a small usability improvement to the home page was followed by a 25 percent increase in sales, and where polish beyond that point added almost nothing to users' value perception, so the team stopped. Both halves are the lesson. Measurement tells you when design pays and when to stop spending.

How does design ROI change as a company grows?

The metric that matters shifts with the stage of the business. What earns a return at launch wastes money at scale, and the reverse.

Early stage: speed to signal

Before product-market fit, design ROI is measured in learning per week. The job is to ship testable versions fast, watch real users, and kill weak directions early. Polish is negative ROI at this stage; every hour spent perfecting a screen that user testing will invalidate is an hour lost.

Growth stage: friction removal at scale

Once the model works, small percentages become large numbers. A one-point conversion improvement on a checkout that processes millions of orders is real revenue. Design work shifts to removing friction from proven journeys, building design systems so quality scales without headcount, and keeping the experience consistent across platforms.

Maturity: differentiation

In crowded markets, design becomes the moat. This is where the McKinsey quartile finding bites: adequate design returns nothing at maturity because every competitor has it. The return comes from experiences competitors have not matched, which requires the continuous user research and iteration habits the top quartile share.

Why does design ROI depend on engineering?

A design decision produces zero return until it ships. That makes engineering throughput a multiplier on design ROI, and it is the part most design-ROI conversations skip. In the Forrester study, better design understanding upstream cut development and testing time by 33 percent and halved design defects. The return showed up in the engineering budget, not the design budget.

This is why at Twistag we run design and product engineering as one pipeline rather than a handoff. Handoffs are where design intent decays: the flow that tested well gets simplified under deadline, the empty states never get built, and the version you measure is not the version you designed. We have written about how design and engineering merge in an AI-native pipeline, where the implementation cost of a design decision drops far enough that iteration speed stops being the constraint.

That drop is what changes the economics next. The 32-point spread McKinsey measured comes from a period when shipping a design change took a sprint. When AI-assisted implementation ships an interface change in a day, a team can test design decisions weekly instead of quarterly — and the compounding advantage will belong to the teams already measuring which changes pay.