<?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 Jessi Shaver on Medium]]></title>
        <description><![CDATA[Stories by Jessi Shaver on Medium]]></description>
        <link>https://medium.com/@jessi.shaver?source=rss-66d5c90c7458------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*NPS53fRq8Zjy257qWNxCIw.jpeg</url>
            <title>Stories by Jessi Shaver on Medium</title>
            <link>https://medium.com/@jessi.shaver?source=rss-66d5c90c7458------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 10:41:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jessi.shaver/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[The Problem with Variables in Figma]]></title>
            <link>https://www.designsystemscollective.com/the-problem-with-variables-in-figma-81ac40161b04?source=rss-66d5c90c7458------2</link>
            <guid isPermaLink="false">https://medium.com/p/81ac40161b04</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[figma-plugin]]></category>
            <dc:creator><![CDATA[Jessi Shaver]]></dc:creator>
            <pubDate>Thu, 05 Jun 2025 02:57:49 GMT</pubDate>
            <atom:updated>2025-06-07T11:30:03.713Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2d40TwS3oXWEcSQTbXBugA.png" /></figure><p>Figma leaves much to be desired in terms of supporting design systems. In 2024, we finally got variables for typography, continuing a shift away from styles towards a more sustainable system. However, in 2025, as Figma begins to tackle a range of other design challenges in the market, variables have been somewhat neglected.</p><p>Sure, we received some useful quality-of-life updates, including variable analytics, the ability to copy and paste variables, displaying values and descriptions on hover, resizing columns, and a few other enhancements I might have missed. Nevertheless, these are features that should have been available right from the start.</p><p>As Figma dominates the design tooling market, it often feels like the platform is doing the bare minimum to check boxes, relying on the community to develop solutions for problems it seems unwilling to address — until it decides to acquire them. But that’s also what makes Figma shine: the community has genuinely helped me thrive in the world of design systems. I want to explore some challenges I’ve faced and the plugins that have been invaluable and deserve your support:</p><h3>Styles &amp; Variable Organizer</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wQPVLzgWT7j2x-atRow_zw.png" /><figcaption>Finding those pesky unlinked variables…</figcaption></figure><p>When updating a component library to a new architecture, I decided to start from scratch by auditing and understanding the current usage of existing tokens. I discovered numerous redundant values that were highly specific and could have been more generalized. However, remapping every single token from the previous set to the new one proved to be a challenging task. As components became more complex, with additional layers and instances, it became increasingly difficult to swap variables seamlessly without overlooking a few. This often resulted in designers encountering incorrect modes or options in the design system library.</p><p><a href="https://www.figma.com/community/plugin/816627069580757929/styles-variables-organizer"><strong>Styles &amp; Variable Organizer</strong></a><strong> </strong>saved me a significant amount of time by allowing me to spot-check components and see what was being referenced locally, externally, or even undefined. It works for both variables and styles, enabling you to target any instance and swap it with your chosen variable or merge it with another variable of the same value.</p><h3>Variant Organiser</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9RCoseUOj7qgIj304q5eOw.png" /><figcaption>Does this spark joy?</figcaption></figure><p>Managing complex components with multiple variants in Figma can quickly become clunky. Despite having standardized naming conventions for variant properties, arranging components consistently, especially when dealing with various sizes, states, and styles, can be challenging. In the design system I work with, buttons are available in three sizes: small, medium, and large, with medium being the default. This setup often leads to visual awkwardness when displaying all sizes together, raising questions about the optimal organization: should it be by size, state, style, or something else?</p><p><a href="https://www.figma.com/community/plugin/1047796251364453654/variant-organiser"><strong>Variant Organiser</strong></a> addresses these challenges by offering two modes:</p><ol><li>Automatically organizing variants based on the order of variant properties in the Design panel.</li><li>Manually define which properties appear as columns and rows to customize the organization.</li></ol><p>The plugin can also help identify missing variants to ensure a component is complete. It also provides property labels for each column and row, making it easier to understand at a glance. TL;DR: Using Variant Organiser helped save time on manually adjusting how components are presented easily.</p><h3>Variable Usage Counter</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cC5jRaijkpgs-fTQcg8xAQ.png" /><figcaption>The numbers, Mason! What do they mean?</figcaption></figure><p>While Figma finally offers variable analytics, it’s insufficient for understanding what’s actually being used in the library and how it can be improved. It lacks clarity on the distinction between instances and the variables themselves. For instance, one of our tokens shows a high usage count because many components are interactive, like color-interaction-base-border. However, this high usage doesn’t mean every component is interactive; instead, components like cards may contain interactive elements, which can inflate metrics due to instances of a variable being included. Overall, Figma’s analytics leave much to be desired, often requiring users to do significant work to understand the data effectively.</p><p>Enter: <a href="https://www.figma.com/community/plugin/1457829396420831856/variables-usage-counter"><strong>Variable Usage Counter</strong></a></p><p>This plugin not only provides metrics for variables across an entire file but also specifies where each variable is used and whether it is an instance or directly mapped to text, vector, frame, or shape. This was incredibly helpful in consolidating our design token architecture further. Upon initially adopting a new architecture, we felt the need to maintain a token set that distinguished between interaction elements and input elements, as they had different color applications. However, further investigation revealed that separating them was not needed due to their minimal usage. This data helped us decide whether to use component-level variables or consolidate them towards a more concise and simplified set.</p><p>Another honorable mention goes to <a href="https://www.figma.com/community/plugin/1440799497106254634/variablescout"><strong>Variable</strong> <strong>Scout</strong></a>.</p><p>This plugin scans a page to display the variables being used across collections. However, I’d love a version that scans an entire file, as it currently provides a great way to drill into the composition of components and see how many variables are used at a glance.</p><h3>Variables Documentation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5fo75jy957CNJzv_q6EtCw.png" /></figure><p>To this day, I don’t understand why Figma won’t make the variables panel accessible to all users. There’s no easy way for users to review how variables are set up as viewers of a library. They only become visible and searchable when working on designs and adjusting properties.</p><p>Speaking of which, why can’t we search and filter within the variables panel itself? Is anyone else bothered by this?</p><p>It raises the ongoing question of how we can provide guidance to designers about variables if they aren’t immediately available. I’ve experimented with various plugins to support this, but I found the most success with <strong>V</strong><a href="https://www.figma.com/community/plugin/1493511839808963998/variables-documentation"><strong>ariables</strong> <strong>Documentation</strong></a>. This plugin offers numerous customization options, allowing you to choose which details to show, including the name, values (especially if they map to another variable), scope, and more. You can also update the UI to display the information as needed.</p><p>I have modified this plugin’s format to make it easier for designers to review. Ideally, the documentation site for the design system should serve as the source of truth, but having everything within Figma streamlines the designer’s workflow. Unfortunately, I lack the experience leveraging other tools, such as Supernova and Knapsack, to speak on whether they’re effective in managing systems at scale. But I’d love to learn and hear more about other’s experiences.</p><h3>Parting Thoughts</h3><p>Variables marked a significant step forward in managing design systems in Figma. However, like any evolving feature, there are areas where improvements can improve usability and efficiency. My experience is one of many — while I’ve focused on refining existing systems, others face challenges with multi-brand support, building from scratch, or managing complex, hybrid systems.</p><p><strong>The community has played a critical role in bridging some of these gaps. </strong>While it’s encouraging to see incremental updates, there’s a growing need for more robust solutions from Figma to address the complexities of design systems. Better analytics, improved management tools, and greater accessibility for all designers would make a difference.</p><p>For designers in a similar space, using plugins can streamline your workflow. Additionally, providing feedback to Figma about these challenges can encourage them to meet the community’s needs better. Just as the community has done, let’s continue to share our experiences, approaches, and ideas to foster a better design experience for all.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81ac40161b04" width="1" height="1" alt=""><hr><p><a href="https://www.designsystemscollective.com/the-problem-with-variables-in-figma-81ac40161b04">The Problem with Variables in Figma</a> was originally published in <a href="https://www.designsystemscollective.com/">Design Systems Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The UX of Parenting]]></title>
            <link>https://medium.com/@jessi.shaver/the-ux-of-parenting-0fbdc1433c34?source=rss-66d5c90c7458------2</link>
            <guid isPermaLink="false">https://medium.com/p/0fbdc1433c34</guid>
            <dc:creator><![CDATA[Jessi Shaver]]></dc:creator>
            <pubDate>Tue, 04 Feb 2025 19:42:09 GMT</pubDate>
            <atom:updated>2025-02-05T20:14:22.359Z</atom:updated>
            <content:encoded><![CDATA[<p>Parenting is a lot like assembling IKEA furniture without instructions. It appears easy enough, but you constantly find yourself putting parts together incorrectly or have no clue what to do. I have a preschooler and a 15-month-old, and I can confidently say that I learned a lot about myself in the short time they’ve been in my life. It has humbled me in several ways, from developing an extraordinary amount of patience to adapting how I communicate to help my kids understand and grow. Let me be clear: parenting is not easy, and I just got started. It will get more challenging and complicated as the years go on. I’ve read many books and articles and talked with several people for advice, and even with all that information, I am sometimes still at a complete loss.</p><p>I bring this topic up because I find a lot of overlap between parenting and UX design. The goal of a UX designer is to create intuitive, usable, and sometimes enjoyable experiences that help users do something. We design experiences based on what users need.</p><p>And sometimes, we have no idea what they need, whether it’s circumstance, a lack of data, or countless other reasons. The same applies to young children. Understanding what they need when communication ranges between limited and non-existent is challenging. But fear not: common practices in UX can also apply to parenting. And this isn’t treating children like users, or our users like children. It’s about embracing the empathic side of design to support and uplift others.</p><h3>Listen beyond words</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/1*b1UbxI8zjGJHcS3skq2PrA.gif" /><figcaption>No words, just a rainy day.</figcaption></figure><p>UX is about understanding user needs. However, what users explicitly say may not express what they need. There’s more to a person than their words, but also the actions they take and the environment they’re in. The same applies to children: they may not fully understand the words they use, or they resort to full-blown meltdowns (tears and runny nose included).</p><p>Observe what users do. Understand their environment, mindset, and what they’re trying to do to help them reach their goals. Sometimes, it’ll require some trial and error, but that’s what iteration is about. You learn, adapt, and try again. I’ve experienced enough existential dread in my life to figure out exactly what my kids need from me. Emotions get high, and I’ve had to take a deep breath to realize I’ll do enough things wrong to get it right, even if it takes months. Speaking of trial and error…</p><h3>You’re going to get it wrong, and that’s okay</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q5CnqmZz2nLmFiaEfIHxng.png" /><figcaption>What forgetting floaties can do</figcaption></figure><p>Life is all about learning. Sometimes, an idea, workflow, or design you’ve thought of doesn’t work well in practice. The feedback you get from your work allows you to continuously improve users’ experiences. What you iterate on can span from a little tweak to something entirely different. It is essential to recognize that it takes time to get things right and that patience will get you there. It’s hard to be patient when we want things to work the first time around, but there’s a lot to gain from learning.</p><p>It’s hard to describe how I thought I was patient until I became a parent. I’m constantly in a tug-of-war between annoyed and extremely confused to utterly lost. I’m annoyed when the countless approaches I’ve read about having my oldest listen fail exceptionally. I’m extremely confused when my youngest is flailing for food, but when presented with their favorite thing to eat, decides to yeet their milk bottle to the shadow realm and paint the floor with food. In all this chaos, I learned that trying one thing and staying consistent works. Or even though my kid’s hungry, maybe they’re not in the mood for their favorite thing, or they’re teething (which sucks, by the way). Embrace the chaos of being wrong, even if it’s nonsensical. There’s is something to learn from it just by trying and adapting.</p><h3>Consider every action has a reaction</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*Ep8zzYtq31atcuR9LSLybA.gif" /><figcaption>When you have the receipts to make Bingo sad</figcaption></figure><p>An optimal user experience is the happy path. The user quickly gets from point A to point B and it’s a job well done. But what happens when something goes wrong? What if an error occurs or something unexpected happens? Is the experience accessible to everyone regardless of ability or disability? I mentioned earlier that a UX designer’s goal includes creating “sometimes enjoyable” experiences. Not every experience is enjoyable, but we must support users through it. The user experience is greater than the sum of its parts. The error, edge, and unideal cases should be considered with the same level of care as the happy path.</p><p>You might browse my Instagram and think my kids are always happy by smiling brightly and enjoying the world around them. But the experiences you don’t see are just as meaningful. Every tantrum requires patience and understanding to help my oldest learn good habits. Every restless night requires attention and care to ensure my youngest sleeps comfortably, even if they sleeps on the edge of the crib and spits out their pacifier countless times. Every experience, good and bad, works towards a happy path.</p><h3>In the end</h3><p>A phrase that always stuck with me from a keynote I heard from Cameron Moll is “Done is better than perfect.” You can unpack a lot with that, especially if you enter the nebulous void of “what is the definition of done” (which I still haven’t figured out). Creating the perfect experience may never be possible, but being able to put something out in the world allows it to get better. People naturally want positive experiences, even if they are difficult to get right. But with time, patience, and thoughtfulness, you’re always a step closer to something better, no matter the level of impact. Take a moment to appreciate that.</p><p>In the infinite wisdom that comes from Bluey, there’s something you need to know. <strong>You’re doing great.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*GHe0VjFDcB8gyWKcnBybQg.gif" /><figcaption>Bella brings wisdom and comfort with three words.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0fbdc1433c34" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weathering the Storm: The Midlife UX Crisis]]></title>
            <link>https://medium.com/design-bootcamp/weathering-the-storm-the-midlife-ux-crisis-371e6fa9f9ba?source=rss-66d5c90c7458------2</link>
            <guid isPermaLink="false">https://medium.com/p/371e6fa9f9ba</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Jessi Shaver]]></dc:creator>
            <pubDate>Wed, 18 Dec 2024 22:34:46 GMT</pubDate>
            <atom:updated>2024-12-19T19:50:43.365Z</atom:updated>
            <content:encoded><![CDATA[<p>The UX industry is in an interesting place. Over the past decade, we’ve witnessed tremendous growth in the field, with UX practitioners becoming more specialized to hone their craft: research, design, accessibility, testing, operations, writing, engineering, strategy — the list could go on. There is infinite potential in what UX can contribute, and it’s incredibly exciting.</p><p>However, with the end of 2024 upon us, there’s been a worrying shift in the <a href="https://trends.uxdesign.cc/">current state of UX</a>:</p><ul><li>Companies are prioritizing speed over quality. This isn’t a new problem, but one making a strong comeback. Designers are pressured to make quick decisions and assumptions in their work without the guarantee of revisiting them to move on to the next thing. Treating features as flavors-of-the-week comes with neglecting user needs and at the cost of creating substandard experiences.</li><li>User Research is consistently on the cutting room floor, with continued layoffs trending in the tech industry. Research is commonly treated as something that costs both money and time that many are unwilling to invest. Instead, designers may find themselves taking this role to the best of their ability, trending them back into a generalist role that assumes more responsibility. Or even worse, it gets ignored entirely.</li><li>UX Practitioners continue to diligently fight, advocate, and evangelize the value they bring. Despite the many studies, success stories, and organizations that embody and/or showcase good design — many still treat design as pixels to be pushed over problems to be solved. It’s still a shared norm that designers must paint the house without fixing the underlying foundation.</li><li>AI has both excitement and skepticism. It can accelerate the ability to deliver quality experiences and compensate where designers may lack data, support, and resources. However, it comes at the potential cost of <a href="https://www.researchgate.net/publication/380522812_Concerns_and_Challenges_of_AI_Tools_in_the_UIUX_Design_Process_A_Cross-Sectional_Survey">replacing the work we do</a> (Figma is watching you).</li></ul><p>I have seen various ways UX has regressed throughout my design career. I’ve started to feel insane that in each new role I step in, the environment is increasingly worse, and I repeatedly face the same problems I worked through in the role before. How often will I have to advocate that design should have an equal seat at the table as other roles when making decisions (engineering, product management, etc)? How many times will I have to push for validating decisions through research over designing purely on assumptions? How often will I have to create experiences for the sake of an announcement at an event over making scalable, durable decisions? How much longer do designers and other UX practitioners need to wait to get the overdue recognition they deserve?</p><h3><strong>The answer: I have <em>no</em> idea. And I’m tired.</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/369/1*pqx4edrvBDPldtsH5uGAzw.gif" /><figcaption>We’ve all been there, Browns fan.</figcaption></figure><p>I’m only human. My job requires me to work with other humans and create impactful experiences for humans. We all have our priorities, ambitions, goals, and mindsets that may never align or be understood. And you may read this and say to yourself, “Yeah, Jessi, but this is what is expected of UX — stop complaining. How do you expect UX to mature if you’re not willing to make the push?” And you’re absolutely right; any role that isn’t recognized as valuable comes with some much-needed grit to be an agent of change for yourself, your team, your company, and the industry.</p><p>So…what now? How do we stay sane in an environment that may do everything to make us think otherwise?</p><p>I’m no expert, and I don’t know everything. But I do know what’s worked well for me throughout my career. These are 3 things that I’ll focus on for 2025 and the years to come. And I hope they will be helpful to you in some way:</p><h3>1. Be a change agent. Be an advocate for yourself.</h3><p>I know, I know. I was complaining about how this is a never-ending struggle. But there are so many ways to have a positive impact that can change things for the better, even if it’s exclusively for your benefit. Start small and expect to fail, <strong>but learn</strong>. Change is scary and will always come with some amount of resistance. Recognize what’s in your control and try new or different things that may be beneficial. Whenever possible, speak up and don’t accept things as they are, especially if it doesn’t make sense. What you learn from whatever you try is crucial in moving the needle.</p><h3>2. Build meaningful relationships.</h3><p>You’re not alone. There are people here to support and uplift you, in or outside of work. If you struggle to progress, have conversations with anyone interested in your challenges, ideas, or perspective. Be sure to listen actively to theirs too . These could be fellow team members (especially if you work on a cross-discipline team), individuals across your organization, a former colleague, or even someone you’ve connected with on LinkedIn. Use this dynamic to ask tough questions, such as considering if something is the right thing to do.</p><p>Having allies can help create a coalition that fosters alignment, collaboration, and a sense of community. At the very least, it can be a sanity check and provide a space to unload.</p><h3>3. Disconnect.</h3><p>Work is important. You were brought into whatever role you’re currently in for a reason — because you can have an impact. Whether it’s your craft, personality, or potential, people have expectations and rely on you. However, we are setting the bar unreasonably high for ourselves more often than not. We push ourselves to do more than what’s asked of us because we know it’ll work towards a positive outcome.</p><p>But everyone has limits. It’s easy to ignore those limits and ultimately fall into the abyss of burnout. Know your limits and when to ask for help. If you feel you’re doing too much, get someone else involved. If you’re working overtime to get something done, understand and acknowledge the cost to <strong>you</strong>. I’m not suggesting that these are situations you should avoid, but they will weigh on you to some degree and test your resilience.</p><p>Push yourself as far as you want, but don’t beat yourself up. Be proud of yourself and your contributions, but also be able to walk away. You do not need to pull heroics time and time again. Bring people along for the ride and learn together.</p><p>For those that made it this far, thank you.</p><p>I’ve wanted to share my thoughts, experiences, and ideas about UX for a long time. I always felt that others did a much better job doing it, so why bother? Over time, I realized that I, too, have a voice and can use it, even if it’s echoing what others have been saying. I also want to use this as an opportunity to platform others who deserve recognition. So we’ll see what happens.</p><p>Until next time 👋</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*8euFKFBHUiKFubxE4HOcxw.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=371e6fa9f9ba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/weathering-the-storm-the-midlife-ux-crisis-371e6fa9f9ba">Weathering the Storm: The Midlife UX Crisis</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>