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

Transcript

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

• 0:00
  AI can now spot usability problems faster than human
• 0:02
  researchers. Wait, so we're replacing the team? No, it just
• 0:06
  flags the failures, but only if you ask the right questions.
• 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:31
  The question of what remains when machines do the work is no
• 0:35
  longer theoretical. It's the central tension in our field
• 0:38
  today. Dan Saffer at Chicago Camps argues in "Six Futures"
• 0:41
  that traditional apps are just one of six emerging interaction
• 0:45
  models. He highlights task-based workspaces and ephemeral
• 0:48
  interfaces that dissolve once the AI has done its job. This
• 0:51
  shift means our durable value lies in the judgment to choose
• 0:54
  the right one for the context. Jim Lewis and Jeff Sauro at
• 0:58
  MeasuringU present a rigorous comparative study in "Using AI
• 1:01
  To Find Usability Problems: Examining Task Failure", showing
• 1:04
  that AI models find a similar volume of usability issues to
• 1:08
  humans. However, the AI generated significantly more
• 1:10
  false alarms than the experienced researcher did. This
• 1:13
  suggests we can use AI to cast a wider net, but we still need
• 1:17
  human eyes to filter the noise from the signal. Kai Wong
• 1:20
  writes in "Why designers need to stop reporting and start
• 1:23
  recommending at work" that designers often undervalue their
• 1:26
  role by acting as passive reporters of data. He argues
• 1:29
  that presenting sticky notes to stakeholders is insufficient and
• 1:33
  fails to drive decision-making. Instead, designers must provide
• 1:37
  clear, directional advice that guides teams toward effective
• 1:40
  outcomes. This positions the designer as a strategic partner.
• 1:43
  Other reads available from Smashing Magazine on naming
• 1:46
  conventions, UX Planet on game design models, and Chicago Camps
• 1:50
  on maintaining healthy professional boundaries.
• 2:00
  A junior designer is stuck in the middle of a broken approval
• 2:03
  loop, while a user asks if building a search engine is
• 2:06
  really that easy. These are the questions defining our field
• 2:09
  today. Over on r/UI_Design, a junior designer describes a
• 2:12
  process where Customer Success approves work that developers
• 2:15
  later reject, leaving them without a clear definition of
• 2:18
  done. This disconnect highlights a real tension, because when
• 2:21
  machines handle the heavy lifting, humans often lose the
• 2:24
  structural role of decision- making. We need to ask what
• 2:27
  remains of human judgment when the workflow is automated but
• 2:30
  the accountability is still fragmented. In r/UI_Design,
• 2:33
  someone is wrestling with how to guide a user who feels stuck in
• 2:36
  life, asking if a calm tone can survive a complex navigation
• 2:39
  structure. The core question is whether we should offer an
• 2:42
  overview of all features or push a single next step. This matters
• 2:45
  because if the interface is too complex, it undermines the very
• 2:49
  relief the product promises to provide. Over on
• 2:51
  r/UXResearch, an aspiring researcher is seeking realistic
• 2:54
  feedback on their first project and expressing distrust in AI-
• 2:57
  generated career advice. They want to know if entry-level
• 3:00
  roles are accessible without relying on tools that might
• 3:03
  dilute their own voice. This is a significant signal, because
• 3:06
  the field is currently grappling with how to maintain authentic
• 3:09
  human insight when automated tools are everywhere. In
• 3:12
  r/web_design, a user assumes that building a product search
• 3:15
  site is easy because modern tools are available. But the
• 3:18
  reality of aggregating retail data is far more complex than
• 3:21
  the interface suggests. This misconception reveals a gap
• 3:24
  between the perceived simplicity of the front end and the
• 3:27
  logistical difficulty of the back end, which is a critical
• 3:30
  distinction for any practitioner to understand. Today's
• 3:33
  discussions point to a single truth: the question of what
• 3:36
  remains when machines do the work is no longer theoretical.
• 3:39
  It's the central tension in our field right now.
• 3:49
  The Feed and The Thread is brought to you by Chicago Camps.
• 3:52
  For a weekly and monthly exploration of the patterns and
• 3:55
  signals across UX, you can also check out Patterns and Signals
• 3:58
  at the website patterns and signals dot com. Chicago Camps
• 4:01
  will have more events in 2027. You can submit to be a speaker
• 4:05
  at a future event at Chicago Camps dot org.
• 4:14
  The MeasuringU study on AI usability testing is a data
• 4:17
  point we can't ignore. It found that AI models catch a similar
• 4:20
  volume of usability issues as human researchers, but they
• 4:23
  generate significantly more false alarms. That volume
• 4:25
  metric is exactly where the narrative goes wrong. It treats
• 4:28
  a false positive and a true positive as the same unit of
• 4:31
  work. But in practice, a false alarm isn't just noise. It's a
• 4:34
  cost that erodes the stakeholder's trust in the human
• 4:36
  who has to filter it out. And that erosion is systemic. When
• 4:39
  the signal-to-noise ratio drops, the organization stops treating
• 4:42
  the researcher as a source of insight and starts treating them
• 4:45
  as a gatekeeper of data. We see this in the thread from
• 4:48
  r/UI_Design, where a junior designer is stuck in an approval
• 4:51
  loop that has no clear definition of done. That junior
• 4:54
  designer is the canary in the coal mine. They're being asked
• 4:57
  to perform the judgment call that the automated workflow has
• 4:59
  stripped of context. The AI finds the issue, the developer
• 5:02
  rejects it, and the human is left holding the bag of
• 5:05
  accountability without the authority to define what "fixed"
• 5:08
  actually looks like. So we have a tension between the need for
• 5:11
  speed and the need for judgment. The AI casts a wide net, but it
• 5:14
  doesn't know why a particular issue matters in the context of
• 5:17
  the user's goal. And that's the gap. The AI can find the
• 5:19
  friction, but it can't explain the strategy. If we don't teach
• 5:22
  our teams to articulate the "why" behind the fix, we're just
• 5:25
  replacing human error with machine noise. The value lies
• 5:28
  in knowing which problem to solve and why. Exactly. The
• 5:31
  field is shifting from detection to direction, and the ones who
• 5:34
  can't explain the strategic intent behind their fixes will
• 5:37
  find their judgment discounted.
• 5:40
  That's The Feed and The Thread for today. We'll catch you next
• 5:43
  time!