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

Transcript

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

• 0:00
  Current AI handles booking flights, but ignores social
• 0:03
  maintenance. So we're optimizing for tasks, not relationships?
• 0:06
  Exactly, and that gap is why the tech feels so hollow.
• 0:13
  Welcome to The Feed and The Thread, brought to you by
• 0:16
  Chicago Camps. The Feed & The Thread is available online at
• 0:18
  feed and thread dot com to submit your feeds, or download
• 0:21
  our app for all the feeds and threads delivered right to your
• 0:24
  pocket.
• 0:32
  We build tools to make life easier, yet we often ignore the
• 0:35
  messy, human parts of living. We automate the transaction, but we
• 0:38
  leave the relationship to chance. Julie Zhuo at The
• 0:41
  Looking Glass makes this case in "What would make AI truly
• 0:44
  social?". She argues that current tech handles simple
• 0:47
  tasks like booking flights, but fails at the complex work of
• 0:50
  maintaining social bonds. Her data shows dinner parties are
• 0:54
  declining because the logistical friction is too high. An AI
• 0:57
  agent recently coordinated a college reunion by managing
• 1:00
  contacts and logistics. This proves AI can handle the
• 1:03
  unglamorous work of showing up for others. In "UX and NPS
• 1:06
  Benchmarks of Third Party Automotive Websites (2026)", Eva
• 1:09
  Sundberg, Jim Lewis, and Jeff Sauro at MeasuringU benchmarked
• 1:12
  eleven major automotive websites. They found the
• 1:15
  industry averages the fifty- first percentile in overall
• 1:18
  experience, which is essentially a median performance. Usability
• 1:22
  is the strongest area, with cars.com leading at the eighty-
• 1:25
  second percentile. However, trust remains the critical
• 1:28
  differentiator that separates the leaders from the laggards.
• 1:31
  If users don't trust the data, the best search feature doesn't
• 1:34
  matter. Kai Wong at UX Design.cc tackles a stubborn
• 1:37
  problem in "How to talk about a design that looks worse on
• 1:40
  paper". They use the example of Microsoft taking five years to
• 1:44
  implement a simple fix. This delay happened because designers
• 1:47
  tried to sell the visual appeal instead of the business outcome.
• 1:50
  The piece argues that we must frame proposals around user
• 1:54
  impact and feasibility. A design that looks simple on paper is
• 1:57
  often the hardest one to sell. Also out today: UX Planet on
• 2:00
  making Claude Code more predictable and UX Design.cc on
• 2:03
  what we sacrifice for AI.
• 2:12
  Today's conversations circle a familiar tension: the gap
• 2:15
  between what we build and how people actually live. We
• 2:18
  automate the transaction, yet we often leave the human
• 2:20
  relationship to chance. Over on r/UI_Design, a developer shares
• 2:24
  their progress recreating a complex glow shader from a
• 2:27
  recent conference, entirely in WebGL. It's a technical feat
• 2:30
  that took months to perfect, moving native capabilities into
• 2:33
  the browser. The question isn't just about the code, but about
• 2:36
  the pursuit of visual fidelity. When we chase these specific,
• 2:40
  high-end effects, we're often trying to make digital products
• 2:43
  feel less like tools and more like lived experiences. In
• 2:46
  r/UXResearch, someone with a psychology background is asking
• 2:49
  if an MSc in Applied Psychology is a worthwhile investment for a
• 2:52
  career in tech in India. They're seeking validation on whether
• 2:56
  academic credentials translate to employability. It's a
• 2:58
  practical question, but it highlights a deeper anxiety:
• 3:01
  that we often treat UX as a technical skill rather than a
• 3:04
  human one. The field needs to value the psychological
• 3:07
  foundation more explicitly, not just as a nice-to-have, but as a
• 3:11
  core competency. Back in r/UI_Design, a designer without
• 3:14
  formal UX training is asking for feedback on a finance app built
• 3:17
  with AI assistance. They're bridging the gap between coding
• 3:20
  and interface design, acknowledging their lack of
• 3:23
  expertise. This is a sign of the times: tools are lowering the
