Latest / The Feed & The Thread / The Feed & The Thread - October 2, 2026

Transcript

The Feed & The Thread - October 2, 2026 · The Feed & The Thread

• 0:00
  Designers are losing the right to decide what gets built. So
• 0:03
  who owns that authority now? The AI agents do, and they aren't
• 0:06
  reading your documentation.
• 0:12
  Welcome to The Feed and The Thread, brought to you by
• 0:14
  Chicago Camps. The Feed & The Thread is available online at
• 0:17
  feed and thread dot com to submit your feeds, or download
• 0:20
  our app for all the feeds and threads delivered right to your
• 0:22
  pocket.
• 0:30
  The tools we use to build products are changing, but the
• 0:33
  question of who holds the power to decide hasn't. We need to
• 0:36
  look closely at where authority sits in the design process right
• 0:39
  now. Stacie Sheldon at UX Design.cc asks the hard question
• 0:42
  in "In/tension modeling: what gives us the right?": what
• 0:45
  actually gives us the right to make decisions for others. The
• 0:49
  piece argues that empathy often masks an unchecked exercise of
• 0:52
  power, which can unintentionally cause harm. Sheldon proposes a
• 0:55
  framework for surfacing tension between conflicting user voices
• 0:59
  and reframing these conflicts as opportunities. This approach
• 1:02
  helps us stay with the discomfort instead of silencing
• 1:05
  minority perspectives to force a single solution. Luke
• 1:08
  Wroblewski at LukeW's blog tackles the maintenance burden
• 1:11
  in "Design Systems for AI Agents". He suggests using AI
• 1:13
  agents as a steering layer for front-end code, which enforces
• 1:17
  design tokens and brand guidelines automatically. This
• 1:19
  allows non-designers to update sites without breaking visual
• 1:23
  consistency, shifting the single source of truth from
• 1:25
  documentation to code. It solves the longstanding problem of
• 1:29
  design systems becoming outdated through human error. Anne
• 1:32
  Cantera at Chicago Camps outlines the new skill set in
• 1:35
  "The New Design Stack: The Skills Traditional Designers
• 1:37
  Need to Add To Their Toolboxes ASAP". She argues that screen-
• 1:41
  based design is no longer enough for a world of multimodal
• 1:44
  interfaces, including voice and chat. Designers must now
• 1:47
  orchestrate the right modality based on user context and
• 1:50
  cognitive load, rather than forcing interactions into a
• 1:53
  single visual format. This shift requires us to design for the
• 1:56
  moment, not just the screen. Other reads today include Deque
• 1:59
  Blog on testing MCP apps for accessibility, UX Planet on
• 2:02
  comparing Sonnet and Opus for design, and UX Design.cc on
• 2:05
  moving from chatting to collaborating with AI.
• 2:15
  A professor is telling students to hide their Asian identity to
• 2:18
  get hired, and a designer is pausing real history for user
• 2:21
  choice. Over on r/UXResearch, a junior researcher is exhausted
• 2:25
  after months of job hunting, asking where the gap lies in
• 2:28
  their candidacy. This solitary plea highlights a field that
• 2:31
  demands senior-level strategic insight from entry-level
• 2:34
  candidates, creating a catch-22 where you need experience to get
• 2:37
  experience. It's a structural failure in how we define junior
• 2:40
  work. In r/UI_Design, someone is asking how many designers
• 2:44
  actually work on a site like Apple's, wondering if it's one
• 2:47
  centralized team or distributed product teams. The answer is
• 2:50
  likely a hybrid, but the question reveals a deeper
• 2:53
  anxiety about who holds authority in a design system.
• 2:56
  When a single brand voice dominates, the tension between
• 2:59
  local context and global consistency becomes a power
• 3:01
  struggle that designers must navigate daily. Back in
• 3:04
  r/UXResearch, a cognitive science grad from Bangalore is
• 3:07
  seeking a transition into UX, worried their sports cognition
• 3:10
  background isn't enough. This is a valid concern, but it also
