Loading…
11
A dev at a coffee shop in Austin said our design system saved his weekend.
He was trying to build a new feature fast and our component library's clear props kept him from having to write custom CSS. How do you measure that kind of time saved across a whole team?
3 comments
Log in to join the discussion
Log In3 Comments
wadeyoung3mo ago
That's exactly it though, the drop in CSS lines is the easiest number to point to and it's hard to argue with. @diana_bell74 yeah we started doing the same PR review time tracking and saw a 40% drop in the first quarter alone after we pushed the design system harder. What really sold leadership though was mapping that time saved back to how many more features each dev could ship per sprint. It wasn't perfect math but when you show them a team shipping 30% more stuff with fewer style bugs they stop asking questions.
3
diana_bell745mo ago
That story about the dev in Austin is exactly it. We track how often people use the library and look at pull request data. If a team goes from writing a ton of custom styles to mostly using our components, you can see the drop in CSS lines of code and review time. It's not a perfect number but the trend is clear.
1
keith_henderson5mo ago
Totally agree, that trend data tells the real story. We saw the same thing when teams fully bought in, the drop in CSS bugs was even more telling than lines of code. It shifts the whole conversation in code review from arguing about pixel spacing to actual logic. You stop asking "why did you rebuild the button" and start talking about the feature itself. That's the real win, when the system just gets out of the way.
6