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

Transcript

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

• 0:00
  Anthropic and OpenAI are building software factories that
• 0:03
  sideline user experience entirely. So we're designing for
• 0:06
  the machine, not the human? Exactly. And the industry is
• 0:09
  asking if we've started training people to adapt to AI instead.
• 0:17
  Welcome to The Feed and The Thread, brought to you by
• 0:19
  Chicago Camps. The Feed & The Thread is available online at
• 0:22
  feed and thread dot com to submit your feeds, or download
• 0:24
  our app for all the feeds and threads delivered right to your
• 0:27
  pocket.
• 0:35
  The big tech companies are rewriting the software lifecycle
• 0:38
  to let AI do the heavy lifting, and in doing so, they're quietly
• 0:41
  erasing the role of human judgment. We're building systems
• 0:45
  that are faster, yet they're losing the very context that
• 0:48
  makes them useful. Tanner Kohler at Nielsen Norman Group
• 0:51
  argues in "The Role of UX in Agentic Software Factories" that
• 0:54
  reducing UX to mere context for AI generation is a dangerous
• 0:57
  mistake. This view ignores the critical work of discovering
• 1:00
  user needs and shaping team consensus on what to build. By
• 1:04
  sidelining these core responsibilities, organizations
• 1:06
  risk losing the user insight their AI systems depend on. The
• 1:10
  curators at Rosenfeld Media reflect on the first Shift UX
• 1:13
  conference in "Let’s recap: Our curators reflect on the first-
• 1:16
  ever Shift UX conference", noting a consensus that the
• 1:19
  industry must move beyond industrial production models.
• 1:22
  They argue that UX education needs a fundamental reset,
• 1:25
  emphasizing that identity alone won't solve current challenges.
• 1:29
  The narrative of AI's impact is too narrowly focused on
• 1:32
  designers, ignoring the collective responsibility of
• 1:34
  strategists and product managers. Nick Babich at UX
• 1:37
  Planet identifies eight common mistakes in "Claude 5.5 Model
• 1:40
  Mistakes You’re Still Making" that users still make with the
• 1:44
  Claude 5.5 model. Many fail to leverage the model's full
• 1:47
  potential due to outdated prompting habits or vague
• 1:49
  instructions. Providing sufficient context and utilizing
• 1:52
  its complex reasoning abilities are key to optimizing workflows.
• 1:56
  Other reads available from UX Design.cc on AI strategy and
• 1:59
  Nielsen Norman Group on dropping the "User" from "User
• 2:02
  Experience."
• 2:10
  The question is whether we're designing for humans or training
• 2:13
  them to fit machine logic, and the tension shows up in how we
• 2:16
  handle AI transparency. Over on r/HCI, someone asked if we're
• 2:20
  slowly erasing user autonomy in favor of convenience. The core
• 2:23
  issue is that auto-complete and recommendations make life
• 2:26
  easier, but they also reduce the user's active role in the
• 2:29
  decision. This matters because if we optimize for speed without
• 2:32
  preserving agency, we build systems that feel efficient but
• 2:35
  lack the context that makes them truly useful. In r/UI_Design, a
• 2:39
  startup founder is stuck on how to show trust when an AI
• 2:42
  aggregates ticket prices. They want to differentiate from
• 2:45
  traditional sites, but the standard loading bar feels like
• 2:48
  a black box. The challenge here is making the AI process feel
• 2:51
  transparent rather than magical. If the user doesn't understand
• 2:54
  how the price was calculated, the speed of the search doesn't
• 2:57
  matter as much as the confidence in the result. Over on
• 3:00
  r/ProductDesign, a student is imagining a modern revival of
• 3:03
  Blockbuster, focusing on physical rentals and community
• 3:06
  features. It's a thoughtful exercise in balancing nostalgia
• 3:09
  with modern expectations. Even with AI, the human desire for
• 3:13
  tangible, shared experiences remains a powerful design anchor
• 3:16
  that pure digital efficiency often overlooks. Today's
• 3:19
  threads all point to one thing: we need to bring human judgment
• 3:22
  back into the loop, or we risk building tools that are fast but
• 3:25
  fundamentally disconnected from the people using them.
• 3:35
  The Feed and The Thread is brought to you by Chicago Camps.
• 3:38
  For a weekly and monthly exploration of the patterns and
• 3:41
  signals across UX, you can also check out Patterns and Signals
• 3:44
  at the website patterns and signals dot com. Chicago Camps
• 3:47
  will have more events in 2027. You can submit to be a speaker
• 3:50
  at a future event at Chicago Camps dot org.
• 4:00
  The thing that stuck with me today is Tanner Kohler's
• 4:02
  argument that treating UX as just context for AI generation
• 4:05
  is a dangerous mistake. He's pointing out that we're building
• 4:08
  faster systems, but we're losing the specific context that makes
• 4:11
  them actually useful to a person. I hear you, but I think
• 4:14
  we're looking at this the wrong way. It's not that we're losing
• 4:17
  context, it's that we're outsourcing the discovery of
• 4:19
  that context to the machine. The community on r/HCI is asking if
• 4:22
  we're erasing user autonomy, and I think the answer is yes. We're
• 4:26
  optimizing for speed, which feels efficient, but it strips
• 4:28
  away the user's active role in the decision. That's a fair
• 4:31
  point, but look at the systemic angle here. The big tech
• 4:34
  companies are rewriting the software lifecycle to let AI do
• 4:37
  the heavy lifting. They're not just removing a step; they're
• 4:39
  erasing the role of human judgment entirely. If we accept
• 4:42
  that the machine knows best, we stop asking the right questions
• 4:45
  in the first place. But that's exactly where I'd push back. We
• 4:48
  don't need to be the ones asking every question. We need to be
• 4:51
  the ones defining the boundaries. The Blockbuster
• 4:53
  revival idea on r/ProductDesign is a perfect example. People
• 4:56
  want tangible, shared experiences. That's a human
• 4:59
  desire that pure digital efficiency overlooks. We need to
• 5:01
  design for that human anchor, not just let the AI fill in the
• 5:04
  blanks. So we're saying the human's job is to set the
• 5:07
  constraints? No, I'm saying the human's job is to recognize when
• 5:10
  the machine is wrong. The machine is great at pattern
• 5:12
  matching, but it's terrible at understanding why a user
• 5:15
  hesitates. That hesitation holds the insight. We need to bring
• 5:18
  that judgment back into the loop, not just as a check, but
• 5:21
  as the primary driver of the design. That's a strong stance.
• 5:24
  And it's the only one that works. If we don't hold that
• 5:26
  line, we're just training humans to fit machine logic, and that's
• 5:29
  a design failure.
• 5:32
  That's The Feed and The Thread for today. We'll catch you next
• 5:35
  time!