• 3:26
  barrier to entry, but they're not replacing the need for
• 3:29
  critical thinking about usability. The work is deciding
• 3:32
  what the code should do for the person using it, not generating
• 3:35
  the code. In r/UXResearch, a researcher is weighing a pivot
• 3:38
  to climate communications, asking how Information
• 3:41
  Architecture skills are valued in nonprofit work. They're
• 3:44
  considering a master's in climate journalism versus
• 3:47
  entering the workforce directly. It's a career question, but it's
• 3:50
  also a signal: our skills are portable, but we need to
• 3:53
  understand how they apply in different contexts. The value
• 3:56
  lies in the problem you're solving, not just in the method.
• 3:59
  Finally, over on r/UI_Design, a developer is asking how to build
• 4:02
  an animated pet companion for a Pomodoro app. They're comparing
• 4:06
  animation tools like Rive and Lottie to handle state-based
• 4:09
  transitions. It's a creative question, but it's about making
• 4:12
  productivity tools feel less sterile. We're not just building
• 4:15
  timers; we're building relationships. The goal is to
• 4:18
  build relationships.
• 4:26
  The Feed and The Thread is brought to you by Chicago Camps.
• 4:29
  For a weekly and monthly exploration of the patterns and
• 4:32
  signals across UX, you can also check out Patterns and Signals
• 4:35
  at the website patterns and signals dot com. Chicago Camps
• 4:38
  will have more events in 2027. You can submit to be a speaker
• 4:41
  at a future event at Chicago Camps dot org.
• 4:51
  I kept coming back to Kai Wong's point about Microsoft. They
• 4:53
  spent five years trying to implement a simple fix, and the
• 4:56
  reason wasn't technical. The team tried to sell the visual
• 4:59
  appeal of the design instead of the business outcome. They
• 5:02
  failed because they framed it as "it looks better" rather than
• 5:04
  "it solves this specific user friction." That's a painful
• 5:07
  reality check. In the community, I see this constantly. A
• 5:10
  designer builds a beautiful interface, but they can't
• 5:12
  articulate why it matters to the bottom line. It's not about
• 5:15
  being a salesperson, but it's about speaking the language of
• 5:18
  the people who sign off on the project. If you're leading with
• 5:21
  aesthetics, you're vulnerable to a "we'll do it later" response.
• 5:24
  And that's where the systemic issue hits. When we treat design
• 5:27
  as purely aesthetic, we ignore the feasibility argument. The
• 5:29
  piece argues that we must frame proposals around user impact and
• 5:32
  feasibility. If you don't prove the path is buildable and
• 5:35
  valuable, the beauty of the concept is irrelevant to the
• 5:38
  decision-maker. I agree, but I think we're missing a deeper
• 5:41
  layer here. It's not just about proving feasibility. It's about
• 5:43
  proving human value. We often treat UX as a technical skill, a
• 5:46
  set of checkmarks. But the core competency is understanding the
• 5:49
  psychology of the person using the tool. If you don't have that
• 5:52
  foundation, you're just guessing at what makes a design "work."
• 5:55
  That's a fair push. We do risk treating the human element as a
• 5:58
  nice-to-have. If we don't explicitly value the
• 6:00
  psychological foundation, we end up with interfaces that are
• 6:03
  functional but cold. They work, sure, but they don't resonate.
• 6:06
  And that's where trust erodes. Exactly. Trust is the
• 6:08
  differentiator. It's not about how fast the search is, or how
• 6:11
  clean the grid is. It's about whether the user feels
• 6:14
  understood. That's the shift we need to make. We need to defend
• 6:17
  our design choices as acts of empathy. So the question isn't
• 6:19
  how to make it look good. It's how to make it feel right.
• 6:22
  That's the standard we should be holding ourselves to. And
• 6:25
  that's the skill that can't be automated. It's the ability to
• 6:28
  see the human behind the screen, and to build something that
• 6:30
  meets them where they are. That's the future of this work.
• 6:35
  That's The Feed and The Thread for today. We'll catch you next
• 6:38
  time!