The measurement problem
Advocates for a dedicated design system often have to prove its value to leadership, and the question usually comes down to whether it is worth the cost. The difficulty is that developer productivity, front-end quality, and to some degree accessibility are nebulous quantities. Google's Core Web Vitals are frequently cited as the counterexample, since they turn a problem into a number and suggest concrete next steps.
Design systems have no equivalent score. There is no metric that tells a team it should staff a design systems group in order to move a rating from 60/100. Such an instrument may never exist.
Sparkbox's experiment
Sparkbox set out to test the question directly with its eight developers. Each participant built a form by hand, then built it again using IBM's Carbon design system, which none of them had used before.
What the numbers showed
Using a design system made a simple form page 47% faster to develop versus coding it from scratch. The median time for the scratch submissions was 4.2 hours compared to the 2 hour median time for Carbon submissions. The Carbon timing included the time the developers spent familiarizing themselves with the design system.
The comparison is notable because the Carbon timings were recorded with unfamiliarity included. Developers already fluent in the system would presumably build the same forms considerably faster than these first results.



