<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>John Reese — Design Leadership &amp; AI</title>
    <link>https://jreese.com</link>
    <atom:link href="https://jreese.com/feed.xml" rel="self" type="application/rss+xml"/>
    <description>Thinking on design leadership, AI-augmented workflows, and building design orgs at scale. By John Reese — 15 years leading UX at Walmart, Home Depot, and beyond.</description>
    <language>en-us</language>
    <managingEditor>Reese@jreese.com (John Reese)</managingEditor>
    <webMaster>Reese@jreese.com (John Reese)</webMaster>
    <copyright>Copyright 2026 John Reese</copyright>
    <ttl>2880</ttl>
    <image>
      <url>https://jreese.com/favicon.svg</url>
      <title>John Reese</title>
      <link>https://jreese.com</link>
    </image>

    <item>
      <title>Design Systems in the AI Era</title>
      <link>https://jreese.com/thinking/design-systems-ai</link>
      <guid isPermaLink="true">https://jreese.com/thinking/design-systems-ai</guid>
      <description>Nearly two decades of design systems, from building Amazon's form patterns in 2008 to Walmart's first enterprise design system and Home Depot's unified B2C system. Token architecture, ADA compliance, content strategy, and teaching your design system to AI.</description>
      <content:encoded><![CDATA[
        <p>My first design system work was at Amazon in 2008, building form patterns that did not exist yet. Since then I have built Walmart's first enterprise design system, unified Home Depot's B2C system, and contributed at Dell and PayPal. The discipline that made products consistent at scale is about to become something bigger. It is becoming the layer that teaches AI how to design.</p>
        <p>Tokens are the contract. Accessibility is a system property, not a review step. Content strategy belongs in the system. And an AI can generate a thousand screens an hour, but your design system decides whether any of them are yours.</p>
        <p>Read the full article at <a href="https://jreese.com/thinking/design-systems-ai">jreese.com/thinking/design-systems-ai</a></p>
      ]]></content:encoded>
      <category>Design Systems</category>
      <author>Reese@jreese.com (John Reese)</author>
    </item>

    <item>
      <title>How AI Compresses the Design Workflow</title>
      <link>https://jreese.com/thinking/ai-design-process</link>
      <guid isPermaLink="true">https://jreese.com/thinking/ai-design-process</guid>
      <description>Discovery transcripts to an interactive prototype in five or ten minutes, with no wireframes. The PRD, developer handoff, and QA test script all come out of the prototype afterward.</description>
      <content:encoded><![CDATA[
        <p>Record discovery. Run it through Claude. Ship an interactive prototype in five or ten minutes. Here's the exact workflow.</p>
        <p>The paperwork moves to the end. Instead of writing a PRD before anyone has seen the product, the prototype comes first and Claude generates the PRD, the developer handoff, and the QA test script from the working code.</p>
        <p>The step most design teams skip: partnering with engineering to train Claude on their design tokens and code conventions, so what you hand off is genuinely buildable rather than a screenshot they have to rebuild.</p>
        <p>Faster does not mean smaller. Work that took a week in Figma takes five or ten minutes in Claude, but the judgment still has to come from you.</p>
        <p>Read the full article at <a href="https://jreese.com/thinking/ai-design-process">jreese.com/thinking/ai-design-process</a></p>
      ]]></content:encoded>
      <category>AI + Design</category>
      <author>Reese@jreese.com (John Reese)</author>
    </item>

    <item>
      <title>The Power of Northstar Design</title>
      <link>https://jreese.com/thinking/northstar-design</link>
      <guid isPermaLink="true">https://jreese.com/thinking/northstar-design</guid>
      <description>What Northstar designs are, why they create org-wide alignment, and how to use them to earn executive buy-in — even before a single line of code is written.</description>
      <content:encoded><![CDATA[
        <p>What Northstar designs are, why they create org-wide alignment, and how to use them to earn executive buy-in.</p>
        <p>A Northstar isn't a prototype. It isn't a concept. It's a shared language — a picture of the future that every team, every executive, and every engineer can point to.</p>
        <p>Read the full article at <a href="https://jreese.com/thinking/northstar-design">jreese.com/thinking/northstar-design</a></p>
      ]]></content:encoded>
      <category>Strategy</category>
      <author>Reese@jreese.com (John Reese)</author>
    </item>

    <item>
      <title>What Makes a Great Design Leader</title>
      <link>https://jreese.com/thinking/great-design-leader</link>
      <guid isPermaLink="true">https://jreese.com/thinking/great-design-leader</guid>
      <description>Four pillars built from 15 years of leadership: Define Success, Build Culture, Elevate Craft, Develop Skills. What separates design leaders who scale from those who plateau.</description>
      <content:encoded><![CDATA[
        <p>Four pillars built from 15 years of leadership: Define Success, Build Culture, Elevate Craft, Develop Skills.</p>
        <p>Great design leadership isn't about being the best designer in the room. It's about making everyone else better — and building the conditions where great work is inevitable.</p>
        <p>Read the full article at <a href="https://jreese.com/thinking/great-design-leader">jreese.com/thinking/great-design-leader</a></p>
      ]]></content:encoded>
      <category>Leadership</category>
      <author>Reese@jreese.com (John Reese)</author>
    </item>

  </channel>
</rss>
