Our 4 convictions for a successful Design Language System in 2024
Maxime Frere
Principal Designer
Feb 28, 2024
Welcome to the first edition of our Open! newsletter.
Every month, one of our experts shares their hot takes on a specific topic in Design or Tech, hopefully giving you a better understanding and helping you save time.
In this inaugural newsletter, we want to discuss Design Language Systems (DLS)!
And with a decade in this field, Maxime Frere, Principal Designer at Source has condensed his expertise into 4 powerful convictions for DLS success in 2024.
Summary
If you’re not involved in DLS yet, you’re off track
Embrace code as the source of truth, not design tools
Strive for design excellence, not just industrialization
DLS is more than design, it’s a transformative journey
1. If you’re not involved in DLS yet, you’re off track
Design Language System is more than a buzzword; it's a strategic investment essential for transforming companies into more productive and competitive businesses.
In 2024, chances are high that your competitors have already invested in a DLS, enabling them to ship faster and include more features while maintaining visual consistency across platforms. This ultimately leads to a better user experience and contributes to gaining market share. Take Apple as an example; their clean and consistent experience across various devices is one of the reasons why they achieve such a strong brand preference.
If your company has yet to embark on a DLS, the good news is that you can start small. In fact, we believe it's best to begin as small as possible. This approach minimizes initial investment, facilitates validation and iteration, and presents an opportunity for achieving design excellence.
2. Embrace code as the source of truth, not design tools
End users don’t interact with design tools, they engage with code!
While tools like Figma or Framer offer quick and easy interface creation, their capabilities are limited compared to what web and code can accomplish.
Designing interfaces solely based on the capabilities of design tools leads to a leveling down of quality. Despite the improvements made by Figma or Framer to facilitate collaboration between designers and front-end engineers, this approach often creates communication challenges between both disciplines.
Therefore, we strongly advocate for establishing code as the source of truth between Design & Tech teams.
Designing interfaces solely based on the capabilities of design tools leads to a leveling down of quality.
By prioritizing code over design tools, our approach to Design Language Systems aims to seamlessly align designers' workflows with the processes and preferences of developers.
One of the reasons why we emphasize the term “Design Language System” over “Design System” is the creation of a standardized vocabulary. This language not only bridges the gap between design and code but also enables expression across various mediums, from digital to physical products and print materials.
And while various KPIs can measure the success of a DLS, for me the most important outcome often transcends metrics: it’s fostering synergies between Design and Tech teams. As I once heard from a Head of IT, "seeing my dev team coming to work with a smile is better than any metric".
3. Strive for design excellence, not just industrialization
Building a Design Language System should be seen as an opportunity for design excellence. Many people prioritize the aspect of industrialization, but it’s important to remember that if we standardize mediocrity, we will only achieve mediocrity.
Every decision within the core of a DLS has a significant impact on the quality of interfaces, particularly in complex interfaces.
If we standardize mediocrity, we will only achieve mediocrity.
Establishing solid design foundations then becomes crucial. Well-built foundations are not only difficult to dispute but they can persuade designers and front-end engineers to adopt the DLS.
Attention to detail is essential when creating color palettes, selecting typography, and choosing illustration assets like icons. Each design decision should be meticulously explained and justified to ensure a commitment to excellence is maintained across all assets.
4. DLS is more than design, it’s a transformative journey
People often neglect the ability of Design Language Systems to transform organizations with low design maturity.
While it may sound like a heavy and complex process, with numerous dimensions to consider, I have never witnessed such profound influence brought by the adoption of a DLS.
In fact, when we start DLS programs for clients, it is often necessary to scale down their ambitions and adopt a bottom-up approach. Although the main goal of is to scale design capabilities, initiating with a modest scope, such as a Proof of Concept, paves the way for broader buy-in.
People often neglect the ability of Design Language Systems to transform organizations with low design maturity.
I’ve talked about how a code-oriented DLS brings significant changes in how Design & Tech teams collaborate. When they are aligned, we find that everyone starts seeking solutions instead of hindering progress in any way. Often, we see that this extends beyond the DLS, and methods and processes spread across teams.
However, even if operational-level adoption is successful, we’ve seen that many companies encounter a glass ceiling that limits the further growth of the product (the DLS).
And to achieve widespread adoption, it is sometimes necessary to promote or enforce it.
Another crucial factor for successful adoption is the extent to which the company can take ownership of the DLS. Therefore, it should be adapted to fit the company's operational capabilities, with an appropriate level of flexibility. And just like any other language, the DLS will live and evolve over time.
Our ultimate goal is to transfer the product to the clients so they can independently operate it.
A proven productivity boost
Now that you know our perspective on Design Language Systems, let's explore what others have to say. Numerous studies have demonstrated the various benefits of implementing a DLS. We’ve selected three.
More efficient Design production
30% to 50% reduction in time spent on design work when using a Design System. (Source: zeroheight)
Faster development for Tech
Up to 50% less time to complete a front-end development task when using a DLS. (Source: Figma)
Savings and revenue growth
+20% in revenue thanks to a more consistent and trustworthy digital ecosystem. (Source: Forbes)
Welcome to the first edition of our Open! newsletter.
Every month, one of our experts shares their hot takes on a specific topic in Design or Tech, hopefully giving you a better understanding and helping you save time.
In this inaugural newsletter, we want to discuss Design Language Systems (DLS)!
And with a decade in this field, Maxime Frere, Principal Designer at Source has condensed his expertise into 4 powerful convictions for DLS success in 2024.
Summary
If you’re not involved in DLS yet, you’re off track
Embrace code as the source of truth, not design tools
Strive for design excellence, not just industrialization
DLS is more than design, it’s a transformative journey
1. If you’re not involved in DLS yet, you’re off track
Design Language System is more than a buzzword; it's a strategic investment essential for transforming companies into more productive and competitive businesses.
In 2024, chances are high that your competitors have already invested in a DLS, enabling them to ship faster and include more features while maintaining visual consistency across platforms. This ultimately leads to a better user experience and contributes to gaining market share. Take Apple as an example; their clean and consistent experience across various devices is one of the reasons why they achieve such a strong brand preference.
If your company has yet to embark on a DLS, the good news is that you can start small. In fact, we believe it's best to begin as small as possible. This approach minimizes initial investment, facilitates validation and iteration, and presents an opportunity for achieving design excellence.
2. Embrace code as the source of truth, not design tools
End users don’t interact with design tools, they engage with code!
While tools like Figma or Framer offer quick and easy interface creation, their capabilities are limited compared to what web and code can accomplish.
Designing interfaces solely based on the capabilities of design tools leads to a leveling down of quality. Despite the improvements made by Figma or Framer to facilitate collaboration between designers and front-end engineers, this approach often creates communication challenges between both disciplines.
Therefore, we strongly advocate for establishing code as the source of truth between Design & Tech teams.
Designing interfaces solely based on the capabilities of design tools leads to a leveling down of quality.
By prioritizing code over design tools, our approach to Design Language Systems aims to seamlessly align designers' workflows with the processes and preferences of developers.
One of the reasons why we emphasize the term “Design Language System” over “Design System” is the creation of a standardized vocabulary. This language not only bridges the gap between design and code but also enables expression across various mediums, from digital to physical products and print materials.
And while various KPIs can measure the success of a DLS, for me the most important outcome often transcends metrics: it’s fostering synergies between Design and Tech teams. As I once heard from a Head of IT, "seeing my dev team coming to work with a smile is better than any metric".
3. Strive for design excellence, not just industrialization
Building a Design Language System should be seen as an opportunity for design excellence. Many people prioritize the aspect of industrialization, but it’s important to remember that if we standardize mediocrity, we will only achieve mediocrity.
Every decision within the core of a DLS has a significant impact on the quality of interfaces, particularly in complex interfaces.
If we standardize mediocrity, we will only achieve mediocrity.
Establishing solid design foundations then becomes crucial. Well-built foundations are not only difficult to dispute but they can persuade designers and front-end engineers to adopt the DLS.
Attention to detail is essential when creating color palettes, selecting typography, and choosing illustration assets like icons. Each design decision should be meticulously explained and justified to ensure a commitment to excellence is maintained across all assets.
4. DLS is more than design, it’s a transformative journey
People often neglect the ability of Design Language Systems to transform organizations with low design maturity.
While it may sound like a heavy and complex process, with numerous dimensions to consider, I have never witnessed such profound influence brought by the adoption of a DLS.
In fact, when we start DLS programs for clients, it is often necessary to scale down their ambitions and adopt a bottom-up approach. Although the main goal of is to scale design capabilities, initiating with a modest scope, such as a Proof of Concept, paves the way for broader buy-in.
People often neglect the ability of Design Language Systems to transform organizations with low design maturity.
I’ve talked about how a code-oriented DLS brings significant changes in how Design & Tech teams collaborate. When they are aligned, we find that everyone starts seeking solutions instead of hindering progress in any way. Often, we see that this extends beyond the DLS, and methods and processes spread across teams.
However, even if operational-level adoption is successful, we’ve seen that many companies encounter a glass ceiling that limits the further growth of the product (the DLS).
And to achieve widespread adoption, it is sometimes necessary to promote or enforce it.
Another crucial factor for successful adoption is the extent to which the company can take ownership of the DLS. Therefore, it should be adapted to fit the company's operational capabilities, with an appropriate level of flexibility. And just like any other language, the DLS will live and evolve over time.
Our ultimate goal is to transfer the product to the clients so they can independently operate it.
A proven productivity boost
Now that you know our perspective on Design Language Systems, let's explore what others have to say. Numerous studies have demonstrated the various benefits of implementing a DLS. We’ve selected three.
More efficient Design production
30% to 50% reduction in time spent on design work when using a Design System. (Source: zeroheight)
Faster development for Tech
Up to 50% less time to complete a front-end development task when using a DLS. (Source: Figma)
Savings and revenue growth
+20% in revenue thanks to a more consistent and trustworthy digital ecosystem. (Source: Forbes)
Enjoyed this article? You’ll love Open!
Join our newsletter to get the very best of our content every month — insights, client stories and design experiments, straight to your inbox.
Work with Source.paris
Since 2014, we’ve been turning complex challenges into clear and desirable user experiences.
From product strategy to full-scale rollout, our team brings structure, speed and sharp execution — with no compromises.
Enjoyed this article? You’ll love Open!
Join our newsletter to get the very best of our content every month — insights, client stories and design experiments, straight to your inbox.
Work with Source.paris
Since 2014, we’ve been turning complex challenges into clear and desirable user experiences.
From product strategy to full-scale rollout, our team brings structure, speed and sharp execution — with no compromises.
Enjoyed this article? You’ll love Open!
Join our newsletter to get the very best of our content every month — insights, client stories and design experiments, straight to your inbox.
Work with Source.paris
Since 2014, we’ve been turning complex challenges into clear and desirable user experiences.
From product strategy to full-scale rollout, our team brings structure, speed and sharp execution — with no compromises.
Enjoyed this article? You’ll love Open!
Join our newsletter to get the very best of our content every month — insights, client stories and design experiments, straight to your inbox.
Work with Source.paris
Since 2014, we’ve been turning complex challenges into clear and desirable user experiences.
From product strategy to full-scale rollout, our team brings structure, speed and sharp execution — with no compromises.
Read next
Apr 8, 2025
Apr 8, 2025
Apr 8, 2025
Apr 8, 2025