Design needs its own metrics
2026
I recently ran a survey of design leaders. The outcome was stark: most had to justify their team’s existence monthly, and their main source of metrics was team meetings. Unsurprisingly, most found this difficult.
From conversations with around thirty design leaders over the past few months, a clear pattern emerged. Budgets were tight, headcount was under threat, and AI was disrupting workflows. And design was being treated as a discretionary cost because leaders lacked robust measures to counter those pressures.
Those who did have data relied on NPS or CES surveys. These are useful guides to customer sentiment, but most design leaders are not responsible for the operations, pricing, product prioritisation, or regulatory decisions that shape them. So how do you accurately attribute the impact of a design team on a score that numerous teams legitimately lay claim to? You might manage it after a journey overhaul that is predominantly design-led, but that is a one-off, and such overhauls are rarely design-only. The same applies to revenue, cost reduction, or customer growth. Any serious business metric is affected by teams working in concert, and separating individual contributions becomes fraught with double counting and disagreement.
Other disciplines have solved this. Marketing teams can attribute ROI on spend with real precision. When budget is cut, the revenue drop is traceable. Engineering teams point to velocity, clock speed, and time to market. If you are not shipping, you are falling behind. They are not asked to prove their value every quarter because their outputs are legible.
Design needs the same. It needs metrics that design teams own, data points with clear disambiguation from other functions that show how the work is being done before the outcome arrives.
In my research over the last six months, the raw log data design teams already sit on provides exactly this. Activity from Figma, Miro, and Claude reveals whether teams stay focused, keep momentum, and iterate towards a goal together. These aren’t abstract ideals. In my data they correlate with positive business and customer outcomes.
This data also exposes operational truths. The ratio of designers to product and engineering colleagues shows where a small team is punching above its weight. Capacity and loading data shows where a team is overloaded. Bottlenecks in workflows show why projects stall. Licence waste identifies savings without headcount cuts.
These aren’t irrefutable “design delivered X value” numbers, but neither is engineering velocity. But they’re evidence, owned by design, that a disciplined design process - clear briefs, aligned objectives, focused work from small teams - produces measurably better outcomes. If you can prove that the process works, you earn the right to influence org design, strategic prioritisation, and budget decisions. And it gives design leaders the ammunition they need when the cost-cutting conversations come.