Latest / The Feed & The Thread / The Feed & The Thread - May 4, 2026

Transcript

The Feed & The Thread - May 4, 2026 · The Feed & The Thread

• 0:00
  We can't search our own AI chat histories. That's a structural
• 0:03
  flaw, not a bug. And the industry keeps building
• 0:06
  knowledge bases on messaging app architecture. We need to fix
• 0:09
  this.
• 0:14
  Welcome to The Feed and The Thread, brought to you by
• 0:16
  Chicago Camps. Leadership By Design is on Thursday and
• 0:19
  Friday, September 17 and 18 and tickets are available now! And
• 0:22
  while you're at it, get caught up on UX fundamentals with five
• 0:25
  minute UX at five emm UX dot com. The Feed & The Thread is
• 0:28
  available online at feed and thread dot com to submit your
• 0:30
  feeds, or download our app for all the feeds and threads
• 0:33
  delivered right to your pocket.
• 0:42
  We built tools to connect us, yet we feel more isolated than
• 0:45
  ever. The real friction isn't speed. It's the erosion of trust
• 0:49
  in every interaction. Dating apps are failing because they
• 0:52
  prioritize efficiency over authenticity. Catherine Chu at
• 0:55
  UX Design.cc explores this tension in "Can AI make your
• 0:58
  dating life better?". She notes that despite heavy investment in
• 1:02
  AI coaching features, user skepticism remains high. Only
• 1:05
  fifteen percent believe these tools lead to success. The core
• 1:09
  issue isn't a lack of options. It's the fear that AI-generated
• 1:12
  interactions feel dishonest. We're trading genuine connection
• 1:16
  for algorithmic convenience. Automation often sacrifices the
• 1:19
  nuance that defines quality design. Akaru makes this case at
• 1:23
  Codrops in "Akaru: Crafting Precision-Driven Digital
• 1:25
  Experiences". The article argues for precision-driven experiences
• 1:29
  over generic templates. While automation offers speed, it
• 1:32
  rarely delivers the intentional craftsmanship users actually
• 1:36
  value. This challenges the industry's push for scalable,
• 1:39
  algorithmic solutions. True excellence requires human-led
• 1:42
  design, not just efficient output. AI chat histories are
• 1:45
  structurally broken because we treat them like messaging apps.
• 1:49
  Adi Leviim points this out at UX Design.cc in "The forgotten
• 1:52
  conversation problem in AI chat". Current platforms index
• 1:56
  only titles, ignoring the valuable content buried in
• 1:59
  dialogue. Users lose critical insights because auto-generated
• 2:02
  summaries rarely reflect the true subject matter. This isn't
• 2:05
  a bug. It's a fundamental design flaw in how we handle knowledge
• 2:09
  work. Other reads today include Jeff Gothelf on habits that beat
• 2:13
  tool fluency, LukeW on the death of the handoff, and Rosenfeld
• 2:16
  Media on why designers are leaving tech.
• 2:26
  What's happening in the community today. Over on
• 2:29
  r/UXDesign, a designer is wrestling with the fear that
• 2:32
  simplicity looks like laziness. They describe a pattern where
• 2:35
  initial clarity gets buried under edge cases and feedback.
• 2:38
  One commenter put it well: go back to the job to be done
• 2:41
  before adding anything. If the new complexity doesn't serve
• 2:45
  that core goal, it's just overthinking. The real friction
• 2:48
  here isn't technical. It's the erosion of trust in your own
• 2:51
  instincts when stakeholders demand more. Also in
• 2:54
  r/UXDesign, people are frustrated by using PowerPoint
• 2:57
  for customer journey maps. The static layouts and formatting
• 3:00
  struggles steal time from actual strategy. Someone mentioned
• 3:04
  switching to Miro for its infinite canvas. This connects
• 3:07
  to our theme. When tools fight us, we lose trust in the
• 3:10
  process. We start blaming the medium instead of solving the
• 3:13
  user problem. In r/UXResearch, a psychology student is asking
• 3:17
  how to build a portfolio without real client work. They're unsure
• 3:20
  whether hypothetical case studies hold weight. This
• 3:23
  reveals a gap in our industry. We demand proof of competence
• 3:27
  but often block the path to getting it. The tension is
• 3:30
  between academic rigor and practical application. Back in
• 3:33
  r/UXDesign, a leader is pushing back against a CTO's push for
• 3:36
  probabilistic, AI-native design systems. They argue that shared
• 3:40
  components are essential for accessibility and preventing
• 3:43
  drift. The community is skeptical. If trust in
• 3:46
  interactions is already eroding, introducing randomness into the
• 3:49
  core UI feels risky. Deterministic systems offer
• 3:52
  stability. Probabilistic ones offer uncertainty. We're
• 3:55
  building tools to connect us, yet we feel more isolated. The
• 3:58
  real issue is trust in every interaction.
• 4:08
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:11
  & Friday, September 17 & 18. It's an online event, so you can
• 4:14
  join from anywhere in the world! Tickets are free, thanks to the
• 4:17
  generosity of the community! If it's within your budget, you can
• 4:20
  purchase a general admission ticket for only twenty six
• 4:22
  dollars - with limited early bird tickets at only fifteen
• 4:25
  dollars. Get tickets now at Chicago Camps dot org.
• 4:35
  We treat chat histories like messaging apps. Adi Leviim calls
• 4:38
  it a structural flaw. We index titles, but we ignore the actual
• 4:42
  dialogue. That means we lose the context where the real work
• 4:45
  happens. It's worse than losing context. It's about trust. On
• 4:48
  r/UXDesign, people are terrified that simplicity looks like
• 4:51
  laziness. When you bury insights in auto-generated summaries, you
• 4:55
  kill that trust. Stakeholders stop believing the surface
• 4:58
  level. Exactly. The summary becomes the artifact. And
• 5:00
  summaries are often wrong. They flatten nuance. So we get
• 5:03
  efficient output, but we lose intentional craftsmanship. We're
• 5:07
  optimizing for speed, not for understanding. But here's the
• 5:10
  tension. The community is pushing back against
• 5:12
  probabilistic design systems too. They want deterministic
• 5:15
  stability. Yet we're asking humans to hold complexity that
• 5:18
  the tools can't even index. That's a disconnect. It is.
• 5:21
  We're demanding human-led design while building systems that
• 5:25
  discard human context. The tool fluency is beating the habit of
• 5:28
  thinking. We need to stop treating the interface as the
• 5:31
  destination. The gap isn't in the code. It's in how we value
• 5:34
  the process. Right. If the system can't explain its own
• 5:37
  decisions, it's not a system. It's just noise. And we need to
• 5:40
  start listening to the silence between the prompts.
• 5:45
  That's The Feed and The Thread for today. We'll catch you next
• 5:48
  time!