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

Transcript

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

• 0:00
  Your AI chatbot is just a text wall in disguise. And users are
• 0:03
  scrolling right past it. One designer fixed it by turning
• 0:06
  answers into visuals, and the results are striking.
• 0:13
  Welcome to The Feed and The Thread, brought to you by
• 0:16
  Chicago Camps. Leadership By Design is on Thursday and
• 0:18
  Friday, September 17 and 18 and tickets are available now! And
• 0:21
  while you're at it, get caught up on UX fundamentals with five
• 0:24
  minute UX at five em UX dot com. The Feed & The Thread is
• 0:27
  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
  There's a growing gap between what AI can generate and what
• 0:45
  users actually understand. We're building faster interfaces, yet
• 0:48
  we're often missing the semantic context that makes those
• 0:52
  interfaces usable. The challenge is no longer speed. It's
• 0:55
  clarity. Tanner Kohler at Nielsen Norman Group lays out
• 0:58
  the core problem in "Designing AI Products and Features: Study
• 1:01
  Guide": simply adding AI features doesn't automatically
• 1:04
  create value for your users. The guide pushes back against the
• 1:08
  idea that automation is a silver bullet, urging designers to
• 1:11
  balance optimism with critical assessment. We need to ask if
• 1:14
  the technology serves the user's intent, or if we're just adding
• 1:18
  complexity for the sake of novelty. That distinction
• 1:21
  defines whether your product feels intelligent or just noisy.
• 1:24
  Luke Wroblewski tackles a specific annoyance in "Ask
• 1:27
  LukeW: Less Walls of Text", where AI chatbots produce dense
• 1:30
  walls of text that are hard to scan. His solution is an
• 1:33
  ingestion pipeline that merges AI-generated image descriptions
• 1:37
  with human-written ALT tags. This creates richer semantic
• 1:40
  embeddings, moving beyond generic labels like "green block
• 1:43
  layout" to context-specific meaning. It turns a visual asset
• 1:46
  into a searchable, meaningful part of the conversation. Tom
• 1:49
  Green at UX Design.cc argues in "Nothing has changed other than
• 1:53
  how we talk about it" that Agentic AI and Design Thinking
• 1:56
  are inherently compatible, especially during the Discover
• 1:59
  and Define phases. He shows how AI agents can rapidly generate
• 2:03
  structured Product Requirements Documents, reducing days of work
• 2:06
  to minutes. However, the real value lies in the Human-in-the-
• 2:10
  Loop review, where designers validate the AI's confident but
• 2:13
  potentially inaccurate assumptions. Speed isn't the
• 2:16
  goal. Precision is. Also out today: UX Planet compares Google
• 2:19
  Stitch and Figma AI, and Nielsen Norman Group explores the three
• 2:23
  roles of context for AI agents.
• 2:32
  The gap between what AI can generate and what users actually
• 2:35
  understand is widening. Over on r/UXResearch, a practitioner is
• 2:38
  asking if their four years of gaming QA and data collection
• 2:41
  work qualifies them for a Junior User Researcher role. They list
• 2:45
  moderating usability tests and conducting eye tracking studies,
• 2:48
  but never held the official title. The tension here's about
• 2:52
  semantic context in hiring. We often rely on job titles to
• 2:55
  signal competency, yet the actual skills of coding
• 2:57
  qualitative data and facilitating sessions are often
• 3:00
  hidden under different labels. This matters because it
• 3:03
  highlights a mismatch between how we define expertise and how
• 3:06
  we actually demonstrate it. In r/UI_Design, a designer is
• 3:10
  debating whether playful animated sequences are better
• 3:12
  than simple spinners for loading states. The argument is that
• 3:16
  playful interactions reduce perceived latency, making the
• 3:19
  wait feel less like a pause. However, this can miss the
• 3:22
  semantic context of clarity. If the animation is distracting, it
• 3:25
  might obscure the actual progress. The key isn't just
• 3:28
  speed, but ensuring the user understands exactly what's
• 3:31
  happening in the system at that moment. Over on r/UXResearch,
• 3:34
  someone is seeking a white paper on the long-term negative
• 3:38
  behavioral impact of bad A/B test experiences. They note a
• 3:41
  trend where teams use LLMs to reduce dev time, arguing that
• 3:44
  launching features without research is risk-free because
• 3:47
  iteration is cheap. This is a dangerous assumption. Rapid
• 3:50
  iteration doesn't replace the need for semantic clarity. If
• 3:53
  the feature confuses users, the cost of confusion isn't just
• 3:56
  lost time, but lost trust. Today's discussions all point to
• 4:00
  a single truth: speed is no longer the differentiator.
• 4:03
  Clarity is.
• 4:10
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:13
  & Friday, September 17 & 18. It's an online event, so you can
• 4:16
  join from anywhere in the world! Tickets are free, thanks to the
• 4:19
  generosity of the community! If it's within your budget, you can
• 4:22
  purchase a general admission ticket for only twenty six
• 4:25
  dollars - with limited early bird tickets at only fifteen
• 4:28
  dollars. Get tickets now at Chicago Camps dot org.
• 4:38
  There's a dangerous assumption circulating in the community
• 4:40
  right now that rapid iteration removes the risk of bad design.
• 4:43
  People are saying that because AI lets us ship features in
• 4:46
  minutes instead of days, we can skip the deep research phase.
• 4:49
  They view speed as a replacement for understanding. That logic
• 4:52
  holds up in a code review, but it falls apart in a user's
• 4:55
  hands. If a feature is confusing, the cost is a loss of
• 4:58
  trust. You can ship a hundred confusing features in a week,
• 5:01
  and the user will still walk away feeling that the product
• 5:04
  doesn't respect their time. And that connects directly to the
• 5:07
  critique about semantic context. We're building interfaces that
• 5:10
  are faster to generate, but they're missing the clarity that
• 5:13
  makes them usable. The gap between what the model can
• 5:15
  produce and what a human can actually comprehend is widening,
• 5:18
  and speed is masking that disconnect. So the real value
• 5:21
  is in the review step. We need to treat the AI output as a
• 5:24
  draft. The human-in-the-loop model needs to be about
• 5:26
  validating intent. We have to ask if the feature serves the
• 5:29
  user's goal, or if it's just noise. Exactly. The distinction
• 5:32
  between intelligent and noisy is defined by whether the user
• 5:35
  understands what's happening. If the animation is distracting, or
• 5:38
  if the logic is opaque, the speed doesn't matter. Clarity is
• 5:41
  the metric that actually defines value. We need to stop treating
• 5:44
  speed as a proxy for quality. The field has to start measuring
• 5:47
  success by how well the user understands the interface, not
• 5:50
  by how quickly we can build it.
• 5:54
  That's The Feed and The Thread for today. We'll catch you next
• 5:57
  time!