Framework · Design systems · 4 min read
Design system ROI estimate
A sum a finance partner can check line by line: the hours product teams get back from the system, minus the time they spend on it, next to what the system team costs, so you can say whether the system pays for itself and from what volume.
Screens your product teams build or change per quarter.
From tickets or design filesDesign plus engineering hours saved per screen, timed on matched tasks.
Median, not averageHours product teams spend on the system: contributions, migrations, questions.
From timesheets or estimatesHours of the people who build and run the system.
Shown next to the resultNet hours = Volume × Saving − Overhead − System cost
Use it when
- You write the budget ask for a design system team, or for more people on it.
- Someone in finance or leadership asks what the system gives back for what it costs.
- You report on the system every quarter and want the hours line to mean something.
How to use it
- Count the volume. How many screens your product teams build or change per quarter, from your tickets or design files. Output: one number, with where it came from.
- Time the saving per screen. Run the matched-task method from the lesson: two similar screens, one with the library and one without, and take the median. Ask engineers to time or estimate their side too, and mark it as estimated if it is. Output: design hours saved per screen, plus engineering hours saved per screen.
- Subtract what product teams spend on the system. Contributions, migrations, office hours, questions. Take them from timesheets or a fair estimate. Output: overhead hours per quarter.
- Put the system team's time next to it. The named people and their share of the week, in hours per quarter. Don't leave it out to make the sum look better. Output: system team hours per quarter.
- Turn hours into money and find the break-even. Multiply by the loaded hourly cost from finance (salary plus benefits and overhead). ROI = (value back − system team cost) ÷ system team cost. Break-even screens = (system team hours + overhead) ÷ hours saved per screen. Output: a yearly net, an ROI and the volume where the system starts to pay.
- Add what hours don't show, and repeat. Next to the sum: the repeated bugs fixed once, the distinct versions gone, the adoption share. Report in the same format every quarter. Output: a one-page estimate you can update.
Worked example
Tidewater runs Harbour, a design system used by two product teams. The lead takes the lesson's numbers: 40 screens a quarter, 7.5 design hours per screen without Harbour and 5.0 with it, and 30 hours a quarter that product teams spend on the system. Engineers estimate they save 4 hours per screen with the coded components (an estimate, and labelled as one). The system team is one designer and one engineer, one day a week each: about 192 hours a quarter. Finance gives a loaded cost of 45 an hour.
Product teams get 230 hours back per quarter (100 design, 160 engineering, minus 30). After the system team's 192 hours, that's 38 hours a quarter, or 152 a year. In money: 41,400 back a year against 34,560 for the system team, a net of 6,840, about 20%. Harbour pays for itself from about 35 screens a quarter. The lead presents this as a starting estimate, with the quality counts beside it. Change the numbers below to try your own.
The Harbour example, live. Put your own numbers in: every field is yours to fill from your tickets, timed tasks, timesheets and finance. It's an estimate to start a conversation, not a measurement.
Watch out for
- Someone else's percentage. A published "34% faster" is one team's best case, not your expected return. Use the method, measure your own number.
- The missing minus sign. A sum without the system team's cost breaks at the first question from finance. Show it, even when it makes the net small.
- Design hours only. Most of the saving is often in engineering and maintenance. Leave them out and you undersell the system; guess them without saying so and you oversell it.
- Hours treated as cash. Saved hours usually become more product work, not a smaller budget. Say "time back for product work", not "money saved".
Template
Copy this into the budget ask and fill it from your own sources.
System: Prepared by: Quarter:
Screens built or changed per quarter: ... (source: ...)
Design hours per screen, without / with: ... / ... (timed, median of ... people)
Engineering hours saved per screen: ... (timed / estimated)
Hours product teams spend on the system: ... (source: ...)
Hours back per quarter = screens x saved per screen - overhead = ...
System team hours per quarter: ... (names, share of week)
Net hours per quarter = hours back - system team hours = ...
Loaded hourly cost: ... (from finance)
Value back per year: ... System team cost per year: ...
ROI = (value back - cost) / cost = ...
Break-even screens per quarter = (system team hours + overhead) / saved per screen = ...
Not in the sum (counts): repeated bugs fixed once ..., versions removed ..., adoption ...%
Measured vs estimated: ...
- Design That ScalesDan MallBook · 2023 (Amazon)
- Measuring the value of design systemsFigma (external site)
- Loaded Cost of Employee TimeNN/g (external site)
- Design Systems Survey 2022Sparkbox (external site)
"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.