<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Adam Zielonko on Medium]]></title>
        <description><![CDATA[Stories by Adam Zielonko on Medium]]></description>
        <link>https://medium.com/@adamzielonko?source=rss-d014b3a63cd5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Adam Zielonko on Medium</title>
            <link>https://medium.com/@adamzielonko?source=rss-d014b3a63cd5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 11:50:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adamzielonko/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Design Systems. What, How, and Why Your Digital Product Needs One]]></title>
            <link>https://medium.com/netguru/design-systems-what-how-and-why-your-digital-product-needs-one-e37d52dd36c7?source=rss-d014b3a63cd5------2</link>
            <guid isPermaLink="false">https://medium.com/p/e37d52dd36c7</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Adam Zielonko]]></dc:creator>
            <pubDate>Mon, 23 Mar 2020 11:39:12 GMT</pubDate>
            <atom:updated>2020-03-23T11:39:12.454Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ohdczbhi13ZlGuRNk1T7UQ.jpeg" /><figcaption>The questions that a design system answers / Illustration: <a href="https://dribbble.com/aga-koniuszek">Agnieszka Koniuszek</a></figcaption></figure><p>Many things in the digital world are born out of necessity. That is, we need to find a way to do something in a smoother, more efficient manner in order to create something of higher value.</p><p>In the world of digital design, this concept rings truer each and every day.</p><p>And a design system is one thing that developers, designers and CEOs alike can use to increase the speed of the design process and ensure the product is designed in a coherent manner.</p><p>But <a href="https://www.netguru.com/blog/design-systems-in-react-native">what on earth is a design system?</a></p><p>Well, if you’ve come here asking that question, you’re in the right place.</p><p>This article will explain what a design system is and how it can be advantageous to a digital product.</p><p>You’ll even see how some of the digital realm’s leading brands, like Airbnb, Atlassian, and Shopify are leveraging their design systems to spread brand awareness.</p><p>“Design systems are an investment. Many companies don’t employ people to focus on design systems until the inefficiencies of not having one become too painful to bear” — says Diana Mounter from GitHub in <a href="https://www.youtube.com/watch?v=Hx02SaL_IH0&amp;t=451s">her fantastic presentation on design systems.</a></p><p>If your digital brand values:</p><ul><li>A well-crafted user-experience</li><li>A consistent and easy-to-use environment for designers</li><li>Robust and versatile problem-solving</li></ul><p>Then a design system is going to be the next thing you should set your sights on.</p><h3>Design system — a system of designing?</h3><p>Without digging out the Oxford dictionary, let’s try and define both these words:</p><p><strong>Design: </strong>The art of creating and arranging imagery, shapes, and colours to create something visually appealing and/or functional.</p><p><strong>System: </strong>A series of things working together in harmony; a complex whole.</p><p>So with these two things now clearly defined, are you able to figure out what a design system, in theory, actually is?</p><p>A design system consists of two things: the library and the documentation. Together, they define the brand’s core <a href="https://www.netguru.com/services/ux-review">UX</a> and UI, like visual assets, your logo, typography, colors, grid. A design system also includes UI components, their documentation, and the code snippets to facilitate developers using them across existing products.</p><p>It’s the rules, constraints, and principles implemented in both design and code.</p><p>These elements apply to everything — colour, typography, spacing, and layout. Interestingly, a design system should also encompass non-visual elements such as tone of voice, vocabulary, grammar, and audio cues.</p><p>All these components are designed separately, but are brought together to create a single source of truth.</p><p>It may be compared to front-end and back-end in design. So, on one hand we have all of these reusable components (which are visual), and on the other hand we have the codified counterparts of those elements, and thus they can be used by developers.</p><p>Let’s take a look at all this in action.</p><p>Within your design system are the standards adhered to when designing, for example, a user’s default icon. It doesn’t say how it needs to look, (that’s up to the creative mind of your designer) but your design system indicates the process to be followed in order to create it.</p><p>Simply put, a design system consists of your visual (and non-visual) elements and the processes to which they can be altered.</p><p>It’s worth noting that a good design system also includes naming conventions, file structure, and other ‘formalities’ of working in a digital environment.</p><p>After all, its sole purpose is to speed up and simplify the way designers work — this also includes many file management procedures.</p><p>Let’s dig a little deeper by taking a step back for a moment.</p><h3>Style guide vs design system</h3><p>Let me introduce you to some basic terms around design systems:</p><ul><li>Pattern Library is a set of reusable components and interactions. It is a repository of buttons, modals, and page layouts. A pattern library relies on a consistent form and look. That’s why it is strongly connected to the second part of a design system — the style guide.</li><li>Style guide focuses mainly on style (thank you Captain Obvious!), which means that they’re a repository of colors, fonts, logos, and any other brand attributes used in product design. Style guides and pattern libraries are frequently used by designers and marketing specialists.</li><li>Code snippet is a resource used by coders (Captain Obvious strikes again!). It’s essentially a chunk of code representing styles and patterns included in the previous two repositories.</li></ul><p>Pattern library, style guide, code snippet — this Holy Trinity of product design makes up a design system.</p><p>The main difference between a style guide and design system is the scalability and dynamism of the latter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SEVYpQ_qpF-gsHMX.png" /></figure><p>While style guides are static and closed, design systems are dynamic and expandable. As opposed to handing off a style guide at certain point in time, in design systems the collaboration between designers and developers is ongoing. It bring us down to the simple conclusion: <strong>design systems support agile methodology</strong>, whereas style guides seem to make for a better match with the waterfall approach. In consequence, it allows companies to <strong>save a lot of time and money.</strong></p><h3>Why user experience is so important?</h3><p>It’s obvious that our world is getting more digitized. We’re using apps for everything. You may even be reading this on your phone, using your favourite browser.</p><p>It’s your favourite browser because it is logical to use. You don’t need to read a manual to learn how to use it.</p><p>So, in this digital world, the success of your app or software relies heavily on its design, its user interface, and the experience of the user.</p><p>Let me explain a little more.</p><p>Many businesses are familiar with the correlation between success and design.</p><p>If a user has to be shown, explained to, or taught how to do something, there’s a problem with the design.</p><p>Good user experience is rooted in good design — and when a user has a good experience, important metrics (like loyalty, retention, time in app, and conversion rates) go through the roof.</p><p>It doesn’t take a genius to know that these metrics are the be-all and end-all of a digital product.</p><p>So the next question is the most obvious — how can my digital product be designed in the best way possible?</p><p>Let’s look at some examples of success stories.</p><h3>The current state in the industry</h3><p>The biggest players on the market, like <strong>Atlassian, Dropbox, AirBnb, Shopify, </strong>and <strong>Audi</strong>, just to name a few, are investing in design systems. It isn’t another buzzword that will come and go. It’s more like a revolutionary approach to design, putting design &amp; development at heart. The firms mentioned above are big, but is a particular size required to start thinking about creating a design system? Having one is valuable r <strong>egardless of the company’s size. </strong>It just comes more inevitably to those who have wider array of digital products.</p><p>From the <a href="https://www.slideshare.net/johnmaeda/design-in-tech-report-2017">design in tech report</a> we can learn that 5 out of 10 companies from the top 10 companies by market cap are either exclusively growing by producing software, or software is an important part of their revenue stream.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/468/0*0hRNgQRUQJQmPPCc.png" /></figure><p><em>Source: </em><a href="https://www.uxpin.com/enterprise-ux-design-2017-2018-industry-report"><em>UXPin</em></a></p><p>In the past 12 months, these companies <strong>increased their design headcount</strong> by an average of <strong>65%</strong>. Moreover,<strong> designer to developer ratio improved by 2.5x in 5 years</strong>. The demand for designers has never been bigger. However, with the new scale, new problems arise. New methods had to be developed to bridge the gap between design and <a href="https://www.netguru.com/services/custom-software-development">custom software development</a>. Such a demanding industry requires appropriate tools to keep up the pace with the competition.</p><p><strong>Sources</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/0*iV1MscAzM_5pwEuL.png" /></figure><h3>Design systems in action — examples</h3><p>So now we that know the what and why, let’s take a look at the who and the how.</p><p>As mentioned, many digital companies are seeing the benefits of using a design system.</p><p>Who are the pioneers in this field?</p><h3>Shopify</h3><p>Shopify is a company that creates a product that their customers spend all day using. One look at <a href="https://polaris.shopify.com/">their ‘Polaris’ design system</a> and you can see the ecommerce platform is no stranger to the importance of good design.</p><p>Below, you can see in simple terms, the dos and don’ts of the text/colour relationship.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/844/0*DWYKAz656mobpFJ-.png" /></figure><p>The art of starting an online store is not a single task — more like a series of repetitive tasks that need to constantly be improved as your business grows.</p><p>Polaris has been designed with this in mind — not only to make the product as fatigue-free as possible, but also to make it consistent over all touch points.</p><p>A built-in onboarding procedure leads the user to their ‘ah-ha’ moment, thus adding even more value to the user.</p><p>In this, Shopify drive their growth through their design system.</p><h3>Atlassian</h3><p>Atlassian is a company who has <a href="https://atlassian.design/">a design system that we truly admire</a>.</p><p>Comprehensive, advanced, and constantly evolving, it’s something all design systems should aspire to be.</p><p>One look at the landing page and you’ll see why we’re in love with it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/0*g8XzjRjoIHh2s0ly.png" /></figure><p>It has resources for branding, marketing, colour usage — if a designer needs a logo, it’s there, as well as the way that the logo can be modified.</p><p>As a company that has a wide array of digital products spanning different industries, this design systems ensures consistency and simplicity for designers, developers, marketers, and anyone else involved.</p><h3>IBM</h3><p>Of all the companies mentioned in this article, IBM are the oldest.</p><p>And with age, comes wisdom.</p><p>Recently, the company ‘needed to build out the entire foundation for the way IBM would practice design’.</p><p>And they did that by building the <a href="https://www.ibm.com/design/language/">IBM design language</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/707/0*PJkL9eEzSS7-1ubx.png" /></figure><p>This is just a snapshot of the wealth of resources the IBM have created for their design team.</p><p>The benefits? Joni Saylor, the IBM design lead says ‘we could see these aren’t just updated UIs,’” Saylor says. “The concept, fundamentally, was and is striking a chord with our clients and users.</p><p>A few years later, and IBM’s design team swears by their design system, with ripple effects coming in in marketing and sales.</p><p>IBM’s design system is one of the most in-depth and comprehensive on this list. It’s rivalled only by Google’s design system, <a href="https://material.io/">Material Design</a>.</p><h3>Spotify</h3><p>Spotify, a completely digital product, knows the importance of a design system. As a piece of software that’s used by the same person over multiple devices, the design had to be not only easy, but also consistent.</p><p>And a few years ago, that’s exactly what was lacking</p><p>When design lead Stanley Wood took the helm in 2012, he was ‘shocked at the lack of consistency in elements across Spotify’s product’.</p><p>Over the next 12 months, steps were taken to create Spotify’s design system, G.L.U.E (Global Language for a Unified Experience).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*0UXJML89hYUaq1pu.png" /></figure><p><a href="https://www.invisionapp.com/blog/scale-design-systems/">Source</a></p><p>So how has Glue changed the way Spotify does design?</p><p>“Instead of 2 designers looking at the same thing and unintentionally creating totally different solutions, design systems provide a shared platform to create, collaborate, and build a deliberate outcome.”</p><p>Spotify is revolutionary just in its concept. Ensuring that design nurture and compliment this concept is a testament to the brand’s ongoing success.</p><h3>Airbnb</h3><p>Anyone that’s used Airbnb to book a holiday is no stranger to how easy it is to use and how visually appealing it is.</p><p><a href="https://airbnb.design/building-a-visual-language/">The product’s design system</a> works hand in hand with simple product design in order to take the chaos out of booking somewhere to stay.</p><p>Below, you can see an example of the clear and concise templates that Airbnb use in the desktop version.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t-_wP3oOXhzNjHfe.png" /></figure><p>Airbnb’s design system is extensive. Below, you can see their restraints for type sizes, colour usage and spacing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*I1rG_r7auKjTjeNW.png" /></figure><p>Airbnb have a world-class design system, and one can’t help but feel that it’s part of their HR department’s plan.</p><p>By sharing their assets with the general public, and sharing the story of how it came to be, they’re showing skilled talent that this is a place where your skill will be put to good use.</p><p>A great design system, and perhaps a great recruitment device!</p><h3>Why design systems mean success</h3><p>Asking <em>what </em>a role a design system plays is important, but the value of a design system is truly seen when you ask <em>why.</em></p><p>According to the<a href="https://www.uxpin.com/enterprise-ux-design-2017-2018-industry-report"> enterprise UX industry report</a>, one of the greatest challenges is <strong>lack of design consistency</strong> which leads to <strong>expensive design debt</strong>.</p><p>From the same report, we also learn that collaboration becomes more difficult as developers outnumber designers. It probably sounds familiar to you if your company has not developed a proper solution yet. A well-crafted design system serves as single source of truth and provides the following types of <strong>business value</strong>:</p><h3>1 — Consistency across products</h3><p>Want your brand logos to be echoed through into the default user avatars of your app? Your design system will take care of that. It will outline the process that a designer should take when designing something, and the standards to which he or she must work. The end result is your user having a smooth and consistent experience through all parts of your product</p><h3>2 — Clear guidelines</h3><p>Regardless of the role in the company, a documentation enables comprehension for everyone. If you have ever wondered how to get product managers, designers and engineers on the same page, now you know the secret.</p><h3>3 — Design systems create a good working environment</h3><p>Using a design system means that if your wonderful designer’s creative mind to goes off into some magic world and forgets the relevant font size, he or she will know how to find it. Your designers won’t be lost. They have an up-to-date play book to refer to if something isn’t clear. This in turn increases productivity and the happiness of your designer’s creative mind.</p><h3>4 — More efficient production process</h3><p>Similar to our first point here. Whether your design team is you, one other person, or a team of 45, ensuring that they’re all on the same page is going to make the process much smoother. It not only helps prevent errors, but shows what to do in the event of an error — be it minor or colossal.</p><p>Long story short: Make your design system proactive to avoid a problem, rather than reactive, in order to fix one.</p><h3>Who can build a design system</h3><p>Now let’s focus on 3 primary roles that are present while shipping a digital product.</p><p>We have product managers, designers and developers. Each of them have different requirements and expectations. Let’s take a closer look from three different perspectives.</p><p><em>Finished product is a contribution of entire team</em></p><p>For a <strong>product manager,</strong> the most important thing is to deliver a working product with all the features that the customers want. They hate moving slowly, so the less time is spent on design and development, the better and healthier for the business.</p><p>From a <strong>designer</strong> standpoint, the wish list starts from having consistent designs by keeping track of the changes when more than one designer works on the same project. Being able to make some adjustments quickly isn’t less important, though. On the other hand, they hate seeing their designs disrupted by neglectful development. Even small things matter, because the difference between an excellent and a very good product lies in the details. As the product team gets bigger, the contributions generate inconsistencies. Centralized design version control might be a remedy.</p><p>Finally, <strong>the developers</strong> expect to get thoroughly documented designs, ideally with no further changes. They don’t want to guess what the designer’s intention was. They hate moving pixels back and forth. They want to work with mockups smoothly. However, often times it’s more like a struggle than a pleasant process.</p><p>Does it sound familiar to you? There’s no silver bullet for every problem a product team faces, though. However, based on our experiences, knowledge and our customers’ successes, having a design system is worth the initial investment. A design system is supposed to address those pains and reduce the friction in the process.</p><p>Think about your product and company for a while with the following questions in mind:</p><ul><li>Do you agree that your product’s user interface is consistent: it shares the same design basics and patterns?</li><li>Are you happy with the overall pace of your product’s development?</li><li>How much time and money could you save by cutting down the time needed for design and development?</li><li>How much time and money could you save by reducing the time needed for cleaning up design and technical debt?</li></ul><p>Having doubts? Let’s talk about your case!</p><h3>How to create design system?</h3><p>It takes only 5 steps to get started:</p><ol><li><strong>Do an audit</strong> — check all the designs that you’ve made so far and try to extract basic repetitive elements.</li><li><strong>Organize the elements that you’ve extracted</strong> — build all three repositories I’ve mentioned earlier and create subcategories in every repository to make everything searchable and easy to use.</li><li><strong>Put all of the elements in one place, easy to access for everybody engaged in the product design process</strong> — every designer, coder, and marketing specialist involved in the process needs to have equal access to all parts of the design system simply to work effectively.</li><li><strong>Sell the design system to everybody in the organization</strong> — internal communication is vital to making good use of the system. If nobody knows about it and how to use it they simply won’t.</li><li><strong>Always update your repositories</strong> — evaluate your stash every once in a while and make sure that if any new elements appear they are included in your repositories</li></ol><h3>So why you need a design system?</h3><p>By now, you should have a good idea of what a design system is and how it can be of benefit to your business:</p><ul><li>A single-source of truth for designers and devs, enabling more <strong>control over multiple versions</strong> and <strong>scaling design,</strong></li><li>A well-planned design system help <strong>solve common problems</strong> that designers face your product team will be able to<strong> jump into a new project more easily,</strong></li><li>Your design system will work toward <strong>creating the best possible user experience.</strong></li></ul><p>Furthermore, seeing how some of the biggest digital brands leverage their design system should have you feeling motivated and inspired to create your own.</p><p>Whether you’re a seasoned vet and designed a few design systems in your time, or you’re fresh to the idea, it’s worth noting that there’s no such thing as a bullet proof design system.</p><p>As many digital products constantly grow and change, so should your branding, message, and ultimately your design system.</p><p>What’s the best way to get started building your design system, though?</p><p>Well before creating, it’s worth taking stock of your current position. <a href="http://bradfrost.com/blog/post/interface-inventory/">Conducting a UI/UX audit</a> can show you what’s working and what’s not.</p><p>This ensures that any major inconsistencies in your current processes are revealed, and you’re able to continue using what’s working.</p><p>What are some of the best design systems you’ve seen? Any tips for creating and developing one yourself?</p><p><em>Originally published at </em><a href="https://www.netguru.com/blog/design-systems-what-how-and-why-your-digital-product-needs-one"><em>https://www.netguru.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e37d52dd36c7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/netguru/design-systems-what-how-and-why-your-digital-product-needs-one-e37d52dd36c7">Design Systems. What, How, and Why Your Digital Product Needs One</a> was originally published in <a href="https://medium.com/netguru">Netguru</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a Design System: Our Approach and Experiences]]></title>
            <link>https://medium.com/netguru/creating-a-design-system-our-approach-and-experiences-d32bd56c3a8a?source=rss-d014b3a63cd5------2</link>
            <guid isPermaLink="false">https://medium.com/p/d32bd56c3a8a</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Adam Zielonko]]></dc:creator>
            <pubDate>Wed, 26 Jun 2019 07:26:46 GMT</pubDate>
            <atom:updated>2019-07-01T18:56:43.544Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zOuQxgxwdCYG_h1riXdyFw.jpeg" /><figcaption>Design Systems / Illustration: <a href="https://dribbble.com/aga-koniuszek">Agnieszka Koniuszek</a></figcaption></figure><p><a href="https://www.netguru.com/blog/design-systems-what-how-and-why-your-digital-product-needs-one">Creating a design system</a> is one of the services we offer at Netguru. So far, we’ve created design systems for either enterprise-size or smaller companies. Our approach and process are based on our experiences and the issues we’ve encountered so far. <a href="https://www.netguru.com/services/product-design">Design</a> systems have been quite a popular topic recently, and when it comes to their creation and development, no global standards have been established yet. This is why we want to show how we approach this subject.</p><p>In this blog post, we’d like to share some <strong>insights</strong> into creating design systems. You will learn how to start, how to build a design library assets, and how you should structure the documentation.</p><h3>It takes two (and more) to tango</h3><p>Setting up the right team is crucial. On the one hand, we need someone with <a href="https://www.netguru.com/blog/how-a-ux-designer-can-bring-profit-to-your-business">UX skills</a>; on the other hand, we also need a more UI-savvy designer. Obviously, we could find a unicorn with expertise in both fields, but she or he would quickly become a bottleneck as such projects are complex.</p><p>A design system consists of a few elements. The first is a design library, which is a repository of UI elements. The second piece is the documentation, which is linked to the design library. The documentation often contains some code snippets of design components, which makes a major difference compared to static style guides. We’ve covered the differences and showed the pros of having a design system in our previous blogpost.</p><p>To create a design system you need at least one designer and one developer, but, as we stated above, it might be inefficient. The task will take too much time and will be exhausting for the two. <strong>The more people you can involve in the creation of the design system, the better outcome you will get</strong>.</p><p>An optimally sized team, based on the projects we have done, should consist of five people. Breaking that number down, you need four product designers with different expertise (2x UI, 2x UX) and a developer. The ratio is four-to-one then. This number could be scaled up, so for more complex design systems, you can have eight designers (e.g. with illustration and motion proficiency) and two developers. An example of an advanced design system is <a href="https://atlassian.design/">the one Atlassian have</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/702/0*XBhNxag6Wf5KgLd2" /><figcaption><em>Atlassian Design System</em></figcaption></figure><p>They have covered every area of their products: colors, illustrations, components, to name a few. Having plenty of products in a portfolio like theirs requires some unified guidelines. We hope you now understand the <strong>business benefits of having a design system</strong>.</p><h3>Choosing the right team model</h3><p>A design library team should consist of specialists in areas such as user interface, <a href="https://www.netguru.com/services/illustrations-services">illustration</a>, and motion design. A documentation team should be made up of designers who have expertise in user experience, research, as well as from <a href="https://www.netguru.com/services/front-end-development">front-end developers</a> who excel at codifying design components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/0*ve_6jKhBleiVjVkX" /><figcaption>A possible structure of the design system team</figcaption></figure><p>During our trial and error period, we struggled because our design library was often broken due to synchronization issues. We would recommend choosing one person who will be responsible for updating the master library file (the library owner). In other words, one designer should aggregate all the approved design components from the rest of the team and merge them into the design library file. It allows the team to have better version control over the library. One person responsible for keeping everything in order will also reduce the information creep because the rest of the team will know that the repository has only one owner. The rest of the team should inform the library owner about their needs and issues regarding the component library.</p><p>We keep the master library file on Google Drive and have Sketch linked to that library. It works well now, but it didn’t work when more than one designer was allowed to make changes. <a href="https://medium.com/eightshapes-llc/team-models-for-scaling-a-design-system-2cf9d03be6a0">This team model is called </a>“solitary”.</p><h3>How to get started</h3><p>Once you’ve found the right team for the task, it’s time to kick the project off! As needs vary from company to company, we assume that you’ve already built at least one digital product. The first thing we recommend doing is <strong>listing all elements</strong> that need to be included in the design system. You can use post-it cards and a whiteboard or use a worksheet, as we do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/0*6Xe-LQ5Df0p2eXft" /><figcaption><em>An excerpt from the inventory</em></figcaption></figure><p>Then, you need to <strong>prioritize the items by usage</strong>. To facilitate this task at Netguru, we assign priority points from 0 (mandatory) to 3 (superfluous). You can also use <a href="http://eightshapes.com/images/documents/PickingParts-Products-People.pdf">the worksheet</a> from <a href="https://medium.com/eightshapes-llc/picking-parts-products-people-a06721e81742">Nathan Curtis’ article on medium</a>.</p><h3>How to prioritize the components</h3><p>When your app consists mainly of input fields because you collect some data from your users, input fields, in general, should get a high priority, and the issue should be discussed early on. If you think that input fields aren’t a good example of a topic that might deserve so much attention — you are wrong. Every component that interacts with the user should be thoroughly examined. For example, we can have password input fields (which require a multilevel validation), standard fields, text areas, PIN prompts, and so on. Each of them should get a detailed treatment in terms of visuals, behavior, usage, and anatomy. This is the only way to have the components consistent and to get a successful product as a result. The difference between good and great lies in the details.uns</p><p>Once you’ve created a list of the components and prioritized them, you can allocate the items to relevant sprints. Depending on the team’s size, an example roadmap could look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/0*ybdBqfwsDonyTo8B" /><figcaption>An exemplary roadmap</figcaption></figure><p>At the same time, another designer can start building up or simply collecting the product principles or visual language elements such as brand guidelines, colors, typography and grid.</p><p>Let’s take the grid for example. In our opinion, introducing the grid units at the beginning speeds up the design process later on. For example, while designing for mobile, it is <a href="https://builttoadapt.io/intro-to-the-8-point-grid-system-d2573cde8632">recommended that you lay out designs on an 8px grid.</a> As a result, we can assume that 1 grid unit (gu) = 8px. One of its benefits is spacing consistency and scalability across various device sizes. Let alone the rhythm, which comes along as an extra bonus for using the grid properly.</p><p>Ideally, another designer could simultaneously start establishing documentation templates for describing the elements. The template should include arrows, lines, rulers, numbers, captions, which are used later on for creating the documentation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/676/0*2GKntHParSACLEQX" /><figcaption><em>An excerpt from the documentation: anatomy of the components and layout</em></figcaption></figure><p>As the design system is getting bigger, it’s easy to fall into the trap of having inconsistent documentation. One of the main goals of having a design system is to reduce inconsistencies in the company’s digital products because an inconsistent design system is useless.</p><p>To avoid the inconsistencies, along with the documentation template, establish one standard process for uploading graphics and screenshots to the documentation. For example, all visual examples should be exported at @2x, have the same margins, and be properly named. Also remember to keep all assets in one place (we use Google Drive), in case someone new on the team needs access.</p><h3>Putting it all together</h3><p>As we initially stated, a design system is a combination of a pattern library and documentation. You should end up having a design library with all the components placed in the file. A pattern library is the final outcome of the work of the design library team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/775/0*hGjVC70JgKwN4gRM" /><figcaption><em>Shopify’s Design System — Polaris (Design Library in a Sketch file)</em></figcaption></figure><p>Once the components have been designed, the documentation team will be able to create the necessary descriptions and provide the anatomy of the components (e.g. margins, height, width). The structure depends on the end platform of the product(s). If a product is served for both desktop and mobile, then also some rules for breakpoints and viewports should be covered. An example table of contents for each component and pattern looks as follows:</p><p>Description<br>Specification<br>Anatomy<br> 1. Element name<br> 2. Element name<br>Behavior<br>Qualities<br>Measurements<br>Usage (worth having some animated examples)<br>Code snippets<br>Dos &amp; Don’ts</p><h3>Further maintenance</h3><p>For keeping track of our progress we use a <strong>kanban board,</strong> and we work in <strong>biweekly sprints</strong>. The rest is aligned with the Agile approach: we have status calls on a daily basis, where we inform each other what was done the previous day, what our plan for today is, and what the potential blockers are. Once every two weeks we conduct a thorough review, and we go through all the new and revised components, one by one. The entire team is present at these calls because everyone somehow contributes. The roadmap serves here as a guide. Some of the elements could have their second or even third iteration, because of new issues will arise during the development. That’s normal. A product design process is never finished. As design systems are living “beings”, they have no definition of “done”.</p><h3>Key takeaways</h3><ul><li>A Design System consists of two components: a design elements library and documentation.</li><li>Start by listing down all the elements that need to be included in the design system.</li><li>Prioritize the elements by usage and allocate items for the first sprint.</li><li>Start with the visual language: colors, typography, and grid.</li><li>Introduce grid units (for example while designing for mobile 8px = 1gu).</li><li>Create templates that will describe the elements (arrows, lines, rulers, numbers, captions).</li><li>Set up one standard process for uploading graphics and screenshots to the documentation.</li><li>Keep the source files of the graphics and screenshots from the documentation available to everyone.</li><li>Select one person who will be responsible for updating the master library file (a design library owner).</li><li>The rest of the team can contribute to the library, but they need to contact the library owner first.</li><li>The rest of the team should inform the library owner about their needs and issues regarding the components library.</li><li>Keep the master library file on Google Drive and link that library with Sketch.</li><li>Make backups and keep track of file versions.</li><li>Keep track of the progress by using a sheet, Jira, or another piece of tracking software.</li><li>Have daily meetings when you update each other on what was done the previous day, what is going to be done, and what the potential blockers are.</li><li>Create a structure for the documentation.</li><li>Keep a changelog of the master library.</li><li>Communicate with stakeholders often, keep everyone on the project in the loop.</li><li>Create a note on the Slack channel with all the important information and links (to the library, to the UIs, and so on).</li></ul><p>Design Systems are quite a challenging endeavor, which requires experienced people in order to deliver high quality and usable outputs. The goal is to have a library of reusable components, followed by clear standards so that designers and developers can build coherent digital products. Served as a single source of truth available to everyone in the company, a Design System allows employees to be on the same page and in the loop.</p><p><em>Originally published at </em><a href="https://www.netguru.com/blog/creating-a-design-system-our-approach-and-experiences"><em>www.netguru.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d32bd56c3a8a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/netguru/creating-a-design-system-our-approach-and-experiences-d32bd56c3a8a">Creating a Design System: Our Approach and Experiences</a> was originally published in <a href="https://medium.com/netguru">Netguru</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>