Degreed Fresco Design System
Fresco is Degreed’s design system for its main platform. As core member of the design system team—the Core UI team—I am working to make sure we are building solid reusable components and writing clear documentation. This helps us be consistent, increase the speed of how we work, and ultimately save time and resources.
Full case study available upon request
The problem
Since joining Degreed in 2018 the design team has faced several problems that we needed to solve for, amongst others:
- The design team was working from a basic style guide and UI kit combined into one file shared on Dropbox. Having the team grow rapidly this resulted in a non-optimal workflow and caused conflicts when more people simultaneously worked on the file
- Projects were being saved on Dropbox with a basic file management system. It was challenging to know which projects were running, what their state was, or how to quickly reference a project and find solutions and patterns
- Components and styles were not all clearly mapped out in the file. This resulted in people reinventing these elements
- There was no close collaboration with the front-end team. They had no insight into our files, we didn’t speak the same language, and there was hardly any parity between both team’s components
The approach
Over the course of several years we took steps to solve these problems and improve the collaboration between designers. But also improve the collaboration and communication with front-end, PMs, and other product stakeholders. These steps would improve the speed and ease of use of our workflows, bring consistency to everything, and increase the visibility and discoverability of our design work.
The solution in two phases
We initially started with Abstract—Phase I—that served us well over the years, but still posed some issues for the team. In late 2021 we decided to pilot Figma—Phase II—and see if this would solve for the issues that we had with Abstract at that time.
Phase I: Abstract
I was one of the members tasked with moving our files and workflows into Abstract. This would help us have a centralized repository of our projects and libraries, acting as source of truth. We also looked into how we could best organize our files within Abstract, and how to best separate out our shared libraries for easy maintenance. Next to that I helped write documentation for our proposed workflow, file structure, and best practices. This also contributed to the actual start of our
design system Fresco
While this project was underway, it was also a good time to make an assessment of our components. I audited what we had in our UI kit and on the platform, which revealed many discrepancies.
One core component deserves some highlight; our buttons. We were using more buttons on the platform than we had in the kit. Most were also undocumented at the time, making it difficult to know what we truly had. I mapped them all out and made sure that they were properly added to the UI kit, documented, and in collaboration with front-end we removed all the odd ones out to have parity between the teams.
Phase II: Figma
Working with Sketch and Abstract improved our workflows significantly. But there were still issues that this combination could not solve. Next to that we wanted to decrease our stack of used tools consisting of Sketch, Abstract, and Invision. The design team decided to change to Figma.
During this period I transferred into a new role, working fulltime on our Design System within the Core UI team.
I lead the transition from Sketch and Abstract to Figma, making sure that all our components and pages were properly recreated, leveraging the features of Figma. Along the way also helping the team onboard this new tool.
To support this, I researched how to best organize our work within Figma, and documented this together with a workflow—the Figma Workflow at Degreed.
Core UI Team
As core member of the design system team—the Core UI team—I am working to make sure we are building solid reusable components, updating existing ones, and writing clear documentation.
Lastly, I’m collaborating with the front-end team to pilot a project for a possible transition to Angular Material and Tailwind CSS. My role is assessing all of our current components and consulting the front-end team whether these could be supported by Angular Material and Tailwind.