#designsystem
#web
#Sketch
#Figma
Increasing design system adoption at KVK
Increasing design system adoption at KVK
Increasing design system adoption at KVK
Increasing design system adoption at KVK
Increasing design system adoption at KVK
Increasing design system adoption at KVK
At KVK, I am part of the design system team (Team Matrix) which is focused on curating, documenting, and creating usable and accessible digital experiences together with the product development teams. I also advocate for adoption and collaboration in the organization through facilitating workshops and mentoring peers to effectively use the design system.
At KVK, I am part of the design system team (Team Matrix) which is focused on curating, documenting, and creating usable and accessible digital experiences together with the product development teams. I also advocate for adoption and collaboration in the organization through facilitating workshops and mentoring peers to effectively use the design system.
At KVK, I am part of the design system team (Team Matrix) which is focused on curating, documenting, and creating usable and accessible digital experiences together with the product development teams. I also advocate for adoption and collaboration in the organization through facilitating workshops and mentoring peers to effectively use the design system.
At KVK, I am part of the design system team (Team Matrix) which is focused on curating, documenting, and creating usable and accessible digital experiences together with the product development teams. I also advocate for adoption and collaboration in the organization through facilitating workshops and mentoring peers to effectively use the design system.
At KVK, I am part of the design system team (Team Matrix) which is focused on curating, documenting, and creating usable and accessible digital experiences together with the product development teams. I also advocate for adoption and collaboration in the organization through facilitating workshops and mentoring peers to effectively use the design system.
At KVK, I am part of the design system team (Team Matrix) which is focused on curating, documenting, and creating usable and accessible digital experiences together with the product development teams. I also advocate for adoption and collaboration in the organization through facilitating workshops and mentoring peers to effectively use the design system.
2022 - present
Timeline
Interaction & Product Designer
Role
2022 - present
Timeline
Interaction & Product Designer
Role
Background
Background
Team Matrix was already rocking it with our top-notch component-based design system and a bunch of talented designers and devs. But, the team struggled when it came to getting designers in the org to really dive into using it.
The organisation, at this point, has twelve product teams working on the online experience for KVK, meaning that 12 product designers are ideally connected to the design system. It wasn't just about telling these designers, 'Hey, use this.' We really needed to connect, understand each other, and work together more. We saw some cool changes, like some designers who used to hardly ever use the system components (for various reasons) suddenly shooting to the top of the usage charts.
Team Matrix was already rocking it with our top-notch component-based design system and a bunch of talented designers and devs. But, the team struggled when it came to getting designers in the org to really dive into using it.
The organisation, at this point, has twelve product teams working on the online experience for KVK, meaning that 12 product designers are ideally connected to the design system. It wasn't just about telling these designers, 'Hey, use this.' We really needed to connect, understand each other, and work together more. We saw some cool changes, like some designers who used to hardly ever use the system components (for various reasons) suddenly shooting to the top of the usage charts.
Goals
Goals
1
Improve collaboration between product designers and the design system (team)
I noticed that the users and the design system team weren't really on the same page. Everyone's super skilled in what they do, but there's been some friction, especially about the design system not being flexible enough and not enough talk happening between the two groups.
1
Improve collaboration between product designers and the design system (team)
I noticed that the users and the design system team weren't really on the same page. Everyone's super skilled in what they do, but there's been some friction, especially about the design system not being flexible enough and not enough talk happening between the two groups.
1
Improve collaboration between product designers and the design system (team)
I noticed that the users and the design system team weren't really on the same page. Everyone's super skilled in what they do, but there's been some friction, especially about the design system not being flexible enough and not enough talk happening between the two groups.
2
Ensure a smooth transition from Sketch to Figma for designers
At KVK's design team, we're always looking to stay up-to-date with what's best in the industry. That's why we decided to switch to Figma, seeing how it could really boost our design systems' component library with its cool features. This was my second time facilitating the switch from Sketch to Figma from a design system point of view.
2
Ensure a smooth transition from Sketch to Figma for designers
At KVK's design team, we're always looking to stay up-to-date with what's best in the industry. That's why we decided to switch to Figma, seeing how it could really boost our design systems' component library with its cool features. This was my second time facilitating the switch from Sketch to Figma from a design system point of view.
2
Ensure a smooth transition from Sketch to Figma for designers
At KVK's design team, we're always looking to stay up-to-date with what's best in the industry. That's why we decided to switch to Figma, seeing how it could really boost our design systems' component library with its cool features. This was my second time facilitating the switch from Sketch to Figma from a design system point of view.
Figma library analytics showing component inserts and adoption
Figma library analytics showing component inserts and adoption
Work & learnings
Work & learnings
1
Introducing office hours
Our users told us that our requests for feedback on the design system often got lost in the shuffle, especially since we were only reaching out through Microsoft Teams. With everyone's crazy schedules, it was easy for our messages to get overlooked. So, we realized we needed a dedicated time to get together and chat about everything related to the 'Trinity design system.' That's where the Trinity office hours came in. We set up these calls to give users a chance to ask us anything they wanted about using the system. It was also a perfect time for them to share their thoughts and suggestions. This really helped us work better together and make the system even stronger.
1
Introducing office hours
Our users told us that our requests for feedback on the design system often got lost in the shuffle, especially since we were only reaching out through Microsoft Teams. With everyone's crazy schedules, it was easy for our messages to get overlooked. So, we realized we needed a dedicated time to get together and chat about everything related to the 'Trinity design system.' That's where the Trinity office hours came in. We set up these calls to give users a chance to ask us anything they wanted about using the system. It was also a perfect time for them to share their thoughts and suggestions. This really helped us work better together and make the system even stronger.
1
Introducing office hours
Our users told us that our requests for feedback on the design system often got lost in the shuffle, especially since we were only reaching out through Microsoft Teams. With everyone's crazy schedules, it was easy for our messages to get overlooked. So, we realized we needed a dedicated time to get together and chat about everything related to the 'Trinity design system.' That's where the Trinity office hours came in. We set up these calls to give users a chance to ask us anything they wanted about using the system. It was also a perfect time for them to share their thoughts and suggestions. This really helped us work better together and make the system even stronger.
2
The 'magic' tool: Figma
Initially we believed that switching to Figma was the utlimate magic spell that would solve all our adoption problems, because working with Trinity would become easier as Figma offered more options for design system libraries. However, we quickly realised that Figma is 'just another tool' in a toolbox that keeps expanding for designers. So that's exactly what we decided on seeing it as. A tool to change the culture around our design system and start fresh. Therefore, I saw the switch from Sketch to Figma as a great chance to get our designers together to learn from each other. Our team educated designers how to use auto-layout, properties, frames, variants, etc. And sprinkling a little design system component here and there to serve as an example helped the designers learn Figma by using the design system. I also facilitated workshops with the team that allowed us to move our component library from Sketch to Figma with the help of our users. All designers came together to collaboratively build components in Figma. This created a shared understanding of the work we put into a building a component and a shared responsibility for the design system and the work we put out as a collective of designers for KVK.
2
The 'magic' tool: Figma
Initially we believed that switching to Figma was the utlimate magic spell that would solve all our adoption problems, because working with Trinity would become easier as Figma offered more options for design system libraries. However, we quickly realised that Figma is 'just another tool' in a toolbox that keeps expanding for designers. So that's exactly what we decided on seeing it as. A tool to change the culture around our design system and start fresh. Therefore, I saw the switch from Sketch to Figma as a great chance to get our designers together to learn from each other. Our team educated designers how to use auto-layout, properties, frames, variants, etc. And sprinkling a little design system component here and there to serve as an example helped the designers learn Figma by using the design system. I also facilitated workshops with the team that allowed us to move our component library from Sketch to Figma with the help of our users. All designers came together to collaboratively build components in Figma. This created a shared understanding of the work we put into a building a component and a shared responsibility for the design system and the work we put out as a collective of designers for KVK.
2
The 'magic' tool: Figma
Initially we believed that switching to Figma was the utlimate magic spell that would solve all our adoption problems, because working with Trinity would become easier as Figma offered more options for design system libraries. However, we quickly realised that Figma is 'just another tool' in a toolbox that keeps expanding for designers. So that's exactly what we decided on seeing it as. A tool to change the culture around our design system and start fresh. Therefore, I saw the switch from Sketch to Figma as a great chance to get our designers together to learn from each other. Our team educated designers how to use auto-layout, properties, frames, variants, etc. And sprinkling a little design system component here and there to serve as an example helped the designers learn Figma by using the design system. I also facilitated workshops with the team that allowed us to move our component library from Sketch to Figma with the help of our users. All designers came together to collaboratively build components in Figma. This created a shared understanding of the work we put into a building a component and a shared responsibility for the design system and the work we put out as a collective of designers for KVK.
3
Collaborate and educate on design system usage and maintenance
I'm all about soaking up as much as I can from the design system we're building together. The more I know, the better I can help others, whether that's one-on-one or through our docs. But honestly, it's the face-to-face chats with our users that are the real gold. These conversations let me see firsthand how our product's really doing for them. So seeking out one-on-one time with the users became a priority. Listening to their needs, hearing their complaints if they had any, and translate that to issues on our backlog. It also involved saying 'no' to requests sometimes, which sucks, but instead I've always tried providing an existing solution from the system to help them on their way.
3
Collaborate and educate on design system usage and maintenance
I'm all about soaking up as much as I can from the design system we're building together. The more I know, the better I can help others, whether that's one-on-one or through our docs. But honestly, it's the face-to-face chats with our users that are the real gold. These conversations let me see firsthand how our product's really doing for them. So seeking out one-on-one time with the users became a priority. Listening to their needs, hearing their complaints if they had any, and translate that to issues on our backlog. It also involved saying 'no' to requests sometimes, which sucks, but instead I've always tried providing an existing solution from the system to help them on their way.
3
Collaborate and educate on design system usage and maintenance
I'm all about soaking up as much as I can from the design system we're building together. The more I know, the better I can help others, whether that's one-on-one or through our docs. But honestly, it's the face-to-face chats with our users that are the real gold. These conversations let me see firsthand how our product's really doing for them. So seeking out one-on-one time with the users became a priority. Listening to their needs, hearing their complaints if they had any, and translate that to issues on our backlog. It also involved saying 'no' to requests sometimes, which sucks, but instead I've always tried providing an existing solution from the system to help them on their way.
Note from my performance review - 2023: "Nearly all designers in the design practice noted that the communication with the design system team improved greatly in the last year. I attribute that in big part to your efforts and collaboration with the (design) practice."
Frank de Wit
Design Practice Lead
Conclusion
So, that's the story of how we at Team Matrix turned things around with our design system. It's been amazing working on Trinity so far. We started off with some real challenges getting our designers on board, but we tackled them head-on. Setting up those office hours was a game changer – it gave everyone a chance to chat, give feedback, and just get more involved with the 'Trinity design system.' Switching to Figma wasn't just about a new tool; it was about bringing us all together.
We all got our hands dirty rebuilding our component library in Figma, which really helped everyone feel like they were part of the process. And we invested time in one-on-one talks and group sessions where we really dug into how to use and maintain the system.
The coolest part? Seeing designers who were barely using the system before now leading the pack in component usage. It just goes to show how a little teamwork and a lot of listening can make a huge difference. I can definitely say my passion lies in working in design systems and building bridges between the users and the system, connecting the dots, and making the system work for everyone.
I've talked about how we're handeling design system adoption at KVK at the NL Design System Week 2023 back in October. Check out the recording here!