Latest / The Feed & The Thread / The Feed & The Thread - June 3, 2026

Transcript

The Feed & The Thread - June 3, 2026 · The Feed & The Thread

• 0:00
  AI isn't freeing us from work. It's creating document fatigue.
• 0:03
  So we're just reading more garbage? Exactly. One designer
• 0:06
  shows how she stopped the churn and reclaimed her focus.
• 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:26
  available online at feed and thread dot com to submit your
• 0:29
  feeds, or download our app for all the feeds and threads
• 0:31
  delivered right to your pocket.
• 0:40
  We promised AI would give us time back. Instead, it gave us a
• 0:43
  mountain of drafts to review and a new way to cheat our research.
• 0:47
  The tools meant to speed us up are demanding more of our
• 0:50
  attention, not less. Heenesh Patel at UX Design.cc tackles
• 0:54
  this exhaustion in "AI-created document fatigue: how I designed
• 0:57
  my way out of it". The problem isn't that AI writes badly. It's
• 1:01
  that reading screen text is slow and draining. He built ARC, a
• 1:04
  voice-first tool that lets you listen to documents and speak
• 1:08
  feedback directly into Google Docs. It turns passive reading
• 1:11
  into active conversation. You review complex material without
• 1:15
  staring at a screen, and the cognitive load drops
• 1:17
  significantly. Jim Lewis and Jeff Sauro at MeasuringU offer a
• 1:21
  clever fix for dirty data in "Using the TAC-10 for Screening
• 1:24
  and Data Cleaning". Ten percent of paid panelists cheat, and old
• 1:28
  attention checks fail against AI. They suggest using the
• 1:31
  TAC-10 checklist to spot fakes. By looking for Guttman scaling
• 1:35
  consistency, researchers can filter out bots that mimic human
• 1:38
  behavior. It turns a tech- savviness test into a lie
• 1:41
  detector. Nick Babich shows how to actually use AI for work in
• 1:45
  "Automation with Claude Code". He focuses on Claude Code's new
• 1:48
  workflow features for automation. These updates handle
• 1:51
  complex, multi-step processes that usually require manual glue
• 1:55
  code. Designers can streamline repetitive tasks and reduce
• 1:58
  overhead in their development lifecycle. It shifts AI from a
• 2:02
  chat toy to a production partner. Other reads today from
• 2:05
  CSS-Tricks on search styling, UX Design.cc on trusting your
• 2:08
  taste, and UX Planet on complex animations.
• 2:18
  Today's threads keep returning to the same uncomfortable
• 2:21
  observation — AI isn't the threat, it's the cover story for
• 2:24
  leadership cutting design out of the work. Over on r/UXDesign, a
• 2:27
  senior designer details being replaced not by an AI tool but
• 2:30
  by a Product Analyst — and the post's title says the quiet part
• 2:34
  out loud: it's not the AI, it's a lack of understanding of what
• 2:37
  design actually does. Commenters across the thread land in the
• 2:40
  same place, noting AI didn't cause the failure but exposed an
• 2:43
  organizational dysfunction that had been there all along. The
• 2:46
  work itself becomes the casualty when leadership treats design as
• 2:50
  decoration instead of decision- making. Elsewhere on
• 2:52
  r/UXDesign, another designer describes the whiplash version
• 2:56
  of the same story — pushed all- in on AI, hit a tenfold
• 2:58
  productivity gain through vibe- prototyping, then the company
• 3:02
  yanked the token budget when Copilot bills got real. They're
• 3:05
  now back to static Figma prototypes with stakeholders
• 3:07
  still expecting the AI-velocity output. The cost of mandating
• 3:11
  tools without strategy is paid by the people doing the work,
• 3:14
  not the people doing the math. And from r/UXDesign, a senior
• 3:17
  designer in Vietnam writes about resigning after watching their
• 3:20
  company spend five months systematically dismantling the
• 3:23
  design function — Figma licenses pulled, design and product
• 3:26
  management merged into "Product Generalists," designers pushed
• 3:29
  to ship code they can't read or debug. It's the vibe-coding
• 3:32
  trend running aground on the part nobody wants to say out
• 3:35
  loud: research, judgment, and accountability live in different
• 3:38
  heads for a reason. Calling that consolidation efficiency is the
• 3:42
  polite name for negligence. In r/UI_Design, a designer asks
• 3:45
  whether their dark-mode App Store screenshots feel too
• 3:48
  intimidating for a health and calorie-tracking app — a small
• 3:51
  question pointing at a real tension between the designer's
• 3:54
  pull toward premium-and-simple and the use case's need for
• 3:57
  safe-and-open. Dark mode reads as heavy or clinical, and that
• 4:00
  runs against everything wellness UX is trying to communicate. The
• 4:03
  question is really whose state wins — the designer's taste, or
• 4:06
  the emotional register the product actually has to meet.
• 4:09
  The pattern threading through today isn't AI versus design —
• 4:12
  it's leadership versus design, with AI as the script the cuts
• 4:16
  read from.
• 4:23
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:26
  & Friday, September 17 & 18. It's an online event, so you can
• 4:29
  join from anywhere in the world! Tickets are free, thanks to the
• 4:32
  generosity of the community! If it's within your budget, you can
• 4:36
  purchase a general admission ticket for only twenty six
• 4:38
  dollars - with limited early bird tickets at only fifteen
• 4:41
  dollars. Get tickets now at Chicago Camps dot org.
• 4:51
  Heenesh Patel built an entire voice-first review system just
• 4:54
  to escape AI document fatigue. Jim Lewis and Jeff Sauro built a
• 4:57
  screening test to catch panelists who hand their answers
• 5:00
  to a chatbot. Nick Babich is wrestling Claude Code into real
• 5:02
  automation pipelines. These are people taking AI seriously by
• 5:05
  engineering carefully around it. And on the community side it
• 5:08
  looks completely different. One designer in r/UXDesign got
• 5:11
  replaced by a "Product Analyst" because leadership decided
• 5:14
  design was just decoration. Another posted about being told
• 5:17
  to go all-in on AI, then had the token budget yanked when the
• 5:20
  bill came due. A third in Vietnam just resigned after
• 5:22
  their company merged design into product management and pushed
• 5:25
  designers into code they can't debug. Same tool. Completely
• 5:28
  different relationship to it. One side is engineering around
• 5:31
  AI's actual costs. The other side is having the tool waved at
• 5:34
  them as a justification for cutting roles. The giveaway is
• 5:37
  the language. Practitioners building voice review tools talk
• 5:40
  about cognitive load and screening discipline. The
• 5:42
  designers in those threads talk about being "consolidated" or
• 5:45
  "encouraged to go all-in." That's not a technology
• 5:48
  vocabulary. That's an HR vocabulary. Which makes the
• 5:50
  careful pragmatism almost defensive. You build a voice
• 5:53
  review tool because you accept the document tsunami isn't going
• 5:56
  away. You build a cheater filter because you accept the research
• 5:59
  pool is now contaminated. Right — and the resignations are what
• 6:02
  happens when nobody upstream is doing that work. When the tool
• 6:05
  gets reached for as a justification rather than a
• 6:08
  constraint. The split doesn't run along skills or generations.
• 6:11
  It runs along who actually has to do the work. The tool
• 6:13
  doesn't cut the team. AI is just the cover sheet on the
• 6:16
  memo.
• 6:18
  That's The Feed and The Thread for today. We'll catch you next
• 6:21
  time!