<?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 Mariana Rita on Medium]]></title>
        <description><![CDATA[Stories by Mariana Rita on Medium]]></description>
        <link>https://medium.com/@marianarita?source=rss-92434e7b7aca------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qjyF-xzjcgLyTLAwB7J7Tw.png</url>
            <title>Stories by Mariana Rita on Medium</title>
            <link>https://medium.com/@marianarita?source=rss-92434e7b7aca------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:54:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@marianarita/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[Stop paying for design system documentation you can build yourself]]></title>
            <link>https://medium.com/all-about-design-systems/stop-paying-for-design-system-documentation-you-can-build-yourself-a10f1390987f?source=rss-92434e7b7aca------2</link>
            <guid isPermaLink="false">https://medium.com/p/a10f1390987f</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[zeroheight]]></category>
            <category><![CDATA[docusaurus]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[design-documentation]]></category>
            <dc:creator><![CDATA[Mariana Rita]]></dc:creator>
            <pubDate>Mon, 23 Feb 2026 12:44:13 GMT</pubDate>
            <atom:updated>2026-02-23T13:57:10.689Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vfClPFUPelgOOGJNHtDJng.png" /></figure><p><strong>TL;DR</strong></p><p>Paid DS documentation platforms cost $2k–$10k/yr, can’t handle multi-platform systems, and are invisible to AI agents.</p><p>This article is a practical guide to replacing them with free, open-source tools — where AI writes the docs from your Figma and code repos, designers edit through a visual interface, and the site auto-deploys.</p><p>Two weeks to set up. Real trade-offs included.</p><p>For a while, tools like <a href="https://zeroheight.com/">Zeroheight</a> and <a href="https://www.supernova.io/">Supernova</a> genuinely made our lives easier. If you didn’t want Figma to double as your documentation, didn’t want to rely on Markdown files, and didn’t want to push your designers into engineering-oriented tools like <a href="https://storybook.js.org/">Storybook</a> — these were the answer. You paste your Figma library link, pick which components you want to display, and you’ve got a decent-looking documentation site without writing a single line of code.</p><p>That was a big deal. But it doesn’t make sense anymore.</p><p>With the rise of <a href="https://modelcontextprotocol.io/">MCP servers</a>, AI agents, and solid open-source documentation tools, you can build something that’s more powerful, more flexible, and way cheaper. And I’m not talking about a hypothetical future — I’m talking about tools you can set up this week.</p><h3><strong>What changed</strong></h3><p>It’s become so easy to fetch data from Figma — using the <a href="https://www.figma.com/developers/api">Figma REST API</a>, Figma MCP, or the <a href="https://github.com/southleft/figma-console-mcp">Figma Console MCP</a> — that the main value proposition of tools like Zeroheight has evaporated. The “we pull your Figma components so you don’t have to” pitch made sense when doing that yourself was hard. It’s not hard anymore.</p><p>At the same time, LLMs have gotten good enough to act as technical writers. You can point an AI agent at your Figma library and your code repos, and it’ll generate accurate documentation pages — with real token values, real component APIs, real specs. Not hallucinated approximations. Actual data, extracted from the source.</p><p>So now you’re paying for a platform that does less than what you can do yourself with free tools.</p><h3><strong>What these platforms actually cost you</strong></h3><p>Let’s put numbers on it.</p><p><a href="https://zeroheight.com/pricing/">Zeroheight’s Starter plan</a> is $49/editor/month. A team of 5 editors runs you <strong>~$2,940/year</strong>. And Starter is limited — you get 2 styleguides, 3 token sets, no API access, no SSO, no adoption tracking. For the features most design system teams actually need, you’re looking at their Enterprise plan, which requires a sales call. Third-party estimates put the Pro tier at <strong>around $800/month</strong>, so roughly <strong>$9,600/year</strong>.</p><p><a href="https://www.supernova.io/pricing">Supernova’s Pro plan</a> charges $35/month per “Full seat” (yearly billing). Five seats is <strong>$2,100/year</strong>. Enterprise is custom pricing.</p><p>These aren’t outrageous numbers for large companies. But they’re not trivial, and they come with limitations that cost you more than money.</p><h3><strong>Where these tools are actually hurting you</strong></h3><p>The cost isn’t the real problem. The real problem is that these platforms were built for a world that doesn’t exist anymore — a world where one design system maps to one tech stack.</p><h4><strong>The multi-platform mess</strong></h4><p>Most of these tools assume 1 Figma component = 1 React component. That’s their mental model, and everything is optimised for it.</p><p>But if you’re like most growing teams, you actually have 1 Figma component = 1 React component + 1 SwiftUI component + 1 Jetpack Compose component. And suddenly you’re stuck finding sketchy workarounds:</p><ul><li>Manually managing component status per platform (which is a maintenance nightmare)</li><li>Embedding .md files or using iframe blocks to show platform-specific code</li><li>Self-hosting separate web pages just to document your iOS and Android APIs</li></ul><p>What usually happens? You give up. The documentation becomes designer-oriented, engineers rarely look at it, and everyone goes back to inline docs in each code repo. The whole point of a centralised documentation site is defeated.</p><figure><img alt="The multi-platform problem: 1 Figma component branching to React, SwiftUI, and Jetpack Compose, versus a documentation platform that only has a slot for one tech stack" src="https://cdn-images-1.medium.com/max/1024/1*4wg-3VDJ3MLdlSY_jjI-hw.png" /></figure><h4><strong>The AI-readiness gap</strong></h4><p>This is the one that’s going to bite people hardest over the next year or two.</p><p>Your design system documentation is increasingly the instruction manual for AI agents. When product teams use <a href="https://claude.ai/">Claude</a>, <a href="https://cursor.sh/">Cursor</a>, <a href="https://bolt.new/">Bolt.new</a>, or <a href="https://lovable.dev/">Lovable</a> to generate UI, the quality of the output depends entirely on how much context the AI has about your design system — tokens, component APIs, usage rules, accessibility requirements, content guidelines.</p><p>If your documentation platform can’t expose that information in a structured, machine-readable way, it’s failing at what’s quickly becoming its most important job.</p><p>Here’s a concrete example: Zeroheight has a native block that displays text styles from your Figma library. Humans can see the styles on the page. But Zeroheight’s API can’t actually extract the data from those blocks. The information is visually there but programmatically invisible. An AI agent reading your docs through the API would have no idea those styles exist.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Otp6Z5NNYjDkNwAfGm4Vmw.png" /><figcaption>Side-by-side: a Zeroheight page showing text styles as a human sees it, versus what an API call returns (missing data)</figcaption></figure><h3><strong>Quick aside: why documentation matters even more now</strong></h3><p>You might be thinking: “If AI can read my Figma and code directly, do I even need documentation?”</p><p>Yes. Here’s why.</p><p>When your design system is small — just Figma and a React codebase — the source of truth is obvious. But when you start expanding to multiple tech stacks and platforms, you end up with multiple sources of truth. People start asking “where’s the reliable place where I can learn everything about this component?” — its status on each platform, its API for each tech stack, usage guidelines, accessibility notes, content design rules.</p><p>Documentation becomes the aggregator. The one place that ties everything together.</p><p>And for AI agents, that aggregator role is critical. The documentation is what you feed into Claude or Cursor so that generated UI is consistent with your product and brand. It’s the context layer that makes AI-assisted development actually work at scale.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qoDFcHbcMjSaINHgdYKjJg.png" /></figure><h3><strong>What you can build instead</strong></h3><p>Every tool here is either open-source or has a free tier that covers what you need.</p><h4><strong>The engine: </strong><a href="https://docusaurus.io/"><strong>Docusaurus</strong></a></h4><p>Open-source, built by Meta, designed specifically for documentation. It supports <a href="https://mdxjs.com/">MDX</a> — which means you can drop live React components directly into documentation pages. Built-in search (via <a href="https://docsearch.algolia.com/">Algolia DocSearch</a>, free for open-source projects), versioning, dark mode.</p><p>The killer feature for design systems: Docusaurus has a native <a href="https://docusaurus.io/docs/markdown-features/tabs">Tabs component</a>. One component page, multiple tabs:</p><ul><li><strong>Design tab:</strong> Visual specs pulled from Figma</li></ul><p><strong>Code:</strong></p><ul><li><strong>Web tab:</strong> Live Storybook embed or React code snippets</li><li><strong>iOS tab:</strong> SwiftUI snippets pulled from your repo</li><li><strong>Android tab:</strong> Jetpack Compose snippets pulled from your repo</li></ul><p>That multi-platform problem? Solved, for free.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qhoj7coS6hTt9xVvko0HTA.png" /><figcaption>Documentation rendered with Docusaurus</figcaption></figure><h4><strong>The designer-friendly layer: </strong><a href="https://tina.io/"><strong>TinaCMS</strong></a></h4><p>Open-source, self-hostable. Cloud plans start at <a href="https://tina.io/pricing/">$29/month</a> for teams if you want the hosted version. Otherwise, it’s free.</p><p>This is what makes the whole thing work for non-technical team members. TinaCMS gives your designers a visual editing interface at yourdocssite.com/admin. They see a WYSIWYG editor — fields for “Description,” “Do’s and Don’ts,” image uploads. When they hit Save, TinaCMS writes the content into a Markdown file and commits it to your GitHub repo. The designer never sees Git. They never see Markdown. They just edit and save.</p><p>You define a schema (basically a template) that structures each page type, so the experience is guided and consistent — not a blank text editor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uB3PmD33bjKNLFVmZfiooQ.png" /><figcaption>Screenshot from <a href="https://demo.tina.io/">https://demo.tina.io/</a></figcaption></figure><h4><strong>The glue: </strong><a href="https://github.com/southleft/figma-console-mcp"><strong>Figma Console MCP</strong></a><strong> + code repo MCPs</strong></h4><p>This is where AI enters the workflow. The Figma Console MCP bridges your Figma library and your documentation files. Instead of a designer manually typing “Button corner radius: 8px,” an AI agent queries Figma directly and extracts the actual value.</p><p>Combine that with a <a href="https://github.com/modelcontextprotocol/servers/tree/main/src/github">GitHub MCP</a>, and the same agent can also read your component source files — Swift, Kotlin, React — to pull API details, props, and default values.</p><p>The AI becomes your technical writer. You prompt it: <em>“Scan the Primary Button in Figma and the Button.kt file in the Android repo. Generate an MDX page listing design tokens vs. code properties for each platform.”</em> Out comes a .mdx file, ready to commit.</p><h4><strong>Hosting: GitHub + GitHub Actions</strong></h4><p>Free. Your docs repo lives on <a href="https://github.com/">GitHub</a>. Anytime someone pushes a change — whether it’s a developer merging code, a designer saving through TinaCMS, or an AI agent updating specs — <a href="https://github.com/features/actions">GitHub Actions</a> triggers a Docusaurus build and deploys to <a href="https://pages.github.com/">GitHub Pages</a>. You can also use <a href="https://vercel.com/">Vercel</a> or <a href="https://www.netlify.com/">Netlify</a>, both free for this use case.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C2ZohSXsI9ChbYYIsTwd7g.png" /></figure><h3><strong>How this works in practice</strong></h3><h4><strong>A designer changes something in Figma</strong></h4><ol><li>Designer updates the “Primary Button” corner radius in Figma.</li><li>They run a command (or a scheduled job does it automatically): <em>“Update the Button documentation.”</em> The AI agent grabs the new values from Figma via MCP and updates button.mdx.</li><li>The designer opens the TinaCMS admin, sees the updated specs, and adds a note: “Use this button for main calls to action.”</li><li>The site redeploys. Done.</li></ol><h4><strong>An engineer changes a component API</strong></h4><ol><li>An Android engineer corrects a property value in the Button component.</li><li>After the PR merges, a GitHub Action triggers the AI agent to update the Android section of button.mdx.</li><li>The site redeploys. The Android code snippets are current.</li></ol><p>No manual documentation updates. No “hey can someone update the docs?” Slack messages that get ignored for three (or more?) weeks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dY4I0bT8oZE6aqXjjAbVqg.png" /></figure><h3><strong>How to actually get started</strong></h3><p>You don’t need to build everything at once.</p><p><strong>Week 1: Setup the website.</strong></p><ul><li><strong>Stand up the site.</strong> Scaffold a <a href="https://docusaurus.io/docs/installation">Docusaurus site</a> (npx create-docusaurus@latest my-ds-docs classic), push it to GitHub, set up <a href="https://docusaurus.io/docs/deployment#deploying-to-github-pages">GitHub Pages deployment</a>. You now have a live, free, version-controlled documentation site.</li><li><strong>Add the designer-friendly editing layer.</strong> Integrate <a href="https://tina.io/docs/frameworks/docusaurus/">TinaCMS</a>. Define schemas for your page types. Your designers can now contribute from a browser.</li><li><strong>Connect your sources of truth.</strong> Set up the <a href="https://github.com/southleft/figma-console-mcp">Figma Console MCP</a>. Write a prompt template for your AI agent to generate.mdx pages from Figma data and code repo data.</li></ul><p><strong>Week 2: Automate.</strong> Create a GitHub Action on a nightly schedule (or on PR merge) that triggers the AI agent to check for changes and update docs. Add a Slack notification so the team knows when something’s been auto-updated.</p><p>Two weeks from zero to a fully automated, multi-platform, AI-ready documentation site. No subscriptions (!)</p><h3><strong>Being honest about the trade-offs</strong></h3><p>You’re trading subscription costs for engineering time. That means:</p><ul><li><strong>You (probably) need a developer for the initial setup.</strong> A designer can’t scaffold this alone. Someone needs to be comfortable with Node.js, GitHub Actions, and basic MCP configuration. (Perhaps Claude or Cursor can help you with this part.)</li><li><strong>You own the maintenance.</strong> When Docusaurus ships a breaking update, that’s your problem, not Zeroheight’s.</li><li><strong>MCP tooling is still maturing.</strong> Expect some rough edges. These tools are being actively developed and things move fast.</li><li><strong>You lose some out-of-the-box conveniences.</strong> Zeroheight has adoption dashboards. Supernova has built-in Storybook playgrounds. You can replicate these (Docusaurus + <a href="https://plausible.io/">Plausible Analytics</a> for tracking, Storybook iframe embeds for playgrounds), but it’s more work.</li></ul><p>For a solo designer maintaining a small system, Zeroheight’s free tier might still be the pragmatic choice. But for any team that’s scaling, supporting multiple platforms, or trying to make their design system AI-ready, the math changes fast.</p><h3><strong>Where this is all going</strong></h3><p>We’re at a point where connecting all your design system’s sources of truth is so easy that building a custom solution tailored to your actual needs makes more sense than conforming to what expensive, generic platforms offer.</p><p>Your documentation isn’t just a reference site anymore. It’s the context layer that powers every AI-assisted design and engineering decision your team makes. Build it like it matters.</p><h3><strong>Tools and resources:</strong></h3><ul><li><a href="https://docusaurus.io/">Docusaurus</a> — <a href="https://docusaurus.io/docs/installation">Installation</a> · <a href="https://docusaurus.io/docs/markdown-features/tabs">Tabs</a> · <a href="https://docusaurus.io/docs/deployment#deploying-to-github-pages">Deployment</a></li><li><a href="https://tina.io/">TinaCMS</a> — <a href="https://tina.io/docs/frameworks/docusaurus/">Docusaurus Integration</a> · <a href="https://tina.io/pricing/">Pricing</a></li><li><a href="https://github.com/southleft/figma-console-mcp">Figma Console MCP</a></li><li><a href="https://github.com/modelcontextprotocol/servers/tree/main/src/github">GitHub MCP Server</a></li><li><a href="https://www.figma.com/developers/api">Figma REST API</a></li><li><a href="https://zeroheight.com/pricing/">Zeroheight Pricing</a> · <a href="https://www.supernova.io/pricing">Supernova Pricing</a></li><li><a href="https://mdxjs.com/">MDX</a> · <a href="https://storybook.js.org/">Storybook</a></li><li><a href="https://github.com/features/actions">GitHub Actions</a> · <a href="https://pages.github.com/">GitHub Pages</a></li><li><a href="https://docsearch.algolia.com/">Algolia DocSearch</a> · <a href="https://plausible.io/">Plausible Analytics</a></li><li><a href="https://vercel.com/">Vercel</a> · <a href="https://www.netlify.com/">Netlify</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a10f1390987f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/all-about-design-systems/stop-paying-for-design-system-documentation-you-can-build-yourself-a10f1390987f">Stop paying for design system documentation you can build yourself</a> was originally published in <a href="https://medium.com/all-about-design-systems">All about Design Systems</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Can Product Designers be “Design System Designers”?]]></title>
            <link>https://medium.com/all-about-design-systems/can-product-designers-be-design-system-designers-c7be6c4b9a0c?source=rss-92434e7b7aca------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7be6c4b9a0c</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Mariana Rita]]></dc:creator>
            <pubDate>Thu, 14 Mar 2024 08:42:29 GMT</pubDate>
            <atom:updated>2024-03-14T08:42:29.463Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DiPF9kXvLKOX9cyZ7ZIEbg.png" /></figure><p>In organisations where the Design System is built in-house but has low maturity, it’s not uncommon for the Product designers working on digital products of the organisation to be the ones building the Design System.</p><p>On the other hand, in larger design teams, where the Design System is more mature and established, there will very likely be a Design System-dedicated team.</p><p>Why are these nuances relevant, and why am I starting to describe the differences between Design System designers and Product designers from these ideas? Because the fact that there are Product designers creating Design Systems makes it seem that Product designers and Design System designers are just the same. And this is not quite true.</p><h3>Product Design vs. Design Systems</h3><p>Let’s start by clarifying the differences in the two disciplines:</p><ol><li><strong>Product Design</strong>: Product Design involves determining what to offer and how to best meet customer demands. It focuses on the creation of individual products, considering user needs, functionality, and user experience.</li><li><strong>Design Systems</strong>: Design Systems are comprehensive sets of standards used to manage design at scale. They consist of reusable components, patterns, and guidelines that ensure consistency and efficiency in design across products.</li></ol><p>While Product Design is about creating specific products, Design Systems are about establishing a framework for consistent design across multiple products or platforms.</p><p>By definition, there’s a clear difference between Product Design and Design Systems, despite their similarities. In detail:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/1*cU1BW6_oISt8VmgoZuDtIw.png" /><figcaption>Summary of the differences between Product Design and Design Systems</figcaption></figure><p>Product Design and Design Systems are both integral elements within the broader field of design, but they serve different purposes and address distinct aspects of the design process.</p><p>Given the differences in these two disciplines, the role of the Product designer will differ from the role of the Design System designer.</p><h3>The differences in the roles of the Product Designer and the Design System Designer</h3><p>Expanding on the distinction between Product designers and Design System designers involves delving deeper into the complexity of their roles, the nuances of their daily tasks, and the broader impact of their work within an organisation.</p><h3>Product Designers</h3><h4>The range of responsibilities</h4><ul><li><strong>User-Centred Design Process</strong>: Product designers are heavily invested in the user-centred design process. This involves extensive user research, creating user personas, mapping out user journeys, and constantly iterating designs based on user feedback. Their objective is to solve real problems for real users, making empathy a crucial skill.</li><li><strong>Prototyping and Validation</strong>: They spend a significant amount of time prototyping various design solutions at different fidelity levels — from low-fidelity sketches to high-fidelity interactive prototypes. These prototypes are then used in usability testing sessions to validate hypothesis and design decisions with actual users, ensuring the final product is both usable and desirable.</li><li><strong>Visual and Interaction Design</strong>: Beyond just making products usable, Product designers also focus on making them visually appealing (UI design) and ensuring a smooth interactive experience (UX design), so that users not only can use the product but also enjoy using it. This requires a keen eye for visual design principles and an understanding of HCI.</li><li><strong>Cross-disciplinary Collaboration</strong>: They work closely with engineers, product managers, marketers, and possibly customer support teams, facilitating a shared understanding of user needs and ensuring that the solution fits within technical capabilities and business strategies.</li></ul><h4>Impact on the product they design</h4><p>Product designers directly influence the user’s interaction with the product, impacting user satisfaction, engagement, and ultimately, the success of the product in the market. They face challenges like balancing user needs with business goals, designing for various user segments, and ensuring accessibility and inclusivity.</p><h3>Design System Designer</h3><h4>The range of responsibilities</h4><ul><li><strong>System Thinking</strong>: Design System designers apply principles of system thinking to create scalable and reusable design solutions. They’re not just designing components in isolation but are considering how all the components can work together within and across products and platforms.</li><li><strong>Component Design and Documentation</strong>: A significant part of their role is to design the UI components and document them thoroughly. This documentation includes not only visual specifications (size, colour, typography) but also behavioural specifications (states, interactions, animations) and code guidelines for implementation.</li><li><strong>Maintaining and Evolving the Design System</strong>: The digital world is constantly evolving, so Design System designers must ensure that the Design System adapts and grows. This involves adding new components, deprecating outdated ones, and ensuring the system remains efficient and relevant.</li><li><strong>Advocacy and Education</strong>: Successfully implementing a Design System requires buy-in from various stakeholders within the organisation. Design System designers often find themselves educating others about the Design System, demonstrating its value, and training designers and developers on how to use it effectively.</li></ul><h4>Impact on the products they <em>serve</em></h4><p>Design System designers work on a meta-level, affecting the Product Design process across the entire organisation. Their work leads to increased design and development efficiency, improved consistency across products, and easier collaboration between teams. Their challenges often include managing the Design System’s growth to prevent bloat, ensuring adoption across the organisation, and keeping the system up-to-date with the most relevant design and technology standards.</p><h3>The overlaps in the roles</h3><p>Despite the distinct responsibilities and focus areas of Product designers and Design System designers, there are several overlaps in their roles, illustrating how interconnected these positions are within the ecosystem of product development. These overlaps often manifest in skills, methodologies, and objectives that both roles share to some extent:</p><h4><strong>Shared Focus on User Experience</strong></h4><p>Both roles have a deep commitment to enhancing the user experience (UX). Product designers directly shape the UX through their design decisions for specific products, while Design System designers influence the UX indirectly by providing the tools and guidelines that ensure consistency and usability across products. That is, of course, when considering the end users. Let’s not forget that the users of the Design System are the Product designers and engineers, and their UX is also considered by the Design System designer.</p><h4><strong>Design Principles and Best Practices</strong></h4><p>Both types of designers rely on a foundational understanding of design principles and best practices. This includes knowledge of colour theory, typography, layout, and interaction design principles that ensure the creation of appealing and functionally effective designs.</p><h4><strong>Collaboration and Communication</strong></h4><p>Collaboration with other team members, such as developers, product managers, and other designers, is crucial for both roles. Effective communication skills are necessary to advocate for design decisions, provide feedback, and ensure that design intentions are accurately implemented.</p><h4><strong>Prototyping and Testing</strong></h4><p>Both Product designers and Design System designers use prototyping tools to communicate design ideas and test them. Prototyping for a Product designer might focus on user flows and interactions within a specific product, while a Design System designer might prototype to test the flexibility and applicability of design components in various contexts.</p><h4><strong>Iteration and User Feedback</strong></h4><p>Iteration based on user feedback and data is a common process for both roles. Product designers iterate on product designs to better meet user needs, while Design System designers might iterate on components and guidelines to ensure they remain relevant and effective across different products and emerging business needs.</p><h4><strong>Attention to Accessibility and Inclusivity</strong></h4><p>Ensuring that designs are accessible and inclusive is a shared responsibility. Both roles need to consider a wide range of users and ensure that the products or components they design can be used by as many people as possible.</p><h4><strong>Use of Design and Prototyping Tools</strong></h4><p>Both roles require proficiency in design and prototyping tools, such as Figma and Sketch. These tools are used to create designs, build prototypes, and collaborate with team members.</p><h4><strong>Advocacy for Design Consistency</strong></h4><p>While Design System designers are directly responsible for creating the standards that ensure design consistency, Product designers also advocate for consistency in their work by adhering to these Design Systems and sometimes contributing to their evolution.</p><h4><strong>Documentation</strong></h4><p>Documentation is essential for both roles but in slightly different contexts. Product designers may document user flows, design decisions, and user research findings, whereas Design System designers focus on documenting Design System guidelines, component usage, and best practices.</p><h3>Final thoughts</h3><p>While both roles deliver designs, in one way or another, <strong>their focuses and processes are clearly distinct</strong>.</p><p><strong>Having a Product designer create a Design System can be risky</strong>, given the required systems thinking approach to create a component that is built in such a way that it responds consistently to existing user needs and has enough flexibility to be scalable for future cases.</p><p><strong>The opposite is also applicable</strong>; having a Design System designer create a product for the end user may not go as well as expected since Design System designers care less for the visual appeal of what they build and <strong>focus more on the rules and guidelines that will allow what they’re designing to address user needs, provide guidance for the engineers who’ll implement it, and be scalable for eventual future needs</strong>.</p><p>Product designers will focus on creating delightful and functional user experiences for specific products, while, in contrast, Design System designers invest in the infrastructure that enables consistent and efficient design across an organisation’s entire product line.</p><p>Nonetheless, both roles are crucial in delivering high-quality digital products and experiences.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7be6c4b9a0c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/all-about-design-systems/can-product-designers-be-design-system-designers-c7be6c4b9a0c">Can Product Designers be “Design System Designers”?</a> was originally published in <a href="https://medium.com/all-about-design-systems">All about Design Systems</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unlocking seamless design handoffs: The critical intersection of Design Systems and Design Ops]]></title>
            <link>https://medium.com/all-about-design-systems/design-systems-and-design-ops-how-do-these-two-relate-and-differ-a4dd1d8094fd?source=rss-92434e7b7aca------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4dd1d8094fd</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[designops]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Mariana Rita]]></dc:creator>
            <pubDate>Fri, 01 Mar 2024 12:22:42 GMT</pubDate>
            <atom:updated>2024-03-04T16:43:31.213Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mcNBZQgmfHtyUkmCBUzybw.png" /></figure><p>In the last quarter, my team conducted a research project aimed at uncovering the challenges and opportunities for the Design System in the process of hand off from Product Designers to Frontend Engineers.</p><p>The research results were extremely insightful. However, when transforming the insights into action points, it kept on raising this question in my mind: <em>Who should take the findings and make them a reality — the Design System or Design Ops?</em> This might seem like a minor detail, but it’s crucial for making sure <strong>we’re focusing on the right tasks and not spreading ourselves too thinly</strong>.</p><p>Taking on tasks that aren’t really ours can lead to an overwhelming amount of work and can also mask underlying problems that need to be addressed. It may create a precedent where we’re expected to continue covering tasks that aren’t ours, making it less evident to everyone that there’s a gap in the responsibility structure — because we’re the ones continually filling that gap.</p><p>To get to the bottom of this, we need to understand the roles of Design Ops and Design Systems:</p><ul><li><strong>Design Ops is all about making designers’ lives easier.</strong> As a team, its focus is on identifying the best tools, methods, and processes so that designers can produce and deliver their best work.</li><li><strong>Design System provides a toolkit of design elements that ensure consistency and quality across what a company creates.</strong> It’s a foundation that helps both designers and engineers build products more efficiently and consistently.</li></ul><p>While both aim to improve the design process, they do so in different ways. Design Ops focuses on refining how designers work, and Design Systems provide the components that make it easier to implement designs consistently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hilRfujHnJ_I_y9jB9KH-A.png" /><figcaption>Summary of the differences between Design Systems and Design Ops</figcaption></figure><h3>Design Ops</h3><p>Short for Design Operations, Design Ops is an emerging discipline within the design field focused on optimising the operational aspects of the design process.</p><p><strong>Its core mission is to streamline and enhance the efficiency, scalability, and impact of design teams within organisations.</strong> By addressing the ‘how’ of design work, Design Ops aims to bridge the gap between the strategic importance of design and its day-to-day implementation.</p><p>Some key responsibilities of Design Ops include:</p><ol><li><strong>Optimising processes and workflows</strong>, aiming for increased efficiency and transparency. This involves identifying bottlenecks, implementing project management tools, and establishing workflows to ensure design projects meet quality standards.</li><li><strong>Managing tools and platforms</strong>, ensuring the design team has access to the technologies that best suit their needs.</li><li><strong>Cross-functional collaboration</strong>, connecting the dots between design teams and other departments, such as engineering, product management, brand and marketing.</li><li><strong>Analysing metrics and performance</strong> is not uncommon, with the goal of measuring the impact of design within the organisation.</li><li><strong>Advocating for design culture</strong>, championing design thinking, and user-centric approaches at all levels, aiming to elevate the strategic role of design in business outcomes.</li></ol><p>Given the organisational context, these responsibilities may vary, and the scope of Design Ops can become more narrow or broader.</p><p>In essence, <strong>Design Ops empowers design teams to do their best work</strong> — removing obstacles, providing the right tools and resources, and ensuring that design can fully contribute to achieving business goals.</p><h3>Design System</h3><p>Design Systems are comprehensive sets of guidelines, principles, and components used in digital product design and development. They serve as a blueprint, ensuring consistency, efficiency, and quality across an organisation’s products and digital experiences.</p><p>A well-implemented Design System enables teams to create cohesive user interfaces (UI) and user experiences (UX) that align with the brand’s visual and functional standards.</p><p>Some of the core components of Design Systems are:</p><ol><li><strong>UI Toolkit</strong> — the heart of a Design System, including reusable design elements (such as buttons, form elements, typography styles, colour palettes, icons, and more). Each component is defined with specified design properties and behaviours, ensuring visual and functional consistency across platforms and usages.</li><li><strong>Design Principles and Guidelines</strong> that reflect the brand’s <em>ethos</em> and approach to UX. These principles guide decision-making and design practices within the team, striving for a shared understanding of design values.</li><li><strong>Code Libraries</strong> bridging the gap between design and development. This ensures that the released product closely aligns with the intended design and reduces the time needed for development.</li><li><strong>Documentation and standards</strong> covering how to use the components, apply the design principles, adhere to best practices, and contribute to the system. The documentation acts (ideally) as a single source of truth for both designers and developers.</li><li><strong>Accessibility guidelines</strong> for component usage, including considerations for colour contrast, keyboard navigation, screen reader compatibility, and more.</li><li><strong>Patterns and templates</strong> for common UI layouts and interactions, helping to ensure consistency and streamlining the design process.</li></ol><h3>How do these two coexist?</h3><p>In some companies, the Design System team is part of Design Ops, which might suggest a lot of overlap. However, each has a special focus. For example, the Design System team shouldn’t be <em>dictating</em> how designers hand over work to engineers or setting rules for the design process.</p><p>Here are a few statements that help illustrate the difference between the scopes of Design Systems and Design Ops:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JJrkRFRmtxDOR4l6VFP2IA.png" /><figcaption>Statements that help illustrate the difference between the scopes of Design Systems and Design Ops.</figcaption></figure><p>*Note: Both Design Systems and Design Ops are responsible for ensuring accessibility standards are met. However, the Design System team focuses on building accessible components, while Design Ops ensures that the design process and team workflows prioritise and incorporate accessibility considerations.</p><h3>So… what was the conclusion of the research pursued by my team?</h3><p>Returning to the original research project, our final understanding was that there is not much the Design System team can do regarding specific ways of working. Most of the pains points stemmed from a lack of knowledge on how to use Figma efficiently. We did identify some improvement points regarding our documentation. However, tackling design file templates, alignment on ways of working, as well as providing training to design teams is, unfortunately, beyond what a design system and its team can do.</p><p>Considering the differences between the roles of Design System and Design Ops, this is an example of where the two disciplines can complement each other in areas common to both.</p><p>Looking specifically at the design handoff (from product designer to frontend engineer), here’s an attempt to summarise the concrete items that Design Systems and Design Ops can cover:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fw-RHLY4oi6vrWiyvvNsyQ.png" /><figcaption>Summary of concrete items that Design Systems and Design Ops can cover regarding the design handoff to engineering.</figcaption></figure><p>Both Design System and Design Ops aim to reduce the layers of decisions Product Designers need to think about while designing, but from different perspectives.</p><p>On a general scale, <strong>Design Systems provide the UI elements that enable efficiency for Product Designers during the design phase, as well as scalability for the solutions they create.</strong></p><p>On the other hand, <strong>Design Ops provides the tooling and guidelines for Product Designers to follow, so that they work better and in streamlined ways.</strong></p><p><strong>Both Design Systems and Design Ops aim for efficiency</strong>, but Design Systems care for the deliverables, and Design Ops care for the ways of working.</p><p>In short, in the handoff process, Design Systems provide UI elements that are common to both designers and engineers, making it easier for engineers to implement what designers deliver; Design Ops ensures designers have the necessary tools and guidelines so that they can focus on designing and delivering within the set timelines.</p><h3>In conclusion</h3><p>Design System and Design Ops, while aiming for the same outcome (increased efficiency and consistency), are separate disciplines.</p><p>The concrete example of the role these two play in the design handoff to engineering illustrates clearly how these areas complement each other but do not coincide.</p><p>Even though it is not uncommon to have Design Ops teams creating Design Systems, it’s important to understand that they’re not the same. One focuses on ways of working, and the other is the product/technology that product teams use.</p><p>Maintaining clear boundaries between Design System and Design Ops is vital for a well-coordinated and effective design workflow. By understanding the unique roles these disciplines play, we pursue a transparent and efficient design process that enhances the overall productivity of the organisation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4dd1d8094fd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/all-about-design-systems/design-systems-and-design-ops-how-do-these-two-relate-and-differ-a4dd1d8094fd">Unlocking seamless design handoffs: The critical intersection of Design Systems and Design Ops</a> was originally published in <a href="https://medium.com/all-about-design-systems">All about Design Systems</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>