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

Transcript

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

• 0:00
  The agent woke up before you did. So the human is no longer
• 0:03
  the center. That breaks the core assumption of user-centered
• 0:06
  design entirely.
• 0:11
  Welcome to The Feed and The Thread, brought to you by
• 0:14
  Chicago Camps. The Feed & The Thread is available online at
• 0:16
  feed and thread dot com to submit your feeds, or download
• 0:19
  our app for all the feeds and threads delivered right to your
• 0:22
  pocket.
• 0:29
  The core assumption of user- centered design is breaking. We
• 0:33
  used to build interfaces where the user held the wheel, but now
• 0:36
  the system is anticipating our needs before we even ask. That
• 0:39
  shift changes who's in control of the interaction. Adrian Levy
• 0:43
  at UX Design.cc tackles this in "The agent woke up before you
• 0:46
  did", arguing that AI agents are becoming proactive actors rather
• 0:50
  than passive tools. Four major companies have pushed this
• 0:53
  boundary, creating a paradigm where the system drives the
• 0:56
  flow. Designers can no longer assume the user is the sole
• 0:59
  driver. We must now account for agent behavior and intent in our
• 1:03
  research. Claude Liu and Chris Chen at ACM Interactions examine
• 1:06
  the emotional cost of digital permanence in "The Feeling
• 1:10
  Machine: Paying to Be Remembered". They describe a
• 1:12
  trend where users pay AI to curate their memories, creating
• 1:16
  a constructed identity rather than raw data. This raises hard
• 1:19
  questions about ownership and the commodification of selfhood.
• 1:22
  The risk is a distorted past, filtered by algorithms that
• 1:26
  prioritize what they think matters over what actually
• 1:28
  happened. Christine Vallaure at UX Design.cc proposes a workflow
• 1:32
  inversion in "Building an AI- ready design system library:
• 1:35
  Code → Figma with MCP.". She argues that traditional Figma-
• 1:39
  to-code processes fail because design files hide critical
• 1:42
  details like focus order and error states. When AI translates
• 1:45
  these incomplete files, it invents plausible but flawed
• 1:48
  behaviors. Starting with code as the source of truth ensures the
• 1:52
  design mirrors reality. This prevents shipping interfaces
• 1:55
  that look correct but function poorly. Other reads available
• 1:58
  today from ACM Interactions on an ethical framework for AI and
• 2:02
  UX Design.cc on design leadership in smaller teams.
• 2:12
  A nineteen year old in Sri Lanka is fighting the urge to hoard
• 2:15
  design inspiration, while a product designer spent three
• 2:18
  years building a golf putter and a testing rig to validate it.
• 2:21
  One is asking if AI is eroding the boundary between design and
• 2:24
  product management, and another is wondering if career services
• 2:28
  actually work outside the United States. Over on
• 2:30
  r/ProductDesign, a young developer describes the
• 2:33
  graveyard of saved references that never turn into work. They
• 2:36
  launched a tool to link those references directly to specific
• 2:39
  design decisions, aiming to bridge the gap between passive
• 2:42
  collection and active execution. The tension here is real,
• 2:45
  because saving an image feels productive, but it often
• 2:48
  replaces the actual cognitive work of making a choice. This is
• 2:51
  less about the tool and more about the discipline required to
• 2:54
  move from looking to building. In r/ProductDesign, a designer
• 2:57
  shares the journey of prototyping a modular CNC milled
• 3:00
  golf putter over three years. They built an automated testing
• 3:03
  rig to verify that the mechanical interface between the
• 3:06
  aluminum and stainless steel parts feels solid and premium.
• 3:09
  It's a reminder that digital interfaces are just one layer of
• 3:13
  the experience, and that physical constraints, material
• 3:15
  properties, and tactile feedback still demand rigorous, hands on
• 3:19
  validation that no software can fully simulate. Over on
• 3:22
  r/UXDesign, a designer facing a team cut is asking if the shift
• 3:25
  to Product Manager is a temporary survival tactic or a
