{"id":15032,"date":"2018-05-24T11:00:50","date_gmt":"2018-05-24T10:00:50","guid":{"rendered":"https:\/\/marvel7077.wpengine.com\/?p=15032"},"modified":"2021-01-18T04:54:58","modified_gmt":"2021-01-18T04:54:58","slug":"build-design-systems-scale","status":"publish","type":"post","link":"https:\/\/marvelapp.com\/blog\/build-design-systems-scale\/","title":{"rendered":"How to Build Design Systems to\u00a0Scale"},"content":{"rendered":"

In our ever-growing tech world, we need the design to scale as fast as other aspects of that world. But design doesn\u2019t scale easily since it\u2019s a mixture of art and science, form and content. So how to achieve this?<\/p>\n

Design Systems can be the answer.<\/em><\/strong><\/p>\n

Let\u2019s dive deeper into this and see what they are and how they can help scale design.<\/p>\n

Anyone who has ever played with Lego can understand what a design system is<\/a>. It\u2019s basically a Lego-like method+process that product teams need to make design and development more consistent. In fact, a lot of folks have already come to the idea that they need design systems<\/strong>. 69% of enterprise companies<\/a> either use a design system or are currently working on one.<\/p>\n

The core benefit of design systems is that they help establish consistency between the design and development processes and eliminate repetitive work. In a design system, everything starting with design patterns and ending with code references for each little bit of design are being documented. As a result, design and development go hand in hand.<\/p>\n

If this still sounds unfamiliar to you and you still cannot grasp the idea of design systems, just take a look at Google, Spotify, Atlassian or any other big brand. They have got their very own design systems.<\/p>\n

When Spotify\u2019s Design Director Stanley Wood joined the design team in 2012, he was shocked at the lack of consistency<\/a> between Spotify\u2019s products and features from the design perspective. And since a redesign didn\u2019t solve the problem, he decided to find a better solution. He knew that a team of distributed designers that is spread across different time zones should have a chance to work together to create a coherent experience.<\/p>\n

So, in 2014 GLUE (a Global Language for a Unified Experience) came into life as Spotify\u2019s Design Language System. It is available throughout the company and it has helped align design across all design teams within the company.<\/p>\n

\"\"<\/a>

Version 1 of Spotify\u2019s Guidelines | Stanley Wood<\/a><\/p><\/div>\n

Google\u2019s Material Design is another successful design system. Note that it evolved over the last few years to become what it is today. And it\u2019s still evolving. Do you remember how in 2011, Gmail was redesigned with flatter buttons? Then in 2012, Google Now introduced layered \u201ccards.\u201d These elements are now all formalized under Material design but those design upgrades back then were a part of a larger, very purposeful and deliberate process.<\/p>\n

What has been most impressive is Google\u2019s ambition to unify the design across a set of varied products. Hence, Material Design can serve as proof that design is POSSIBLE to scale.<\/p>\n

\"\"<\/a>

Image source<\/a><\/p><\/div>\n

But how?<\/strong><\/p>\n

Well, there are a few steps you would want to take to be able to build a design system to scale. Here you go:<\/p>\n

Check if you really need a design system<\/strong><\/p>\n

There is always the possibility that you might be carried away by the trends, the hype. A lot of us often start looking for solutions for non-existent problems. Yes, this does happen. But then, it turns out that we have not checked the problem yet. So, if a simple redesign will work for you, then there is most probably no need for coming up with a design system.<\/p>\n

The idea is that you should really do your homework and see if your company needs it or not. Building a design system or outsourcing it to a design and development company will take time and money. Estimate your needs properly before allocating resources to building a design system.<\/p>\n

Make sure your people know what to expect<\/strong><\/p>\n

Not everyone understands the value that design systems provide. So, your responsibility will be to teach your team what a design system is and how it can help make work easier. Be the influencer, the trend-maker in your company. Call it whatever you want.<\/p>\n

If you have decided to build a design system, the company is going to pay for it. So you might want to make sure all the stakeholders are positive about the idea. With this in mind, maybe it\u2019s worth involving someone from your team who has done this before or has helped someone earlier to build a design system? Think about it!<\/p>\n

Develop a game plan<\/strong><\/p>\n

Remember the famous quote? \u201cBy failing to plan, you are planning to fail.\u201d It seems obvious that you need a game plan but a lot of people don\u2019t plan the work in advance and then they get into trouble due to unexpected circumstance or force majeure. Of course, you cannot foresee a force majeure but you can at least have plan B if it happens.<\/p>\n

So, basically, the idea is that you need to define your mission or goal or a set of values and go for them. Each company has got its own industry-specific challenges, so take your time to evaluate the situation, explore the opportunities, the pain points for your team and customer in order to build the right system for your needs. And most importantly, focus on creating a design system that is consistent and scalable.<\/p>\n

Review and adopt best practices<\/strong><\/p>\n

Don\u2019t start from scratch, it might take too much time and resources. Review existing design systems and see which one is closer to your vision. Many companies have made their design systems publicly available. So, why not take a look at them?<\/p>\n

Conduct a UX\/UI audit<\/strong><\/p>\n

You are conducting a UX\/UI audit to know what you are working with. This whole thing is pretty much about documenting what exists. This can be time-consuming, but the game is worth the candle since through a UX\/UI audit you will discover:<\/p>\n