<?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 Vivek Juyal on Medium]]></title>
        <description><![CDATA[Stories by Vivek Juyal on Medium]]></description>
        <link>https://medium.com/@vivekjuyal?source=rss-da1e70540796------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Fca3X7ueQddxWsyHNMytIA.jpeg</url>
            <title>Stories by Vivek Juyal on Medium</title>
            <link>https://medium.com/@vivekjuyal?source=rss-da1e70540796------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:19:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vivekjuyal/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[Do you really need a Design System?]]></title>
            <link>https://medium.com/@vivekjuyal/do-you-really-need-a-design-system-right-now-b9f3ad4eb057?source=rss-da1e70540796------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9f3ad4eb057</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design-leadership]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Vivek Juyal]]></dc:creator>
            <pubDate>Wed, 25 Jan 2023 21:08:48 GMT</pubDate>
            <atom:updated>2023-01-26T20:52:20.774Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>I recently got a chance to interact with the product &amp; design team of an early stage e-commerce <em>startup</em> who wanted to “up their game” by introducing a design system to their product eco-system. There are some great examples of powerful &amp; well document design systems like <a href="https://medium.com/u/be36e94a7e47">Google</a>’s <a href="https://medium.com/u/413d230e5fe2">Material Design</a>, <a href="https://medium.com/u/60a317bb70e4">Spotify</a>’s Encore, <a href="https://medium.com/u/5aa6b9976187">Atlassian</a> design system, to name a few. There is also enough justification as to the what, why and how a design system can add value in scaling with speed. However, in the rut of upping the game, we forget to ask one important question as to <strong>“When should we start to invest in building a design system?”</strong></blockquote><p>Design systems have become a staple in the digital product design process, with many companies turning to them to improve efficiency and consistency across their products. However, in this article, I’ll talk about <em>why </em><strong><em>not </em></strong><em>all digital products need a design system</em> and <em>when is the right time to invest in a design system.</em></p><p>Firstly, a digital product may not need a design system is its small scale. If a product has a limited number of pages or features, a design system may not be necessary. Instead, <strong>a simple style guide outlining basic design principles and guidelines may suffice.</strong> This allows for flexibility in design and can save resources that would otherwise be dedicated to maintaining a design system.</p><p>Secondly, a design system may not be necessary if the product’s lifespan is short-term. If a product is only expected to be in use for a limited time, the resources required to create and maintain a design system may not be worth the investment. In this case, it may be more beneficial to focus on creating a functional and user-friendly design that meets the needs of the project.</p><p>Additionally, a design system may not be the right fit for a product with a unique or experimental design. A design system is built on established design principles and conventions, and may not provide the freedom needed to explore new and experimental design ideas.</p><p>It’s also important to note that a design system is not a one-size-fits-all solution and every product is unique in its own way. Therefore, it’s advisable to evaluate the specific needs of the product and determine if a design system is the right fit.</p><p>So when should we think of building a design system?</p><h3><strong>Here is a my list of 5 fundamental questions to ask when deciding to invest in building a design system.</strong></h3><ol><li><strong>Is the product large and complex, with many different pages and features? </strong><em>If it is, a design system can help ensure consistency and efficiency across the product.</em></li><li><strong>Is the product expected to be in use for an extended period of time?</strong> <em>If so, a design system can help ensure that the product remains consistent and user-friendly over time.</em></li><li><strong>Is the team working on the product “large enough” or will it be growing either horizontally or vertically in the future?<em> </em></strong><em>If yes, a design system can help ensure that everyone is on the same page and working with the same design elements.</em></li><li><strong>Do you have the budget to invest in creating &amp; maintaining a design system?</strong> <em>If not, it </em><strong><em>may not be feasible</em></strong><em> to implement one.</em></li><li><strong>Is the product’s design experimental or unique?</strong> <em>If so, a design system </em><strong><em>may not be the best fit </em></strong><em>as it is built on established design principles and conventions.</em></li></ol><p>In conclusion, while a design system can be a valuable tool for improving consistency and efficiency in digital products, it comes with a cost, not just of building a design system but also of maintaining it. Factors such as scale, lifespan, and design approach should be considered before deciding to implement a design system. It’s important to evaluate the product’s needs and determine if a design system is the right fit for the project. Style guides if documented well can sometimes work really well for small to medium scale projects/products, especially in a would where we are blessed with amazing tools like <a href="https://medium.com/u/bf1152b11387">Figma</a>, <a href="https://medium.com/u/496b48c374df">Notion</a>, Confluence by <a href="https://medium.com/u/5aa6b9976187">Atlassian</a>, etc.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9f3ad4eb057" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>