If you've worked on design systems long enough, you've accumulated a heap of collateral to build the case for design systems. It’s just part of the job. Like you, I’ve done this. Then I did it again. And again. And again… Which, in retrospect, was silly. So, after an embarrassingly long amount of time, it dawned on me to make a reusable “presentation” which calculates the value of design systems. Then I made it available for everyone, including you. https://lnkd.in/gc7FVQCx This tool won’t replace your own custom case for design systems, but it may give you a boost. And who doesn’t like a little boost now and then?
Kelly Anneken
1mo
You’re amazing ✨
Dirk Bahrenburg
1mo
Just wow! PJ Onori So cool that you're sharing this 🙏. Would be super interesting to see also how you calculate these numbers for better transparency when presenting this to someone. I can imagine that this question could be raised 🤓.
Tiago Almeida
1mo
Lemme just save this 😅 160k buckerinos is def not what we make on these parts 😜
Josh Clark
1mo
I love this so much.
Darren Simons
1mo
Doing the “design lords” work. Should we call you Lord PJ now? 😂 thanks again for putting this together bud. Hope all is well!!
Ben Callahan
1mo
This is brilliant. Well done, sir!
Ashley Stell
1mo
This is really awesome.
Jeremy Cowan
1mo
Overrides are welcome with no need to detach the instance ? 😜
James Sann
1mo
Thanks for sharing PJ Onori. Reposting for greater visibility 🙌
UX, Accessibility, Inclusive Design | Dad of 3 | Proudly non-FAANG
1moIncredible. 🤩 Could you please explain "A design system team of 5 supporting 200 consumers would need to improve efficiency by ~2% to break even" a bit more? Is this a team of 5 designers building and maintaining a design system for 200 internal consumers who use it to build/develop/test? How do you calculate the efficiency gain to plug in for the ROI section?