Latest / The Feed & The Thread / The Feed & The Thread - May 20, 2026

Transcript

The Feed & The Thread - May 20, 2026 · The Feed & The Thread

• 0:00
  Most AI tools just make you faster. So speed isn't the win.
• 0:03
  The best ones actually make you better by forcing critical
• 0:06
  thinking. We're breaking down why that shift matters.
• 0:13
  Welcome to The Feed and The Thread, brought to you by
• 0:15
  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 emm 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 treat AI speed as the primary metric for success. That
• 0:45
  assumption is dangerous. It ignores the cognitive cost of
• 0:48
  automation and the structural friction of fragmented teams.
• 0:52
  Most tools help you finish tasks faster. But Daisy Chen at UX
• 0:55
  Design.cc argues that the best tools make you better. She warns
• 0:59
  against cognitive atrophy in "Most AI tools make users
• 1:02
  faster. The best AI tools make users better.". When users lose
• 1:05
  essential skills, they develop blind trust in the system. Chen
• 1:09
  proposes a framework to calibrate that trust. The goal
• 1:12
  is coevolution, not replacement. Luke Wroblewski sees a similar
• 1:16
  problem in how teams work. He calls current AI usage a solo
• 1:19
  sport. In "Collaborative Steering", he argues that
• 1:22
  scattered context leads to fragmented products. System
• 1:25
  prompts often reflect individual biases rather than shared goals.
• 1:29
  He introduces collaborative steering to fix this. Teams must
• 1:32
  collectively maintain the context that guides their
• 1:35
  agents. Experience doesn't always equal seniority. Jim
• 1:38
  Lewis and Jeff Sauro question the five-year benchmark for UX
• 1:42
  researchers. In "How Many Years Does It Take to Become a Senior
• 1:45
  UX Researcher?", they analyze salary data to find the truth.
• 1:49
  Agency researchers gain methodological breadth quickly.
• 1:52
  In-house peers develop deeper stakeholder navigation skills.
• 1:55
  Context matters more than the calendar. Other reads today
• 1:59
  from Rosenfeld Media on staying human in an AI-smooth world,
• 2:02
  Intercom Blog on pricing strategy, and Codrops on digital
• 2:05
  motion design.
• 2:13
  The conversation today feels less like a trend report and
• 2:16
  more like a field survival guide. Over on r/UXResearch, a
• 2:20
  senior researcher with seven years of experience in banking
• 2:23
  and hardware is re-entering the European market after maternity
• 2:26
  leave. The reality check is stark. One commenter notes that
• 2:29
  despite six years in finance, they haven't even secured an
• 2:32
  interview since AI tools entered the hiring pipeline. Another
• 2:36
  shares that thirty applications and fourteen referrals resulted
• 2:39
  in zero phone screenings. The market isn't just quiet. It's
• 2:42
  structurally hostile to traditional networking. The
• 2:45
  speed of AI filtering has outpaced human connection,
• 2:47
  leaving experienced professionals in a waiting room
• 2:50
  that never opens. In r/UXDesign, the community is
• 2:53
  venting about the semantic noise drowning out actual craft. Terms
• 2:56
  like vibe coding and founder mode are drawing ire for masking
• 3:00
  a lack of ethical substance. But the real friction comes from
• 3:03
  phrases like you're drinking too much. It's a deflection tactic.
• 3:06
  When we treat AI speed as the primary metric for success, we
• 3:09
  ignore the cognitive cost of automation. These buzzwords
• 3:12
  aren't just annoying. They're symptoms of a system that values
• 3:16
  output velocity over user trust. Over on r/hci, a prospective
• 3:19
  master's student is asking which coding languages actually boost
• 3:22
  employability. This anxiety reveals a deeper tension. The
• 3:25
  industry keeps shifting the goalposts for technical
• 3:28
  literacy. Designers feel pressured to become developers
• 3:31
  without a clear roadmap. The question isn't just about
• 3:34
  syntax. It's about who holds the power in fragmented teams. If
• 3:37
  you can't code, do you lose the right to design the interface?
• 3:40
  That assumption is dangerous. In r/UXDesign, a junior designer
• 3:44
  working solo is asking how to uncover edge cases without peer
• 3:47
  review. This highlights the structural friction of isolated
• 3:50
  workflows. When teams are fragmented, the safety net of
• 3:53
  collaborative critique disappears. The designer is left
• 3:56
  guessing. It's not just about missing bugs. It's about the
• 3:59
  cognitive load of simulating diverse user contexts alone.
• 4:02
  Automation might speed up the prototype, but it can't
• 4:05
  replicate the collective intuition of a review session.
• 4:08
  Finally, over on r/UXDesign, a fintech designer is weighing a
• 4:11
  move to a streaming agency. The trade-off is clear. They're
• 4:14
  trading the perceived complexity of financial systems for higher
• 4:18
  income and less bureaucracy. But there's a fear that streaming
• 4:21
  lacks the rigorous problem- solving required in fintech.
• 4:24
  It's a valid concern. Complexity isn't just about data density.
• 4:27
  It's about the stakes. If we prioritize speed over depth, we
• 4:30
  risk losing the nuance that makes high-stakes design
• 4:33
  meaningful. The common thread today is the cost of velocity.
• 4:36
  We're moving faster, but we're paying for it in isolation,
• 4:39
  semantic confusion, and structural fragility.
• 4:49
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:52
  & Friday, September 17 & 18. It's an online event, so you can
• 4:55
  join from anywhere in the world! Tickets are free, thanks to the
• 4:58
  generosity of the community! If it's within your budget, you can
• 5:01
  purchase a general admission ticket for only twenty six
• 5:04
  dollars - with limited early bird tickets at only fifteen
• 5:06
  dollars. Get tickets now at Chicago Camps dot org.
• 5:16
  Daisy Chen argues the best tools make you better, not just
• 5:19
  faster. But Luke Wroblewski says our current usage is a solo
• 5:22
  sport. That creates a paradox. We want coevolution, but we're
• 5:25
  feeding agents individual biases instead of shared context. It's
• 5:29
  the calibration problem. You can't coevolve if the system
• 5:32
  doesn't know the team's actual goals. It just knows what one
• 5:35
  person typed into a prompt. That's why the r/hci anxiety
• 5:38
  about coding feels so sharp. Designers feel they need
• 5:40
  technical syntax to prove they hold the context. Exactly. The
• 5:44
  fear isn't about losing the ability to draw boxes. It's
• 5:46
  about losing the right to define the problem. If the AI handles
• 5:50
  the execution, who owns the constraints? Wroblewski suggests
• 5:53
  collaborative steering. We have to treat system prompts like
• 5:56
  living documents that the whole team edits. That's a heavy lift
• 5:59
  for most orgs. But it's the only way to stop cognitive atrophy.
• 6:02
  If we don't collectively maintain that context, the AI
• 6:05
  optimizes for speed, not depth. We end up with fragmented
• 6:08
  products that look good but don't solve the right problems.
• 6:11
  So the metric shifts from velocity to alignment. Right.
• 6:14
  The value isn't in moving fast. It's in ensuring everyone is
• 6:17
  moving in the same direction.
• 6:21
  That's The Feed and The Thread for today. We'll catch you next
• 6:24
  time!