<?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[Sixt UX - Medium]]></title>
        <description><![CDATA[UX Design at SIXT - Medium]]></description>
        <link>https://medium.com/sixt-ux?source=rss----3bbe11a2fa83---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Sixt UX - Medium</title>
            <link>https://medium.com/sixt-ux?source=rss----3bbe11a2fa83---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:04:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/sixt-ux" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Building a Design System — Getting Started]]></title>
            <link>https://medium.com/sixt-ux/building-a-design-system-getting-started-8a5eb1bc7?source=rss----3bbe11a2fa83---4</link>
            <guid isPermaLink="false">https://medium.com/p/8a5eb1bc7</guid>
            <category><![CDATA[design-operations]]></category>
            <category><![CDATA[design-strategy]]></category>
            <category><![CDATA[design-methods]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Benedikt Kaemmerer]]></dc:creator>
            <pubDate>Sun, 30 Jun 2019 21:58:37 GMT</pubDate>
            <atom:updated>2023-09-27T14:21:58.747Z</atom:updated>
            <content:encoded><![CDATA[<h3>Building a Design System — Getting Started</h3><p>How did we get started with building our own design system? This article is part 1 and the start of a series of articles about the Sixt design system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LjUbO4quVwzERQVvVitQeQ.png" /></figure><h3>What is a design system, and why would you need one?</h3><blockquote><strong>“A design system is a set of interconnected patterns and <em>shared practices </em>coherently organized to achieve the purpose of digital products.”</strong><br> — <a href="http://craftui.com/"><em>Alla Kholmatova</em></a></blockquote><p>Actually, there are a lot of different definitions of what a design system really is. What most of them have in common is that they define it as a collection of styles and reusable components that are used to build a digital product.<br>A design system is supposed to speed up the whole design process, to connect different teams with each other, and in the end, to build a better product.</p><p>If you actually need a design system or if you can get away without one depends on a lot of factors. In general, it makes more sense the bigger your organization and the number of people that use the design system gets.<br>With growing team size, it gets harder to collaborate and to build consistent and easy to use experiences for the users. But with a design system, your designers can focus on solving more significant problems than designing a button over and over again, and your developers are empowered to build a more consistent UI across different pages and apps.</p><h4>Design system vs. style guide</h4><p>A style guide is a subclass of a design system that contains the documentation of the design system and its various components, patterns, and rules. It is more static and, if you compare a design system to a set of lego, more like the manual instead of the actual bricks: you can not build the set without the manual, but you also can not make use of the manual without access to the Lego blocks.</p><h4>Want to know more about design systems?</h4><p>As the general topic has already been covered a lot, I want to transition to actually telling our story and how we solved our very own problems at Sixt.<br>If you want to learn more, here are some useful resources:</p><ul><li><a href="https://www.invisionapp.com/inside-design/guide-to-design-systems/"><strong>“A comprehensive guide to design systems”</strong></a> by Will Fanguy</li><li><a href="https://www.smashingmagazine.com/design-systems-book/"><strong>“Design Systems”</strong></a> by Alla Kholmatova</li><li><a href="https://www.designbetter.co/design-systems-handbook"><strong>“Design Systems Handbook”</strong></a> by Marco Suarez, Jina Anne, Katie Sylor-Miller, Diana Mounter, and Roy Stanfield</li><li><a href="https://uxdesign.cc/what-the-heck-is-a-design-system-c89a8ea73b0d"><strong>“What the heck is a design system?”</strong></a> by Inès Serizer</li></ul><h3>Why is the Sixt UX team building a design system?</h3><p>We maintained an essential style guide, and a sketch library with some crucial components that documented our current design for quite some while and that was fine as long as the team was rather small and only one product, Sixt rent, was supported.</p><p>With a growing team and our big product launch, the <a href="https://www.gruenderszene.de/automotive-mobility/sixt-carsharing-interview-gabriel">Sixt Big Bang</a>, where we launched two new products, share and ride, we encountered more and more problems with consistency across different products and platforms. In some parts, our design was, while still sticking close to our corporate identity, more random than well-organized.<br>We knew that we had to change something to be able to maintain the fast growth of our products and still be able to create an excellent user experience. After a team decision and collecting feedback from all members, we started with a small group of two designers to create a concept for a new design system.</p><h3>Start creating</h3><p>Since we were a small team of two and also had several other responsibilities, we could not start from scratch. Luckily we already had our beloved corporate identity and a set of design components that were in use, and we could easily base our new system on the parts that were already proven to work. <br>With a few points that roughly outlined our mission, we started to create our new design system:</p><ul><li>Make our customers lives easier by providing them with a outstanding and consistent experience across all Sixt products</li><li>Enable designers to solve problems and to build better designs faster</li><li>Increase collaboration between teams by utilizing a common foundation</li><li>Empower developers to build better apps with less code</li></ul><p>We knew about the challenges that we might encounter and that a had a lot of work in front of us, bet we were eager to get started and wanted to make a change for our customers because we know that good is not good enough if better is expected.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a5eb1bc7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sixt-ux/building-a-design-system-getting-started-8a5eb1bc7">Building a Design System — Getting Started</a> was originally published in <a href="https://medium.com/sixt-ux">Sixt UX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>