arrow_back Battle Plan for Scaling CSS
Buttons Are Expensive
Submitted by Brajeshwar Oinam (@brajeshwar) on Friday, 25 August 2017
Technical level: Intermediate
A designer, engineer and QA are to design, build, and test some buttons. If these staff cost $100/hr, and it takes this team of three 200 hours combined to design, build and test buttons at this level of quality, then buttons cost $20,000. Buttons Are Expensive, So Make a Library.
Let’s imagine you combine a designer, engineer and QA specialist to design, build, and test these buttons. If these staff cost $100/hr, and it takes this team of three 200 hours combined to design, build and test buttons at this level of quality, then buttons cost $20,000.
200 hrs × $100/hr = $20,000 for Buttons
If your enterprise has 25 teams each making buttons, then it costs your enterprise $1,000,000 to have good buttons.
$20,000 × 50 teams = $1,000,000 for Buttons
That’s a million dollars, for buttons. And since buttons were made by 50 different teams, expect quality and consistency to vary significantly.
If buttons cost a million dollars, how much do our complicated components like header, cards, data grids, and modals cost? It’s not hard to imagine that they could cost millions of dollars each.
This is why we need a system to spread a visual language and reusable UI components across our enterprise of product development teams. So, on to how we can make and adopt such a system.
Brajeshwar is a Product designer who believes in simplicity, minimalism. He has an ardent willingness to push the bounds, envisioning the betterment of usable and practical solutions.