Make.com
Design System
Architecting a scalable design foundation that increased component adoption by 15x and unified the product experience.
Rebuilding the foundation of Make’s product design for scale, clarity, and the next generation of visual consistency. As Make grew, the product started to show its age. Interfaces looked inconsistent, the visual language was outdated, and teams were struggling to stay aligned. What began as a patchwork of local components turned into a complete rebuild of our design language, from tokens to documentation.
Timeline
2024 - Current
Role
Design Lead
Team
4 Devs
01
//Challenges
01
//Challenges
01
//Challenges
01
//Challenges
Challenges.
Before the redesign, the experience was fragmented. Designers were rebuilding components from scratch, wasting hours on patterns that should have been shared across the product. Developers faced the same frustration in code. Custom elements, mixed colors, missing accessibility, and no clear direction. There was no roadmap, no shared vision, and no owner of the system. The existing design system felt outdated and disconnected from what Make had become.
In the end, our users saw the result of that inconsistency every day.
02
//Solutions
02
//Solutions
02
//Solutions
02
//Solutions
Solutions.
When I took over the design system, it was my first time leading the design system project. I made plenty of wrong turns early on, but every one of them helped me learn how to build for scale. I restructured the token architecture to gain full control and flexibility. I redesigned every core component to feel modern, accessible, and ready for the next wave of product evolution.
Transparency became a key principle. Everyone at Make can see what we are building, give feedback, and influence priorities. At the same time, I stay directive about where we go and what belongs in the system. We hosted workshops to onboard designers, introduced new documentation in Supernova, and built small quality-of-life automations like the icon request flow. The development team played a huge part by turning design intent into real, reliable code.
03
//Results
03
//Results
03
//Results
03
//Results
Results.
The impact is clear. In the old system, designers made around 800 to 1,000 component inserts each month.
Today, that number is between 14,000 and 16,000, with only a 2% detachment rate. The new system drives every feature at Make. It’s consistent, scalable, and built to evolve with the product.
The best part is watching teams move faster and with more confidence, knowing that the foundation will support whatever comes next.
03
//Contact
LET'S TALK
03
//Contact
LET'S TALK
03
//Contact
LET'S TALK
03
//Contact
LET'S TALK
Let's Work
TOGETHER.
I'm passionate about design and always eager to keep learning and growing. Let's make something amazing together!
I'm passionate about design and always eager to keep learning and growing.
Let's make something amazing together!
I've collaborated with individuals, startups, and corporations, adapting to diverse needs and environments.
By blending creativity with strategic thinking, I deliver compelling solutions that meet project goals and enhance stakeholder engagement.
I've collaborated with individuals, startups, and corporations, adapting to diverse needs and environments. By blending creativity with strategic thinking, I deliver compelling solutions that meet project goals and enhance stakeholder engagement.
Make.com
Design System
Architecting a scalable design foundation that increased component adoption by 15x and unified the product experience.
Rebuilding the foundation of Make’s product design for scale, clarity, and the next generation of visual consistency. As Make grew, the product started to show its age. Interfaces looked inconsistent, the visual language was outdated, and teams were struggling to stay aligned. What began as a patchwork of local components turned into a complete rebuild of our design language, from tokens to documentation.
Timeline
2024 - Current
Role
Design Lead
Team
4 Devs
//Challenges
01
Challenges.
Before the redesign, the experience was fragmented. Designers were rebuilding components from scratch, wasting hours on patterns that should have been shared across the product. Developers faced the same frustration in code. Custom elements, mixed colors, missing accessibility, and no clear direction. There was no roadmap, no shared vision, and no owner of the system. The existing design system felt outdated and disconnected from what Make had become.
In the end, our users saw the result of that inconsistency every day.
//Solutions
02
Solutions.
When I took over the design system, it was my first time leading the design system project. I made plenty of wrong turns early on, but every one of them helped me learn how to build for scale. I restructured the token architecture to gain full control and flexibility. I redesigned every core component to feel modern, accessible, and ready for the next wave of product evolution.
Transparency became a key principle. Everyone at Make can see what we are building, give feedback, and influence priorities. At the same time, I stay directive about where we go and what belongs in the system. We hosted workshops to onboard designers, introduced new documentation in Supernova, and built small quality-of-life automations like the icon request flow. The development team played a huge part by turning design intent into real, reliable code.
//Results
03
Results.
The impact is clear. In the old system, designers made around 800 to 1,000 component inserts each month.
Today, that number is between 14,000 and 16,000, with only a 2% detachment rate. The new system drives every feature at Make. It’s consistent, scalable, and built to evolve with the product.
The best part is watching teams move faster and with more confidence, knowing that the foundation will support whatever comes next.
//Contact
LET'S TALK
Let's Work
TOGETHER.
I'm passionate about design and always eager to keep learning and growing. Let's make something amazing together!
I've collaborated with individuals, startups, and corporations, adapting to diverse needs and environments.
By blending creativity with strategic thinking, I deliver compelling solutions that meet project goals and enhance stakeholder engagement.
Make.com
Design System
Architecting a scalable design foundation that increased component adoption by 15x and unified the product experience.
Rebuilding the foundation of Make’s product design for scale, clarity, and the next generation of visual consistency. As Make grew, the product started to show its age. Interfaces looked inconsistent, the visual language was outdated, and teams were struggling to stay aligned. What began as a patchwork of local components turned into a complete rebuild of our design language, from tokens to documentation.
Timeline
2024 - Current
Role
Design Lead
Team
4 Devs
//Challenges
01
Challenges.
Before the redesign, the experience was fragmented. Designers were rebuilding components from scratch, wasting hours on patterns that should have been shared across the product. Developers faced the same frustration in code. Custom elements, mixed colors, missing accessibility, and no clear direction. There was no roadmap, no shared vision, and no owner of the system. The existing design system felt outdated and disconnected from what Make had become.
In the end, our users saw the result of that inconsistency every day.
//Solutions
02
Solutions.
When I took over the design system, it was my first time leading the design system project. I made plenty of wrong turns early on, but every one of them helped me learn how to build for scale. I restructured the token architecture to gain full control and flexibility. I redesigned every core component to feel modern, accessible, and ready for the next wave of product evolution.
Transparency became a key principle. Everyone at Make can see what we are building, give feedback, and influence priorities. At the same time, I stay directive about where we go and what belongs in the system. We hosted workshops to onboard designers, introduced new documentation in Supernova, and built small quality-of-life automations like the icon request flow. The development team played a huge part by turning design intent into real, reliable code.
//Results
03
Results.
The impact is clear. In the old system, designers made around 800 to 1,000 component inserts each month.
Today, that number is between 14,000 and 16,000, with only a 2% detachment rate. The new system drives every feature at Make. It’s consistent, scalable, and built to evolve with the product.
The best part is watching teams move faster and with more confidence, knowing that the foundation will support whatever comes next.
//Contact
LET'S TALK
Let's Work
TOGETHER.
I'm passionate about design and always eager to keep learning and growing. Let's make something amazing together!
I've collaborated with individuals, startups, and corporations, adapting to diverse needs and environments. By blending creativity with strategic thinking, I deliver compelling solutions that meet project goals and enhance stakeholder engagement.
Make.com
Design System
Architecting a scalable design foundation that increased component adoption by 15x and unified the product experience.
Rebuilding the foundation of Make’s product design for scale, clarity, and the next generation of visual consistency. As Make grew, the product started to show its age. Interfaces looked inconsistent, the visual language was outdated, and teams were struggling to stay aligned. What began as a patchwork of local components turned into a complete rebuild of our design language, from tokens to documentation.
Timeline
2024 - Current
Role
Design Lead
Team
4 Devs
//Challenges
01
Challenges.
Before the redesign, the experience was fragmented. Designers were rebuilding components from scratch, wasting hours on patterns that should have been shared across the product. Developers faced the same frustration in code. Custom elements, mixed colors, missing accessibility, and no clear direction. There was no roadmap, no shared vision, and no owner of the system. The existing design system felt outdated and disconnected from what Make had become.
In the end, our users saw the result of that inconsistency every day.
//Solutions
02
Solutions.
When I took over the design system, it was my first time leading the design system project. I made plenty of wrong turns early on, but every one of them helped me learn how to build for scale. I restructured the token architecture to gain full control and flexibility. I redesigned every core component to feel modern, accessible, and ready for the next wave of product evolution.
Transparency became a key principle. Everyone at Make can see what we are building, give feedback, and influence priorities. At the same time, I stay directive about where we go and what belongs in the system. We hosted workshops to onboard designers, introduced new documentation in Supernova, and built small quality-of-life automations like the icon request flow. The development team played a huge part by turning design intent into real, reliable code.
//Results
03
Results.
The impact is clear. In the old system, designers made around 800 to 1,000 component inserts each month.
Today, that number is between 14,000 and 16,000, with only a 2% detachment rate. The new system drives every feature at Make. It’s consistent, scalable, and built to evolve with the product.
The best part is watching teams move faster and with more confidence, knowing that the foundation will support whatever comes next.
//Contact
LET'S TALK
Let's Work
TOGETHER.
I'm passionate about design and always eager to keep learning and growing. Let's make something amazing together!
I've collaborated with individuals, startups, and corporations, adapting to diverse needs and environments. By blending creativity with strategic thinking, I deliver compelling solutions that meet project goals and enhance stakeholder engagement.