Table of contents

est 14 min read


Introduction At Sitecore and Templafy, we successfully developed and delivered two headless design systems, I am now sharing the insights and lessons learned from these two projects. Another lesson I shared was Creating a headless design system with Figma.

A common issue with a design systems is adoption.


Short term pain for long term gain Incorporating a design system into the day-to-day operations of product teams in a organization will present challenges, particularly when it's viewed as an additional burden. This perception is understandable, given the relentless pursuit of OKRs by product teams and the perpetual lack of time. Overcoming this hurdle is essential to realizing the significant benefits a design system can offer to a team.

To shift this perception, gaining buy-in from stakeholders is a premature first step in adopting a design system. As part of design system teams in the past, our focus has been on effectively communicating the tangible benefits to our stakeholders before starting the “design system project”.