Latest / The Feed & The Thread / The Feed & The Thread - July 22, 2026

Transcript

The Feed & The Thread - July 22, 2026 · The Feed & The Thread

• 0:00
  Healthcare websites are actually getting worse at user
• 0:02
  experience. That's a shock given all the tech upgrades. Scores
• 0:06
  dropped to the thirtieth percentile, so we're breaking
• 0:08
  down exactly where the money went.
• 0:14
  Welcome to The Feed and The Thread, brought to you by
• 0:17
  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 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
  We build systems to handle complexity, yet our tools often
• 0:45
  create more noise than signal. That tension between automation
• 0:48
  and accuracy is reshaping how we trust our own judgment. Kolozsi
• 0:52
  István at UX Design.cc tests this in "I handed a UX review
• 0:55
  over to AI. Here’s what happened.". He handed a real UX
• 0:58
  review to AI, expecting speed, but found it hallucinated
• 1:01
  defects that didn't exist. The AI caught only twenty percent of
• 1:04
  actual usability issues, while inventing problems that
• 1:07
  distracted from the real work. This confirms what recent
• 1:10
  studies suggest: AI is a companion for structure, not a
• 1:13
  replacement for expert judgment. We risk shipping shallow
• 1:16
  solutions every time we skip the human review. Eva Sundberg, Jim
• 1:20
  Lewis, and Jeff Sauro at MeasuringU show a troubling
• 1:23
  trend in "UX and NPS Benchmarks of Healthcare Websites (2026)".
• 1:26
  Healthcare website scores dropped from the sixty-seventh
• 1:29
  to the thirtieth percentile over eight years. Users access these
• 1:33
  portals during high-stress medical emergencies, yet
• 1:36
  fragmented data and complex navigation increase their
• 1:39
  cognitive load. Digital engagement is high, but the
• 1:41
  experience is deteriorating. Poor design in healthcare isn't
• 1:45
  just frustrating, it's dangerous when users are already
• 1:48
  overwhelmed. Durgesh Pawar at Smashing Magazine exposes a
• 1:51
  security blind spot in "Weaponizing And Defending The
• 1:54
  React Flight Protocol: Deserialization Sinks In RSCs".
• 1:57
  The React Flight protocol acts as a deserialization system,
• 2:00
  which introduces significant risks if developers trust the
• 2:03
  framework too much. A recent vulnerability allowed remote
• 2:06
  code execution via crafted requests to server functions. We
• 2:09
  often overlook attack surfaces in the reconstruction layer
• 2:12
  because we assume the framework handles payload safety. Strict
• 2:16
  schema validation is the only defense against these hidden
• 2:19
  entry points. Other reads today from UX Planet on turning CSV
• 2:22
  data into interactive charts with Claude Code, Jeffrey
• 2:25
  Zeldman on landing page naming, and Codrops on building magnetic
• 2:29
  commerce interfaces.
• 2:37
  Designers are asking harder questions about the value of
• 2:40
  their work today, moving past surface-level tool debates to
• 2:43
  examine how we validate our own judgment. In r/UXDesign, a
• 2:46
  junior designer is preparing for an interview at a very early-
• 2:50
  stage startup, wondering what to expect when processes are
• 2:53
  undefined. It highlights the uncertainty of joining a company
• 2:56
  where responsibility is broad but structure is thin, forcing
• 2:59
  designers to rely on instinct rather than established
• 3:02
  frameworks. That lack of scaffolding tests your ability
• 3:05
  to create order from chaos, proving that accuracy matters
• 3:08
  more than automation when the rules haven't been written yet.
• 3:11
  Over on r/UXDesign, someone is seeking insights from designers
• 3:14
  currently working at Toast to understand the daily workflow
• 3:18
  and culture there. It's a search for anecdotal evidence to make
• 3:21
  informed career decisions, cutting through the polished
• 3:24
  employer branding to find the reality of the work environment.
• 3:27
  We need these honest conversations because company
• 3:30
  culture directly impacts how much mental bandwidth we've for
• 3:33
  actual design thinking versus administrative noise. In
• 3:36
  r/UXDesign, a designer is sharing an open-source assistive
• 3:39
  robot project, asking for feedback on voice control and
• 3:42
  remote operation interfaces. It's a fascinating look at
• 3:45
  physical UX, where quiet, smooth linear motion aims to make
• 3:48
  health monitoring accessible and intuitive. This reminds us that
• 3:51
  good design isn't just about screens, but about how
• 3:54
  technology integrates into our bodies and our lives without
• 3:57
  adding cognitive load. The real challenge isn't just building
• 4:00
  better tools, but learning to trust our judgment when those
• 4:03
  tools fail to provide clear answers.
• 4:13
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:16
  & Friday, September 17 & 18. It's an online event, so you can
• 4:19
  join from anywhere in the world! Tickets are free, thanks to the
• 4:22
  generosity of the community! If it's within your budget, you can
• 4:25
  purchase a general admission ticket for only twenty six
• 4:28
  dollars - with limited early bird tickets at only fifteen
• 4:31
  dollars. Get tickets now at Chicago Camps dot org.
• 4:41
  That Kolozsi experiment is a perfect case study in why speed
• 4:44
  is a trap. He handed a real UX review to AI, expecting
• 4:46
  efficiency, and got twenty percent of the actual issues
• 4:49
  while the system hallucinated defects that didn't exist. It
• 4:52
  proves AI is a tool for structure, not a replacement for
• 4:54
  expert judgment. But here's where I push back on the "expert
• 4:57
  judgment" label. The Reddit thread on UX audits shows the
• 5:00
  real bottleneck isn't the AI's accuracy, it's the human
• 5:03
  inability to sell the findings. If the AI gives you a shallow,
• 5:06
  fast report, stakeholders might actually listen faster. The
• 5:08
  problem isn't that the AI is wrong, it's that our current
• 5:11
  review process is so slow that people stop listening before the
• 5:14
  human expert even finishes speaking. That's a dangerous
• 5:17
  trade-off. If we accept shallow solutions because they're
• 5:20
  faster, we're shipping broken products. The React Flight
• 5:22
  security article makes this even clearer. Developers assume the
• 5:25
  framework handles payload safety, and that assumption
• 5:28
  leads to remote code execution vulnerabilities. We can't
• 5:30
  outsource our critical thinking to the tool, whether it's a
• 5:33
  design assistant or a server protocol. I agree we can't
• 5:36
  outsource the thinking, but I think we're confusing validation
• 5:39
  with generation. The AI didn't replace the designer, it
• 5:42
  replaced the initial scan. The opportunity is to use that
• 5:44
  flawed, fast output as a stress test. You take the AI's
• 5:47
  hallucinated defects and your human findings, and you compare
• 5:50
  them. The friction between the two reveals the blind spots
• 5:53
  neither of you saw alone. So you're arguing for a dialectical
• 5:56
  process. Use the noise from the AI to highlight the signal from
• 5:59
  the human. Exactly. We stop asking if the tool is right or
• 6:01
  wrong. We start asking what the gap between the tool's output
• 6:04
  and our judgment tells us about the system itself. The metric
• 6:07
  shifts from accuracy to insight. And that's the only way we
• 6:10
  survive the noise.
• 6:13
  That's The Feed and The Thread for today. We'll catch you next
• 6:16
  time!