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

Transcript

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

• 0:00
  We keep blaming the model for slow AI. But Doherty's threshold
• 0:03
  is about acknowledgment, not speed. If you miss that
• 0:06
  distinction, your users just feel ignored.
• 0:12
  Welcome to The Feed and The Thread, brought to you by
• 0:15
  Chicago Camps. The Feed & The Thread is available online at
• 0:18
  feed and thread dot com to submit your feeds, or download
• 0:20
  our app for all the feeds and threads delivered right to your
• 0:23
  pocket.
• 0:31
  The gap between what we think users need and what they can
• 0:34
  actually do is widening. We keep building for the average, but
• 0:37
  the real friction lives at the edges, in the delays, and in the
• 0:40
  assumptions we make about how people process information.
• 0:43
  Patrick Neeman at UX Design.cc makes a sharp distinction in
• 0:47
  "Stop blaming the model for slow AI. Using Doherty’s threshold as
• 0:50
  a guideline.", arguing that the 400-millisecond threshold
• 0:53
  applies to the system's immediate acknowledgment, not
• 0:56
  the final answer. In generative AI, we have two distinct events:
• 0:59
  the quick turn that holds attention, and the slow work
• 1:02
  that generates content. If we confuse these, we lose the
• 1:05
  user's supervision budget, which is the only thing keeping model
• 1:09
  errors in check. Speed is about keeping the human in the loop
• 1:12
  long enough to catch what's wrong. Kai Wong at UX Design.cc
• 1:15
  suggests a radical shift in "If you want to design for
• 1:18
  underserved users, look at farmers’ markets", using
• 1:21
  farmers' markets as a model for digital inclusion. Standard UI
• 1:24
  patterns fail users with lower literacy because they rely on
• 1:27
  rigid, abstract cues that don't exist in physical life. Markets
• 1:31
  work because they offer face-to- face interaction and tangible
• 1:34
  feedback, accommodating diverse needs without a single, perfect
• 1:37
  interface. Designers need to look beyond heuristics to
• 1:40
  understand the bottom third of users who are currently
• 1:43
  invisible to our standard guidelines. L. Jeffrey Zeldman
• 1:46
  shares a quiet update in "Another Saturday, Another
• 1:49
  Song.", noting that his personal music project is nearly
• 1:52
  complete. With fourteen songs finished, he expects to release
• 1:55
  the album before the year ends. It's a reminder that creative
• 1:58
  output doesn't always have to be professional or public to be
• 2:02
  meaningful. Sometimes, the best design work happens in the
• 2:05
  margins, away from the pressure of performance. Other reads
• 2:08
  available from UX Design.cc on headless AI platforms and the
• 2:11
  identity of design education.
• 2:20
  A sort button in a new glass interface is suddenly the most
• 2:23
  discussed visual flaw in the industry. Over on r/UI_Design,
• 2:26
  a developer building a cozy water creature game is asking
• 2:29
  which hover state works best for location buttons on their main
• 2:33
  map. They're weighing several visual alternatives to ensure
• 2:36
  clear user feedback, which highlights how much specific
• 2:39
  affordance details impact usability. The question matters
• 2:42
  because subtle visual cues are often the only bridge between a
• 2:45
  static interface and a responsive one. In r/UI_Design,
• 2:48
  another creator is seeking feedback on a retro-styled
• 2:51
  painting app built in Godot, specifically struggling with the
• 2:54
  look of their primary action buttons. They feel the design
• 2:57
  looks amateurish and are trying to make static lesson
• 3:00
  backgrounds more engaging without losing the retro
• 3:02
  aesthetic. This is a common tension where technical
• 3:05
  constraints meet artistic intent, and the need for
• 3:08
  external validation becomes a tool for refinement rather than
• 3:11
  just ego. Also in r/UI_Design, a junior designer is comparing
• 3:14
  two iterations of a notes app, focusing on layout choices while
• 3:18
  leaving icons uncolored. They're navigating the tricky process of
