<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>#Design Systems on Barbara Denney</title><link>https://barbaradenney.com/tags/%23design-systems/</link><description>Recent content in #Design Systems on Barbara Denney</description><generator>Hugo -- 0.148.2</generator><language>en-us</language><lastBuildDate>Wed, 06 Aug 2025 10:15:00 -0600</lastBuildDate><atom:link href="https://barbaradenney.com/tags/%23design-systems/index.xml" rel="self" type="application/rss+xml"/><item><title>Experimenting with Annotation Mode in Figma</title><link>https://barbaradenney.com/posts/figma-annotation-mode-experiment-design-systems-workflow/</link><pubDate>Wed, 06 Aug 2025 10:15:00 -0600</pubDate><guid>https://barbaradenney.com/posts/figma-annotation-mode-experiment-design-systems-workflow/</guid><description>&lt;h2 id="background">Background&lt;/h2>
&lt;p>Our design team recently began exploring a new way to annotate designs directly in Figma. While searching for examples of this technique online, we came up short, which made us wonder if other teams were thinking about this the same way we were.&lt;/p>
&lt;p>Figma already supports switching between properties using &lt;strong>modes&lt;/strong> which is great for themes like light/dark mode or responsive layouts. We started thinking, could we use modes to annotate?&lt;/p></description></item><item><title>Reflection on Early Lessons</title><link>https://barbaradenney.com/posts/design-system-operational-processes-sustainability-reflection/</link><pubDate>Tue, 29 Jul 2025 16:30:00 -0600</pubDate><guid>https://barbaradenney.com/posts/design-system-operational-processes-sustainability-reflection/</guid><description>&lt;h2 id="looking-back-on-hard-won-lessons">Looking Back on Hard-Won Lessons&lt;/h2>
&lt;p>A few years ago, I wrote a &lt;a href="https://adhoc.team/2022/07/18/using-design-systems-digital-success-federal-space/">blog post&lt;/a> reflecting on the early lessons from establishing a new design system. The big ideas I shared that focused on creating alignment, scaling consistency, and building shared patterns remain as relevant as ever.&lt;/p>
&lt;p>But with more experience under my belt, I&amp;rsquo;ve come to understand that &lt;strong>operational processes&lt;/strong> are the invisible foundation that determines whether a design system thrives or slowly deteriorates. These can be considered Design System operations.&lt;/p></description></item><item><title>Design System Series: Part 1 – Why We Built It</title><link>https://barbaradenney.com/posts/design-system-series-part1-why-we-built-government-website/</link><pubDate>Sat, 12 Jul 2025 09:20:00 -0600</pubDate><guid>https://barbaradenney.com/posts/design-system-series-part1-why-we-built-government-website/</guid><description>&lt;ul>
&lt;li>&lt;strong>Part 1: Why We Built It&lt;/strong> &lt;em>(You are here)&lt;/em>&lt;/li>
&lt;li>&lt;a href="../design-system-series-part2-gaining-stakeholder-buy-in-government/">Part 2: Gaining Stakeholder Buy-In&lt;/a>&lt;/li>
&lt;li>&lt;a href="../design-system-series-part3-breaking-silos-team-communication/">Part 3: Breaking Down Silos Through Communication&lt;/a>&lt;/li>
&lt;li>&lt;a href="../design-system-series-part4-driving-team-adoption-strategies/">Part 4: Driving Team Adoption&lt;/a>&lt;/li>
&lt;li>&lt;a href="../design-system-series-part5-lessons-learned-starting-design-system/">Part 5: Lessons Learned&lt;/a>&lt;/li>
&lt;/ul>
&lt;hr>
&lt;h2 id="background">Background&lt;/h2>
&lt;p>The client’s website was undergoing a bold redesign: new tech, new processes, new branding.&lt;/p>
&lt;p>Initially, things were going well until we learned another team’s redesign looked very different, despite being based on the same ui-kit. We were all using the same UI-kit but designs and patterns were being applied differently, depending on the team. This discrepancy highlighted the need for a &lt;strong>shared resource&lt;/strong>: a Design System.&lt;/p></description></item></channel></rss>