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

Transcript

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

• 0:00
  AI gave everyone answers, but nobody can verify them. So we're
• 0:03
  just trusting the black box? Exactly, and we need to talk
• 0:06
  about how to design for understanding, not just output.
• 0:14
  Welcome to The Feed and The Thread, brought to you by
• 0:16
  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:28
  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 used to think speed was the enemy of quality. Now it's the
• 0:45
  enemy of understanding. That shift changes how we value our
• 0:49
  own expertise. Wira Indra Kusuma at UX Design.cc explores
• 0:52
  this in "AI democratized the answer, not the understanding".
• 0:55
  He argues that AI democratized answers, but not the ability to
• 0:59
  verify them. That creates a dangerous dependency where we
• 1:02
  accept outputs without critical evaluation. The real work isn't
• 1:06
  generation. It's verification. And that requires deep domain
• 1:09
  knowledge we can't outsource. Hiroshi Sato writes at UX
• 1:12
  Design.cc in "Past form, future use". He challenges our
• 1:15
  obsession with immediate form by looking at long-term use. Design
• 1:19
  value often emerges through adaptation, not just initial
• 1:22
  intent. We need to consider how our interfaces age and remain
• 1:26
  relevant over decades. Utility transcends trends when we design
• 1:29
  for the future. Jeff Gothelf at his blog makes the case in
• 1:32
  "Training your PMs on AI tools is the easy part". Training
• 1:36
  product managers on AI tools is easy. Integrating them for true
• 1:39
  innovation is hard. Most companies just accelerate
• 1:42
  existing roadmaps. They lack the psychological safety and
• 1:45
  protected time needed for real experimentation. Without
• 1:48
  permission to explore, AI just builds faster feature factories.
• 1:52
  Other articles today from UX Design.cc on the shift from
• 1:55
  T-shaped professionals to polymath architects, and on the
• 1:58
  gap between access and mastery.
• 2:07
  There's a quiet anxiety in the community today about what
• 2:10
  actually holds value when tools move faster than thought. We're
• 2:14
  seeing a shift from judging work by its polish to judging it by
• 2:17
  the depth of understanding behind it. Over on r/UXDesign,
• 2:20
  a designer is wrestling with the trap of solving the request
• 2:23
  instead of the problem. Users often ask for more filters when
• 2:26
  they really need better discoverability. Or they want
• 2:29
  more notifications to soothe anxiety about missing
• 2:32
  information. The tension here's that speed often pushes us to
• 2:35
  just build what's asked for. But true expertise means pausing to
• 2:38
  diagnose the underlying need. If we move too fast, we lose the
• 2:42
  understanding required to fix the root cause. In r/UXDesign,
• 2:45
  an experienced product designer is stuck on structuring their
• 2:48
  portfolio. They've years of experience but feel lost on how
• 2:51
  to present it. This highlights a real friction point. Seniority
• 2:54
  doesn't automatically grant clarity in storytelling. The
• 2:57
  portfolio is no longer just a showcase of visuals. It's a
• 3:00
  demonstration of how you think through complex problems. The
• 3:04
  struggle to organize this reveals that we're still
• 3:06
  figuring out how to value process over output. Another
• 3:09
  thread on r/UXDesign asks whether to bet on traditional
• 3:12
  fundamentals or pivot to AI native specialization. The
• 3:15
  debate centers on whether AI can replace the deep understanding
• 3:18
  of human behavior. Some worry that focusing on tools means
• 3:21
  neglecting the core of design. But the real question is about
• 3:24
  adaptability. We need to master the tools without losing the
• 3:27
  empathy that drives them. Understanding human behavior
• 3:30
  remains the irreplaceable edge. A designer who took a three
• 3:33
  month health break feels like they missed ten years of
• 3:36
  progress. They're anxious about falling behind on agentic AI
• 3:39
  tools for mapping and prototyping. This fear of
• 3:42
  obsolescence is palpable. But visual design skills still hold
• 3:45
  weight. The workflow has changed, but the goal of solving
• 3:48
  user problems hasn't. Catching up is less about learning every
• 3:51
  new tool and more about reapplying core principles to
• 3:54
  new contexts. The divide is clear between moving fast and
• 3:57
  understanding deeply. We're learning that speed is no longer
• 4:00
  the enemy of quality, but it's the enemy of insight.
• 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:23
  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
  The shift from judging work by polish to judging it by the
• 4:41
  depth of understanding behind it is the most significant
• 4:44
  structural change I've seen this year. When AI democratizes
• 4:47
  answers, verification becomes the only thing that retains
• 4:49
  scarcity. I agree that verification is the new
• 4:52
  bottleneck. But the community thread on r/UXDesign reveals a
• 4:55
  dangerous trap. Designers are solving for the request instead
• 4:58
  of the problem because they assume the AI output is the
• 5:00
  starting point. They ask for more filters when they need
• 5:03
  better discoverability. That's exactly the dependency Wira
• 5:06
  Indra Kusuma warned about. We're outsourcing the generation but
• 5:09
  keeping the verification burden on humans who lack the time to
• 5:12
  do it properly. The real risk isn't bad output. It's
• 5:15
  unverified output that looks polished enough to ship. So we
• 5:18
  need to stop treating tools as accelerators and start treating
• 5:21
  them as collaborators that require strict editorial
• 5:23
  oversight. The teams that win won't be the ones building
• 5:26
  faster. They'll be the ones who refuse to ship without a human
• 5:29
  judgment layer that questions the premise, not just the
• 5:32
  pixels. And that judgment layer has to be built into the
• 5:35
  process, not bolted on at the end. Right. Verification isn't
• 5:38
  a final step. It's the foundation.
• 5:41
  That's The Feed and The Thread for today. We'll catch you next
• 5:44
  time!