• 3:21
  adapting iOS-style aesthetics to Android platforms, which often
• 3:24
  requires rethinking default visual hierarchies. The so-what
• 3:27
  here is that cross-platform design isn't just a copy-paste
• 3:30
  job, but a deliberate decision about what feels native to each
• 3:34
  user. Over on r/UI_Design, a user is pointing out that the
• 3:37
  Sort By button in Apple's Finder feels neglected within the new
• 3:40
  Liquid Glass design. They argue it looks congested and oddly
• 3:43
  balanced, challenging the idea that Apple ships with obsessive
• 3:47
  attention to detail. This critique reminds us that even
• 3:50
  flagship products have blind spots, and that user perception
• 3:53
  of polish can diverge from the actual level of effort invested.
• 3:56
  In r/DesignSystems, a UX designer is frustrated by the
• 3:59
  lack of practical AI-assisted workflows that offer true two-
• 4:02
  way syncing between design and code. They're contrasting
• 4:05
  genuine technical solutions with the performative AI promotion
• 4:08
  seen on LinkedIn, which often serves as free marketing rather
• 4:12
  than real utility. The core request is for tools that
• 4:14
  actually solve workflow friction, not just tools that
• 4:17
  promise to do so. Today's discussions all circle back to
• 4:20
  the same friction point, where the gap between intended design
• 4:23
  and actual user experience is widest in the details we often
• 4:27
  overlook.
• 4:34
  The Feed and The Thread is brought to you by Chicago Camps.
• 4:37
  For a weekly and monthly exploration of the patterns and
• 4:40
  signals across UX, you can also check out Patterns and Signals
• 4:43
  at the website patterns and signals dot com. Chicago Camps
• 4:46
  will have more events in 2027. You can submit to be a speaker
• 4:49
  at a future event at Chicago Camps dot org.
• 4:58
  Neeman's piece on the four hundred millisecond threshold is
• 5:01
  pointing at a structural failure we keep ignoring. We treat the
• 5:04
  generation of content as a single event, but it's actually
• 5:06
  two. There's the immediate acknowledgment that holds
• 5:09
  attention, and then the slow work that produces the answer.
• 5:12
  That distinction matters because the r/DesignSystems thread is
• 5:15
  full of people screaming about the lack of two-way syncing.
• 5:17
  They're asking for a way to supervise the process. If the
• 5:20
  tool doesn't let you catch the error in the slow phase, you're
• 5:23
  just guessing at the final output. Exactly. Neeman calls
• 5:26
  this the "supervision budget." It's the limited amount of
• 5:28
  attention a user can give before they disengage. When we blur the
• 5:31
  line between the quick turn and the slow generation, we burn
• 5:34
  that budget before the human can actually verify the result.
• 5:37
  Speed is about keeping the human in the loop long enough to catch
• 5:40
  what's wrong. I think we're framing this as a technical
• 5:43
  problem when it's a trust problem. The community is
• 5:45
  complaining that the current tools treat their judgment as an
• 5:48
  afterthought. If the interface doesn't expose the intermediate
• 5:51
  steps, the designer is just a bystander watching the model
• 5:54
  hallucinate. But exposing those steps isn't free. It adds
• 5:56
  cognitive load. Neeman argues that if we don't manage that
• 5:59
  load properly, we lose the user entirely. The goal is to design
• 6:02
  the specific moment where the human's intervention changes the
• 6:05
  outcome. So the shift is from automation to collaboration. The
• 6:08
  tool should produce a state that invites correction. That's the
• 6:11
  only way to make the "slow work" feel like a partnership instead
• 6:14
  of a gamble. The metric for success is how effectively the
• 6:17
  interface supports the human's ability to steer the process.
• 6:19
  Right now, the gap between what the model can do and what the
• 6:22
  user can verify is where the real design work lives.
• 6:27
  That's The Feed and The Thread for today. We'll catch you next
• 6:30
  time!