• 3:28
  permanent industry trend. The blurring of lines, accelerated
• 3:31
  by AI tools that can generate prototypes and documentation, is
• 3:34
  forcing a hard look at where the designer's unique value actually
• 3:37
  sits. If the system can anticipate the need and draft
• 3:40
  the solution, the designer's role shifts from creating the
• 3:43
  interface to curating the intent and defining the constraints
• 3:46
  that the machine can't guess. In r/UXDesign, a graphic
• 3:49
  designer turning team lead is unsure how to prioritize skills
• 3:52
  when AI tools like Claude are bypassing traditional Figma
• 3:55
  workflows. The uncertainty isn't about the tools themselves, but
• 3:59
  about what happens to the craft when the execution layer is
• 4:02
  automated. The core question is whether the designer's value now
• 4:05
  lies in the strategic judgment of what to build, rather than
• 4:08
  the manual skill of how to build it. The common thread is a
• 4:11
  field that's no longer just designing screens, but
• 4:14
  negotiating control with systems that anticipate, automate, and
• 4:17
  often blur the line between the creator and the tool.
• 4:27
  The Feed and The Thread is brought to you by Chicago Camps.
• 4:30
  For a weekly and monthly exploration of the patterns and
• 4:33
  signals across UX, you can also check out Patterns and Signals
• 4:36
  at the website patterns and signals dot com. Chicago Camps
• 4:39
  will have more events in 2027. You can submit to be a speaker
• 4:42
  at a future event at Chicago Camps dot org.
• 4:52
  There is a specific failure mode in today's feed that worries me,
• 4:55
  specifically in Vallaure's argument about code-first design
• 4:57
  systems. The claim is that Figma files hide critical details like
• 5:00
  focus order, and when AI translates them, it invents
• 5:03
  plausible but flawed behaviors. I think this is a structural lie
• 5:06
  we're telling ourselves about what a design file actually
• 5:09
  contains. I hear the frustration, but I think we're
• 5:11
  misidentifying the problem. The issue is that we stopped
• 5:14
  validating the output. Look at the r/ProductDesign thread where
• 5:17
  someone spent three years building a CNC milled golf
• 5:19
  putter. They didn't rely on a simulation to tell them if the
• 5:22
  metal felt premium. They built a rig to test the tactile
• 5:24
  feedback. Digital designers are losing that instinct. We're
• 5:27
  trusting the software to be the source of truth instead of
• 5:30
  testing the behavior against reality. That's a strong
• 5:32
  counter, but it ignores the scale of the shift Levy
• 5:35
  describes in "The agent woke up before you did." We're no longer
• 5:38
  just designing for a human who clicks a button. We're designing
• 5:41
  for an agent that anticipates intent. If the agent is driving
• 5:44
  the flow, your manual validation of a static state is useless.
• 5:47
  You need to model the agent's decision tree. If the underlying
• 5:49
  code doesn't explicitly define the error states, the agent will
• 5:52
  hallucinate a path. That isn't a tool failure, that's a data
• 5:55
  failure. But that's exactly where the craft is going to
• 5:58
  live. Not in the file, but in the negotiation. The community
• 6:01
  in r/UXDesign is asking how to prioritize skills when AI
• 6:03
  bypasses the traditional workflow. The answer is to learn
• 6:06
  to interrogate the system harder. We treat the interface
• 6:09
  as a hypothesis. The skill is proving it behaves right. I
• 6:11
  think that's the right pivot. We need to move our rigor from the
• 6:14
  creation phase to the verification phase. If we can
• 6:17
  define the behavioral boundaries of the agent as clearly as that
• 6:20
  putter designer defined the mechanical tolerance, we stop
• 6:22
  shipping interfaces that look correct but function poorly.
• 6:25
  The design file is just the sketch. The value is in the
• 6:28
  evidence that the system works. We have to build the test rig
• 6:30
  for the digital world.
• 6:33
  That's The Feed and The Thread for today. We'll catch you next
• 6:37
  time!