Assign a “complexity score” for both design & engineering for each component in the design system.
Associate a reasonable estimate for number of hours for design & engineering for each scalar value in the “complexity score”.
Sum the total design & engineering hours.
Multiple the total hours by number of instances of each component throughout the Open edX platform.
Sum the resulting hours for each component to result in “Total Hours Saved”.
Discussion:
[Adam] Thoughts on the methodology and/or the hours for each scalar value? The hours are intended to take into account the following:
Design
User research
Design
Design review
User testing
Engineering
Implementation
Tests
Code review
QA
[Adam] Should this KPI assume teams have to re-design & re-engineer each component from scratch each time?
[Adam] What about components that have multiple variants?
E.g., it might take X hours of time to build the Button component for all its variants, but as a team re-implementing from scratch, they presumably don’t need to build each variant per usage so the “hours saved” might be inflated.