<?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 Ariel Hernández Domenech on Medium]]></title>
        <description><![CDATA[Stories by Ariel Hernández Domenech on Medium]]></description>
        <link>https://medium.com/@ahdweb?source=rss-a6a3079b6c03------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*mRLxNZLnaSLKyjMkl72__Q.jpeg</url>
            <title>Stories by Ariel Hernández Domenech on Medium</title>
            <link>https://medium.com/@ahdweb?source=rss-a6a3079b6c03------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 05:22:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ahdweb/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[Starting a Design System]]></title>
            <link>https://medium.com/@ahdweb/starting-a-design-system-6ea897000477?source=rss-a6a3079b6c03------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ea897000477</guid>
            <category><![CDATA[sketch]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[design-operations]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Ariel Hernández Domenech]]></dc:creator>
            <pubDate>Thu, 30 Apr 2020 18:29:52 GMT</pubDate>
            <atom:updated>2020-05-12T02:17:32.536Z</atom:updated>
            <content:encoded><![CDATA[<h4>A practical guide to help build your own.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B4q2tnln_XPkT61OaPP7OQ.png" /><figcaption>Background Photo by <a href="https://unsplash.com/@ruvimnogaphoto?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Ruvim Noga</a> on <a href="https://unsplash.com/s/photos/abstract-background?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I am assuming that your organization decided to start a Design System, and you are either curious about, or you will be part of the team, or you are leading the effort. The chances are that you are not sure where to start and want to figure out what are the things you may want to take into consideration.</p><p>For over the last three years, I’ve acted as a leader in two Design Systems teams that supported a total of five different brands. This article is a handy collection of considerations, based on my experience, that I take when putting together a Systems team.</p><p>This list may not fit exactly your needs since every product, and team configurations are different. I hope this article helps you take the very first steps and sparks conversations we can follow up on public forums.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*SVYvDnIGuDm61Fd_XCLCwg.png" /></figure><p>For those who have worked with me, this article is a condensed version of the whiteboards sessions I asked you to attend during your onboarding. It was my goal to explain what we wanted to build. Taking into consideration the amount of information I was outputting, now I feel very sorry for those who went through that 😅.</p><h4>😬 What are Design Systems?</h4><p>A Design Systems is a group of <em>resources</em> and <em>documentation</em> that help you design and build a specific product. Think about design guidelines, UI Kits, and code repositories of reusable components altogether.</p><p>The team in charge will create a <strong>scalable architecture</strong> around the product in question. The team goal is to minimize production debt 💸 in the foreseen future by preparing artifacts that support this goal. They will act as a Product team inside of the organization with its tasks, timeline, and goals.</p><blockquote>A collection of guidelines, principles and assets that are relevant to a business. The purpose of this design system is to help the businesses team to learn, build and grow.</blockquote><blockquote>— <a href="https://medium.com/u/7942afe3d7d3">Gary Simon</a></blockquote><h3>Team roles</h3><p>The success of a System team relies on a healthy Engineering-Design relationship. As a designer, you are no longer “handing-off” your designs and waiting for them to come alive after an Engineer work on it. As an Engineer, you are no longer working in a silo, applying styles you get from a Sketch file or <a href="https://zeplin.io/">Zeplin</a>.</p><p>A System workflow promotes continuous communication, revisions, and validation until the product looks and behaves the way intended. Designers understand code and how apps are developed, and Engineers have an understanding of UX, and how asset optimization may improve the experience of the user.</p><p>People willing to learn multiple disciplines, teach others, and commit to product quality fits well on a System cross-functional team. Here it is the <a href="https://www.invisionapp.com/inside-design/designers-generalists-or-specialists/">example from Envato</a> where they tend to hire “generalist” for that purpose.</p><p>Let me breakdown the essential roles in a Systems team:</p><p><strong>Leadership </strong>— Provides the vision, define workflows, and make sure that everyone involved is making progress towards the primary goal.</p><p><strong>Design</strong> — Designers will help support three different angles:</p><ul><li>Define/Maintain the overall Visual Language of the product</li><li>Build a UI Kit or Library</li><li>Prepare documentation about perceptual and behavioral patterns at a component and pattern level</li></ul><p><strong>Front End Engineering</strong> — This is the person or team in charge of making tangible all the design decisions in an interactive product through code. But also, they must take into consideration:</p><ul><li>Define and document the criteria to build shared components in the System — must seek for minimum code quality, based on the tech stack available</li><li>Build a shared component library, with implemented Design Tokens (more on this below)</li></ul><p><strong>QA</strong> — The process in which the members of the Systems validates that everything built that meets the standard defined. This can be a person or a team or at least a phase in your workflow.</p><p>I’ve worked with teams where the quality process is logged in JIRA tickets, consumed, and validated by the QA team. In part, that is okay because the organization needs to log and measure those efforts. But in reality, quality must be part of the company’s DNA. Do not rely on QA team processes only to achieve it. It is time to <strong>embed quality in your company’s culture</strong>. Gather Engineers and Designers of your team, review the work together increase quality at all times.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*odZE646RVN3Yz0BAeRmnjg.png" /></figure><h3>Documentation</h3><p>Documentation comes in different flavors and formats. Some of them are very detailed, and they exist in article-like formats, while others exist as notes inside Sketch files or paper, and video format like my boss <a href="https://medium.com/u/8e17b22a164a">Alberto Orsini</a> will ask.</p><p>The main goal is to articulate the product you are building, and the components that support the user flows for the specific product you are shaping up.</p><p>In large teams, each designer that is coming with a new pattern, solution, or decision must document it and donates it to the system for the benefit of others.</p><p>Documentation must cover Design and Engineering, and they may overlap sometimes. While Design focuses on the <em>what</em>, <em>why,</em> and for <em>who</em> we are building, the Engineering documentation will specify <em>how</em> we are building it.</p><p>Let’s dive in on Design Documentation, starting with two categories <em>Foundations</em> and <em>Components &amp; Patterns.</em></p><p>💡 When you group and rearrange foundational units, you start building <em>components,</em> like cards, buttons, navigation bars, or input fields. When you group and arrange components to help your users get through specific flows, you start building <em>patterns</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*568W650i-wGvhShMGZn7AA.png" /></figure><h4>Design Foundation</h4><p>Design Foundation lists the base of your design. Starting with applicable principles and the units that the Systems have in place to build the perceptual aspect of your product. When you combine and rearrange them, a Designer can build components with confidence, making sure it is connected to the rest of your product. Let me just list a few of them:</p><ul><li>Design Principles</li><li>Accessibility</li><li>Typography</li><li>Colors</li><li>Iconography</li><li>Spacing</li><li>Shadows</li><li>Sound</li><li>Haptic</li><li>Voice &amp; Tone</li></ul><p>This list can be larger or shorter, depending on the product you need to create.</p><h4>Components &amp; Patterns</h4><p>This is where you tirelessly document the behavioral aspects of your product. As a designer, make sure to answer why you are designing pagination, for example, and how it should behave. You may include Do’s and Don’ts since it will help others in your team on how to reuse that pattern or component into their designs.</p><p>In the best-case scenario, your patterns are designed with enough data (testings and analytics) that supports your decisions. Include those references in the documentation too.</p><p>Here it is a list of common Components &amp; Patterns you can document.</p><ul><li>Alerts</li><li>Buttons</li><li>Cards</li><li>Confirmation flows</li><li>Forms &amp; Input</li><li>Modals</li><li>Navs</li><li>Popovers</li><li>Progress</li><li>Sign In &amp; Log In</li><li>Tooltips</li><li>User Onboarding or Feature Tours</li></ul><p>Just to name a few…</p><p>In the past, I’ve collected and published Systems documentation in Confluence Pages, Sketch files, and Google Drive documents. Other tools help you centralize and share this information like <a href="https://www.invisionapp.com/design-system-manager">inVision DSM</a>, <a href="https://zeroheight.com/">Zeroheight</a>, and <a href="https://www.modulz.app/">Modulz</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VC_hvuk-TNFj1nv78JmBAA.png" /></figure><h3>UI Kit</h3><p>Take advantage of tools like Sketch, Adobe Xd, and Framer that allows you to group your designed components in a single location, share with others, and reuse them through your designs. So far, you’ve spent so much time making decisions on the foundational elements of your product that a tool should automate the distribution and maintenance of reusable components for your team.</p><p>A UI kit contains an assortment of UI components, type styles, colors, and icons for user interface design. Building a Library helps designers to create more visuals in a shorter time while keeping the same aesthetic and quality through the product.</p><p>My preferred tool is Sketch for multiple reasons. First, they have <a href="https://www.sketch.com/docs/libraries/">lots of documentation</a> and community support. Second, the <a href="https://developer.sketch.com/reference/api/">Sketch API</a> makes it viable to create plugins and transform Sketch files into other formats. Third, this is the tool I feel I am better at since I work faster and confident every time.</p><h3>Design Tokens</h3><p>It is time to make that revamped connection with the Engineering team. After you’ve spent time defining the Foundation, it is best to handoff those design decisions in a way that Engineers can <em>consume</em> it while Designers can <em>own</em> it.</p><p>Design Tokens are bits of information that can be stored in a text document, distributed, and consumed by different platforms. Think about having a single document with all the styles you’ve designed that impact the theme on every product in your organization, no matter if it is a native or web project.</p><p>List all the colors hex values, spacing rules, shadow properties, typestyle, and other properties in a single JSON file. <a href="https://amzn.github.io/style-dictionary/">Translate those values into any format</a> like Swift, Sass, or XML.</p><p>After properly implemented, you can modify the theming properties of different products and platforms from a single JSON file, neat!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w6hgxoCfL6zO77BASkGDCg.png" /></figure><h3>Components Repository</h3><p>The culmination point in your product development. So far, we’ve gone through design, documentation, and hand-off. It is time to build the designed components and store them in a place where we can update them and reuse them multiple times.</p><p>A Components Repository will host isolated components where team members can share, maintain, and synchronize them. Think about it like the UI Kit we mentioned before, but build in code that lives in a repository where you can fetch and reuse it over and over.</p><p>Your team can benefit from increasing the usage of reusable code, design-engineering efficiency, deliver consistent UI and UX, and improve the project’s stability. Some tools out there will help you achieve a Component Library for multiple platforms like <a href="https://storybook.js.org/">Storybook</a>, <a href="https://github.com/teambit/bit">Bit</a>, and <a href="https://github.com/styleguidist/react-styleguidist">React Styleguidist</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j7u57M4JI3WsHRg9jZkSuQ.jpeg" /><figcaption><a href="https://medium.com/u/948ea525b6c3">Rachelle Btesh</a> and me presenting a Design QA workflow.</figcaption></figure><h3>Education</h3><p>Promote that individuals gather with others to share knowledge. Prepare presentations on specific topics, and create an open forum for questions and discussions. In my experience, Designers will invite Engineers to discuss new pattern documentation after extensive audits. Others will prepare Show and Tell sessions to review workflows, and sometimes we will bring beers and wine to run workshops about new software or new techniques.</p><h3>TL;DR</h3><p>Far from what the name suggests, a Design System does not end at design. It requires several ingredients, requires participation, collaboration, communication, and problem-solving when it comes to building a scalable project.</p><p>In the beginning, the investment of time and resources seems very steep, and it is. But once the System and the rules have been laid down, it becomes easier and cost-effective to create, iterate, and evolve on top of it.</p><p>👋 Let’s connect! Reach out to me here on <a href="https://medium.com/@ahdweb"><strong>Medium</strong></a> or anywhere else, including <a href="https://twitter.com/arielhernandez"><strong>Twitter</strong></a> ~ <a href="https://www.linkedin.com/in/hernandezariel/"><strong>Linkedin</strong></a> ~ <a href="https://dribbble.com/ahernandez"><strong>Dribbble</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ea897000477" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>