<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Design Jargon: new words</title>
    <link>https://designjargon.fyi</link>
    <description>New design words, each with a live demo, a plain meaning and a line you can say to your team or your AI tool.</description>
    <language>en-us</language>
    <lastBuildDate>Mon, 02 Nov 2026 09:00:00 GMT</lastBuildDate>
    <atom:link href="https://designjargon.fyi/new.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Design system</title>
      <link>https://designjargon.fyi/design-system</link>
      <guid isPermaLink="true">https://designjargon.fyi/design-system</guid>
      <pubDate>Mon, 02 Nov 2026 09:00:00 GMT</pubDate>
      <description>A shared kit of components, design tokens and rules that designers and developers both use, so every screen looks and works the same way. To say it: Are we building from the design system here? If this is a new pattern, can we add it there instead?</description>
    </item>
    <item>
      <title>Accessibility</title>
      <link>https://designjargon.fyi/accessibility</link>
      <guid isPermaLink="true">https://designjargon.fyi/accessibility</guid>
      <pubDate>Mon, 02 Nov 2026 09:00:00 GMT</pubDate>
      <description>Designing so everyone can use the product, including people with low vision, people using a keyboard or a screen reader, and people sensitive to motion. Often written a11y. To say it: Can we check this against accessibility basics before launch: contrast, keyboard use and labels?</description>
    </item>
    <item>
      <title>Usability</title>
      <link>https://designjargon.fyi/usability</link>
      <guid isPermaLink="true">https://designjargon.fyi/usability</guid>
      <pubDate>Mon, 02 Nov 2026 09:00:00 GMT</pubDate>
      <description>How easily people can use something to do what they came to do: how fast they learn it, how few mistakes they make, and how they feel after. To say it: I think there’s a usability problem here. People keep missing this step. Can we look at why?</description>
    </item>
    <item>
      <title>UI</title>
      <link>https://designjargon.fyi/ui</link>
      <guid isPermaLink="true">https://designjargon.fyi/ui</guid>
      <pubDate>Mon, 02 Nov 2026 09:00:00 GMT</pubDate>
      <description>User interface: the parts of a product you see and touch, like buttons, text, colors and layout. UI is how it looks and responds; UX is the whole experience. To say it: The flow works, so this is a UI pass: clearer hierarchy and more consistent spacing, not new steps.</description>
    </item>
    <item>
      <title>UX</title>
      <link>https://designjargon.fyi/ux</link>
      <guid isPermaLink="true">https://designjargon.fyi/ux</guid>
      <pubDate>Mon, 02 Nov 2026 09:00:00 GMT</pubDate>
      <description>User experience: everything about how using a product feels, from finding it to finishing a task to getting help. It covers flows, words and speed, not just screens. To say it: Is the problem how it looks, or how it works? If it’s how it works, I’d look at the flow first.</description>
    </item>
    <item>
      <title>Iteration</title>
      <link>https://designjargon.fyi/iteration</link>
      <guid isPermaLink="true">https://designjargon.fyi/iteration</guid>
      <pubDate>Mon, 02 Nov 2026 09:00:00 GMT</pubDate>
      <description>Improving a design in rounds: make a version, test or review it, learn, and make the next one. Each round gets closer instead of starting over. To say it: Can we treat this as round one? Let’s test it, keep what works, and change one thing at a time.</description>
    </item>
    <item>
      <title>Design brief</title>
      <link>https://designjargon.fyi/design-brief</link>
      <guid isPermaLink="true">https://designjargon.fyi/design-brief</guid>
      <pubDate>Mon, 02 Nov 2026 09:00:00 GMT</pubDate>
      <description>A short document that says what problem to solve, for whom, and what good looks like, before anyone designs anything. It describes the problem, not the solution. To say it: Before you start, let me write a short brief: the problem, who it’s for, and how we’ll know it worked.</description>
    </item>
    <item>
      <title>Design critique</title>
      <link>https://designjargon.fyi/design-critique</link>
      <guid isPermaLink="true">https://designjargon.fyi/design-critique</guid>
      <pubDate>Mon, 02 Nov 2026 09:00:00 GMT</pubDate>
      <description>A structured review where people judge a design against its goals, not their taste. Good critique names what works, what doesn't, and why. To say it: Can we frame the critique around the goal? What’s the one thing this screen needs to do?</description>
    </item>
    <item>
      <title>Persona</title>
      <link>https://designjargon.fyi/persona</link>
      <guid isPermaLink="true">https://designjargon.fyi/persona</guid>
      <pubDate>Mon, 02 Nov 2026 09:00:00 GMT</pubDate>
      <description>A short profile of a typical user, based on research: their goals, their context and what frustrates them. It gives the team one shared picture of who they design for. To say it: Do we have a persona for who this is for? It would help us agree on what matters most.</description>
    </item>
    <item>
      <title>Heuristic evaluation</title>
      <link>https://designjargon.fyi/heuristic-evaluation</link>
      <guid isPermaLink="true">https://designjargon.fyi/heuristic-evaluation</guid>
      <pubDate>Mon, 02 Nov 2026 09:00:00 GMT</pubDate>
      <description>An expert review of a design against a list of well-known usability rules, like &quot;people should always know where they are&quot;. Fast, cheap, and done without users. To say it: Could we do a quick heuristic review before the meeting, so we talk about specific problems, not taste?</description>
    </item>
    <item>
      <title>User interview</title>
      <link>https://designjargon.fyi/user-interview</link>
      <guid isPermaLink="true">https://designjargon.fyi/user-interview</guid>
      <pubDate>Mon, 02 Nov 2026 09:00:00 GMT</pubDate>
      <description>A one-on-one conversation to learn how someone works, what they need and what frustrates them. It's about their life, not your design. To say it: Could we interview a few customers about how they do this today, before we show them anything?</description>
    </item>
    <item>
      <title>Usability test</title>
      <link>https://designjargon.fyi/usability-test</link>
      <guid isPermaLink="true">https://designjargon.fyi/usability-test</guid>
      <pubDate>Mon, 02 Nov 2026 09:00:00 GMT</pubDate>
      <description>Watching real people try to do real tasks with your design, while they think aloud. Five people usually find most of the big problems. To say it: Before we decide, could we run a quick usability test with five people? I’d rather watch than guess.</description>
    </item>
    <item>
      <title>User flow</title>
      <link>https://designjargon.fyi/user-flow</link>
      <guid isPermaLink="true">https://designjargon.fyi/user-flow</guid>
      <pubDate>Mon, 02 Nov 2026 09:00:00 GMT</pubDate>
      <description>The path someone takes through a product to finish one task, step by step, from where they start to where they're done. To say it: Can we walk through the user flow for this task step by step? I think one or two steps could go.</description>
    </item>
    <item>
      <title>Variants and props</title>
      <link>https://designjargon.fyi/variants-and-props</link>
      <guid isPermaLink="true">https://designjargon.fyi/variants-and-props</guid>
      <description>One component in many versions, controlled by settings: size, style, state, icon. Designers and developers use the same names for them. To say it: We have several near-identical buttons. Can we make one component with variants, so design and code use the same names?</description>
    </item>
    <item>
      <title>Navigation patterns</title>
      <link>https://designjargon.fyi/navigation-patterns</link>
      <guid isPermaLink="true">https://designjargon.fyi/navigation-patterns</guid>
      <description>The standard ways to move around an app: top bar, sidebar, tabs, and a bottom bar on phones. Pick by how many places there are. To say it: Which navigation pattern fits the number of sections we have? I’d like it to stay consistent on phone and desktop.</description>
    </item>
    <item>
      <title>Aspect ratio</title>
      <link>https://designjargon.fyi/aspect-ratio</link>
      <guid isPermaLink="true">https://designjargon.fyi/aspect-ratio</guid>
      <description>The proportion of width to height, like 16:9 or 1:1. Fixing it keeps images and videos from stretching or squashing. To say it: The images look stretched. Can we set a fixed aspect ratio for the thumbnails and crop them to fit?</description>
    </item>
    <item>
      <title>Z-index and stacking</title>
      <link>https://designjargon.fyi/z-index-and-stacking</link>
      <guid isPermaLink="true">https://designjargon.fyi/z-index-and-stacking</guid>
      <description>The order in which overlapping things are layered. Higher z-index sits on top, but only within the same stacking context. To say it: The dropdown opens behind the card. Can we fix the stacking order so menus always appear on top?</description>
    </item>
    <item>
      <title>Sticky</title>
      <link>https://designjargon.fyi/sticky</link>
      <guid isPermaLink="true">https://designjargon.fyi/sticky</guid>
      <description>An element that scrolls normally until it reaches the top of its area, then sticks there. Perfect for headers and table headings. To say it: When I scroll this table, I lose the column names. Can we make the header sticky?</description>
    </item>
    <item>
      <title>Layout shift</title>
      <link>https://designjargon.fyi/layout-shift</link>
      <guid isPermaLink="true">https://designjargon.fyi/layout-shift</guid>
      <description>When content jumps around as the page loads, usually because an image or ad arrives late and pushes things down. To say it: The page jumps as it loads, and I’ve tapped the wrong thing because of it. Can we fix the layout shift?</description>
    </item>
    <item>
      <title>ARIA label</title>
      <link>https://designjargon.fyi/aria-label</link>
      <guid isPermaLink="true">https://designjargon.fyi/aria-label</guid>
      <description>A hidden text label that a screen reader announces. An icon-only button needs one, or it just says &quot;button&quot;. To say it: The icon-only buttons need names for screen readers. Can we add an ARIA label to each one?</description>
    </item>
  </channel>
</rss>
