Latest / The Feed & The Thread / The Feed & The Thread - September 5, 2026

Transcript

The Feed & The Thread - September 5, 2026 · The Feed & The Thread

• 0:00
  Reading and writing are actually interfaces. That shifts the
• 0:03
  whole frame. If we treat them as systems, AI stops being a
• 0:06
  ghostwriter and becomes a friction reducer for meaning.
• 0:09
  Let's see how that changes your process.
• 0:15
  Welcome to The Feed and The Thread, brought to you by
• 0:18
  Chicago Camps. Leadership By Design is on Thursday and
• 0:20
  Friday, September 17 and 18 and tickets are available now! And
• 0:23
  while you're at it, get caught up on UX fundamentals with five
• 0:26
  minute UX at five em UX dot com. The Feed & The Thread is
• 0:29
  available online at feed and thread dot com to submit your
• 0:32
  feeds, or download our app for all the feeds and threads
• 0:34
  delivered right to your pocket.
• 0:43
  We treat AI as a generator, but the real shift is using it as a
• 0:47
  critic. That changes how we validate work. Tanner Kohler at
• 0:50
  Nielsen Norman Group frames this in "Using AI for UX Work: Study
• 0:54
  Guide": treat AI as assistive tech that boosts productivity,
• 0:58
  not a replacement for human expertise. We need to stop
• 1:01
  asking if it replaces us and start asking how it handles the
• 1:04
  grunt work so we can focus on strategy. It's about efficiency,
• 1:08
  not autonomy. Michael Buckley at UX Design.cc argues in
• 1:11
  "Reading and writing are interfaces. And AI can reduce
• 1:14
  their friction." that reading and writing are interfaces, and
• 1:18
  AI reduces incidental friction without killing intellectual
• 1:21
  value. He distinguishes between constitutive friction, which
• 1:24
  builds capacity, and incidental friction, which just wastes
• 1:28
  time. If we equate manual difficulty with intelligence, we
• 1:31
  lose the benefit of smoother interaction. Nick Babich shows
• 1:35
  how to use Claude Code in "Figma Design Critique Using Claude
• 1:38
  Code" to critique Figma designs by finding structural
• 1:41
  inconsistencies in a finance app. He intentionally omits
• 1:44
  design system components to force the AI to spot balance and
• 1:48
  hierarchy issues. This turns the tool from a creator into a
• 1:51
  reviewer that catches what we miss. Other articles today from
• 1:55
  Codrops on Three.js speakers, UX Design.cc on user motivation
• 1:58
  problems, and UX Design.cc on growth environments.
• 2:09
  Designers are shifting their focus from generating output to
• 2:12
  validating decisions. Over on r/ProductDesign, a discussion
• 2:15
  asks what happens when AI removes the friction of building
• 2:18
  anything. The core argument is that execution is becoming a
• 2:21
  commodity, so the real differentiator shifts to
• 2:23
  strategic judgment. We're no longer asking how to build a
• 2:26
  feature, but whether we should build it at all. This matters
• 2:29
  because it suggests that critical thinking, not just UI
• 2:32
  skills, is the new moat. In r/DesignSystems, practitioners
• 2:35
  are noticing a strange market shift. Recruiters are actively
• 2:39
  hunting for mid-level experts to set up machine-ready design
• 2:42
  systems. The demand isn't just for component libraries, but for
• 2:45
  workflows that AI tools can actually read and use. It turns
• 2:48
  out that designing for humans is no longer enough, you now have
• 2:51
  to design for the machines that'll generate the interfaces.
• 2:54
  Over on r/web_design, a team shared how they built a mobile
• 2:57
  game landing page using Claude for both design direction and
• 3:01
  code implementation. They paired it with Kling AI for video
• 3:04
  assets to test how far a small team can push production
• 3:07
  quality. It's a practical experiment in leveraging AI as a
• 3:10
  co-pilot for speed, but it also highlights the risk of losing
• 3:13
  that human editorial eye in the process. In r/UserExperience,
• 3:16
  someone raised a tricky privacy question about deleting user
• 3:19
  history. If a user wipes their visible activity, should the
• 3:22
  system also erase the personalization data derived
• 3:25
  from it? There's a tension between respecting user agency
• 3:28
  and maintaining the context needed for good recommendations.
• 3:31
  It's a classic UX dilemma, but now it involves AI memory, which
• 3:34
  makes the stakes feel higher. Today's conversations show that
• 3:37
  we're moving past the novelty of AI generation. We're starting to
• 3:41
  wrestle with the harder questions of strategy, ethics,
• 3:44
  and system architecture.
• 3:52
  Chicago Camps is hosting Leadership By Design on Thursday
• 3:55
  & Friday, September 17 & 18. It's an online event, so you can
• 3:58
  join from anywhere in the world! Tickets are free, thanks to the
• 4:01
  generosity of the community! If it's within your budget, you can
• 4:04
  purchase a general admission ticket for only twenty six
• 4:07
  dollars - with limited early bird tickets at only fifteen
• 4:09
  dollars. Get tickets now at Chicago Camps dot org.
• 4:19
  Buckley's distinction between constitutive and incidental
• 4:22
  friction changes the frame entirely. If AI removes the
• 4:24
  tedious parts of writing and coding, we aren't losing
• 4:26
  intellectual value, we're just stopping the waste of time on
• 4:29
  tasks that don't build capacity. The real danger isn't that AI
• 4:32
  does the work, it's that we mistake the manual effort of the
• 4:34
  past for the intelligence of the present. That's a clean theory,
• 4:37
  but look at what recruiters are actually asking for in
• 4:40
  r/DesignSystems right now. They aren't just looking for people
• 4:43
  who can remove friction, they're hunting for mid-level experts
• 4:45
  who can build machine-ready design systems. The market is
• 4:48
  shifting because designing for humans isn't enough anymore. You
• 4:51
  have to design for the machines that'll read and generate those
• 4:53
  interfaces. Which brings us back to Babich's point about
• 4:56
  using Claude as a critic rather than a creator. If your design
• 4:59
  system can't explain its own structure to an AI, it's not a
• 5:01
  system, it's just a library of components. The shift isn't
• 5:04
  about speed, it's about clarity. If you can't articulate the
• 5:07
  hierarchy clearly enough for a machine to critique it, you
• 5:09
  probably haven't thought through the hierarchy for the user
• 5:12
  either. I see it differently. The thread on r/web_design
• 5:14
  showed a small team using AI for both direction and code, and
• 5:17
  while it was fast, it highlighted a real risk in
• 5:19
  losing the human editorial eye. Efficiency is great, but if the
• 5:22
  output is just structurally sound without strategic intent,
• 5:25
  we've solved the wrong problem. We need to stop asking if AI
• 5:27
  replaces us and start asking if our current workflows actually
• 5:30
  value judgment over output. So the metric for success changes.
• 5:33
  It's no longer about how many screens you ship. Exactly. It's
• 5:36
  about whether the organization treats that judgment as a
• 5:38
  deliverable worth paying for, or just something senior people do
• 5:41
  for free while the AI handles the grunt work.
• 5:45
  That's The Feed and The Thread for today. We'll catch you next
• 5:48
  time!