• 3:14
  signals a shift where domain expertise in human behavior is
• 3:17
  becoming more valuable than generic UX portfolios. The field
• 3:20
  is hungry for people who understand the "why" behind user
• 3:23
  actions, not just the "what." In r/UI_Design, a designer
• 3:26
  shared a project called Moralia, a game that pauses history for
• 3:29
  user choice, using distinct visual identities for moral
• 3:32
  houses. The explicit disclosure of AI use for development and
• 3:36
  narration is notable, positioning the tool as a
• 3:38
  partner rather than a replacement. It's a clear
• 3:41
  statement that the designer retains the creative authority,
• 3:44
  even when the code is generated. Finally, in r/Design, a student
• 3:47
  is pushing back on their professor's advice to hide their
• 3:50
  Asian identity in portfolios, arguing it's outdated and
• 3:53
  harmful. This is a direct challenge to gatekeeping
• 3:56
  mechanisms that have persisted in hiring for decades. The
• 3:59
  student is right to question it, because transparency and
• 4:02
  identity should be assets, not liabilities, in a diverse field.
• 4:06
  The common thread is authority. Who decides what gets hired,
• 4:09
  what gets built, and who gets to speak? The tools are changing,
• 4:12
  but the power structures aren't, and that's where the real
• 4:15
  friction lives.
• 4:23
  The Feed and The Thread is brought to you by Chicago Camps.
• 4:26
  For a weekly and monthly exploration of the patterns and
• 4:29
  signals across UX, you can also check out Patterns and Signals
• 4:32
  at the website patterns and signals dot com. Chicago Camps
• 4:35
  will have more events in 2027. You can submit to be a speaker
• 4:38
  at a future event at Chicago Camps dot org.
• 4:47
  Stacie Sheldon's piece on "In/tension modeling" asks a
• 4:50
  question that usually gets skipped in design reviews. She
• 4:52
  argues that empathy often masks an unchecked exercise of power.
• 4:55
  We decide what the product does, and we label that decision as
• 4:58
  caring for the user. That framing hits hard because it's
• 5:01
  so common. We see conflicting user needs and our instinct is
• 5:04
  to smooth it out. We pick the louder voice, or the one that
• 5:06
  fits our roadmap, and call it a solution. Sheldon says we're
• 5:09
  silencing minority perspectives just to force a single, clean
• 5:12
  path forward. Exactly. And that's where the "design system"
• 5:15
  conversation from Luke Wroblewski starts to look like a
• 5:17
  workaround. If we're using AI agents to enforce brand
• 5:20
  guidelines automatically, we're removing the human decision-
• 5:23
  maker from the loop. We're letting the code decide what is
• 5:25
  "consistent." That feels safe, but it might just be hiding the
• 5:28
  tension we're supposed to be resolving. I don't think it
• 5:31
  hides it. I think it forces us to be more honest about the
• 5:34
  conflict. If the system can't reconcile two opposing user
• 5:36
  needs, it doesn't just pick one. It surfaces the break. That's
• 5:39
  actually a feature. It stops us from pretending a compromise
• 5:42
  exists when it doesn't. So you're saying the rigidity of
• 5:45
  the system is a better ethical check than human empathy? No,
• 5:48
  I'm saying human empathy is too easy to use as a shield. When we
• 5:51
  say "I'm doing this for the user," it's hard to argue with
• 5:53
  that. But when the constraint is structural, when the design
• 5:56
  system literally can't support the feature, the conversation
• 5:59
  shifts from "who is right" to "what are we willing to change."
• 6:02
  That's a harder, better question. That's a shift from
• 6:04
  moral authority to structural constraint. Yes. And it's where
• 6:07
  the real work happens. Not in smoothing over the conflict, but
• 6:10
  in designing the system to hold it. So the goal isn't to
• 6:13
  eliminate the tension. It's to build the capacity to hold it
• 6:16
  without breaking.
• 6:18
  That's The Feed and The Thread for today. We'll catch you next
• 6:22
  time!