<?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 Gustavo Meyer Silva on Medium]]></title>
        <description><![CDATA[Stories by Gustavo Meyer Silva on Medium]]></description>
        <link>https://medium.com/@gustavomeyer?source=rss-e8a6ff83e319------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*u1qDH-xawXxGz14_gLcnWw.jpeg</url>
            <title>Stories by Gustavo Meyer Silva on Medium</title>
            <link>https://medium.com/@gustavomeyer?source=rss-e8a6ff83e319------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:52:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gustavomeyer/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[The one true path to freedom: rules]]></title>
            <link>https://uxdesign.cc/the-path-to-freedom-f1a08249ac23?source=rss-e8a6ff83e319------2</link>
            <guid isPermaLink="false">https://medium.com/p/f1a08249ac23</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-management]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Gustavo Meyer Silva]]></dc:creator>
            <pubDate>Tue, 19 Jun 2018 09:27:17 GMT</pubDate>
            <atom:updated>2018-06-21T23:56:23.148Z</atom:updated>
            <content:encoded><![CDATA[<h4>My thoughts on how to start building a design system</h4><p>2017 was the year of design systems and it is still a pretty hot topic in the world of design in 2018. If you are not working with a DS, you are most likely trying to prove to your management why it is worth all the time and effort to have one.</p><p>The common problem is that you may not work in a design-driven company. Don&#39;t worry, most of us don&#39;t. Talk to a few designers and you will quickly find out you are not alone. That&#39;s what inspired me to write this article — maybe you can find some shortcuts in your journey.</p><p>A design system should help the company build a united and coherent language. But as much well intended as you might be, it could also sound that by creating a system you will be killing creativity.</p><p>I’m sure you think you are worth trusting. Yeah! We all do! But proving a point about a project that will impact everyone’s work is a whole new thing; it usually takes more than one’s opinion to make a point.</p><p>I tried a few obvious arguments before I decided to dive deeper in:</p><p><strong>Obvious Argument 1 — history<br></strong>It may sound like a good start. If you also read <a href="http://designsystemsbook.com/"><em>Design Systems, by Alla Kholmatova</em></a><em>,</em> you know that one of the earliest examples of system documentation is <a href="https://en.wikipedia.org/wiki/Andrea_Palladio">Palladio</a>’s <em>The Four books of Architecture</em>, first published in 1570. But, before you are finished with an historical explanation everybody will be already checking their smartphones, trust me.</p><p><strong>Obvious Argument 2 — Everybody is doing it<br></strong>Most big companies have a design system these days. Not only <a href="https://material.io/design/">Google</a>, <a href="http://www.carbondesignsystem.com/">IBM</a>, <a href="https://polaris.shopify.com/">Shopify</a> and AirBnb but a <a href="https://github.com/alexpate/awesome-design-systems">bunch of other</a> digital product companies too. The problem is: when you start explaining how their teams work, you may find out it does not fit your design team&#39;s size or process. Process is a keyword because process is behaviour.</p><h3>Proving the value of a DS is not about finding the right argument, but finding the right behaviour.</h3><p>Before you start the creation of the perfect polished design system, you should start just like any other project you do: <strong>think about all of your company&#39;s designers as users.</strong></p><h3>Diana is broccolini on Twitter</h3><p>Today I gave a talk about how we shouldn&#39;t compare our design systems to those polished huge design systems of companies with big teams. It&#39;s like comparing your real life to someone else&#39;s Instagram life-the best curated version.</p><p>A good Design System should reflect the needs of its design team, which is exactly the opposite of creating a document with the same amount of sections of the Material Design system.</p><p>Building a design system is about giving freedom to designers, so they don’t have to worry about basic tasks that hold them from achieving their main goal. It empowers the team to bring strategic value to the company with innovation and creativity.</p><p>But how to explain it in a tangible way?</p><h3>Rules are the path to freedom.</h3><p>Saying that rules are the basic concept to live as a society should be more than enough to prove this point, but I found a much more attractive way to explain it.</p><p><a href="https://en.wikipedia.org/wiki/Benny_Greb">Benny Grab</a> is a german drummer known for the development of a system called the language of drumming, in which he explains how you could play basically anything by combining 24 rudiments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/1*bZNOGkRgshWNBGokmIOuqA.jpeg" /><figcaption><a href="https://www.youtube.com/watch?v=wsidXNUHMFY">The Language of Drumming DVD scen</a>e • Where Benny Grab explains the 24 rudiments.</figcaption></figure><p>When I first saw this DVD, it blew my mind. It was amazing to watch how the combination of some of those patterns could sound so complex and bring so much emotion and beauty when <a href="https://www.youtube.com/watch?v=DDIGrvG6lL8">played</a> with perfection.</p><p><strong>As designers, aren’t we all trying to achieve that?</strong> Don’t we work day-by-day bringing together a set of patterns, with the intent to drive the user through a mix of emotional and rational decisions that, in the end, will provide a pleasant and unique experience (and, thus, profit to our companies 😁)?</p><h3>Conclusion</h3><p><strong>Don&#39;t try to convince people that you should stop designing to work on documentation.</strong> Instead, work alongside your teammates to solve the pain points in their process. To do so, you will naturally need to generate patterns and assets and, as a result, a good and polished product. The value of your initiative will be noticed and, hopefully, you will get more time to invest in a complete design system.</p><p>If you&#39;re not able to get more time, well, follow these tips and I’m sure your team will be even nicer and more collaborative! 😄</p><p><strong>Here are some practical tips to help you start your design system MVP:</strong></p><ol><li><strong>Find out </strong>what are the <strong>designers&#39; main pain points </strong>on their creative process.</li><li>Throughout the discovery process, pay attention not only to assets such as fonts, colors and icons, but also to <strong>what kind of tools and software your company&#39;s designers use</strong>. It will help you decide how to share assets in a practical way.</li><li>Based on your discovery of pain points, start defining each section of your companies&#39; DS. Always keep your user in mind.</li><li>The documentation should always be evolving, but defining some deadlines and boundaries will help you to keep track of your evolution.</li><li><strong>Build together. </strong>Involving people in the process is the best way to make sure your company&#39;s design system is providing the right solutions for your team.</li></ol><p>Before I forget, if you didn’t read Design Systems, by Alla Kholmatova, you definitely should do it. It’s a great book.</p><p>I hope you may find this article useful. <strong>Please, clap if you do.👏👏👏</strong> 😄</p><p>Special thanks to <a href="https://medium.com/u/a537cd8e9f77">pablo</a> and <a href="https://medium.com/u/b2ee32447296">Julia</a> who, besides being a great team to work with, helped me finish this article.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1a08249ac23" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-path-to-freedom-f1a08249ac23">The one true path to freedom: rules</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>