Latest / The Feed & The Thread / The Feed & The Thread - April 14, 2026

Transcript

The Feed & The Thread - April 14, 2026 · The Feed & The Thread

• 0:00
  AI tools are so fast they're cutting out the actual thinking.
• 0:03
  That sounds like a feature, not a bug. Until you see what
• 0:06
  happens to the output. We need to talk about this.
• 0:13
  Welcome to The Feed and The Thread, brought to you by
• 0:15
  Chicago Camps. There's an open call for speakers for UX Camp
• 0:18
  Summer on May 30th, so now is your chance to get on stage and
• 0:21
  share your ideas! You can use our Proposal Counselor to help
• 0:23
  you get submitted today. The Feed & The Thread is available
• 0:26
  online at feed and thread dot com to submit your feeds, or
• 0:29
  download our app for all the feeds and threads delivered
• 0:31
  right to your pocket.
• 0:40
  Speed used to be a competitive advantage. Now it's table
• 0:43
  stakes, and the real question is what you do with the time you
• 0:46
  save. Kevin O'Brien shows how to turn deep, manual customer
• 0:50
  work into scalable product features. He outlines a
• 0:53
  framework that moves from cross- functional swarms to internal
• 0:56
  tools, finally shipping native automation. This rewrites the
• 1:00
  assumption that you need data science to find broad patterns.
• 1:03
  Kevin details this process at the Intercom Blog in "From
• 1:06
  swarms to product: Turning customer signals into scalable
• 1:10
  features". Sunkanmi Fafowora proves that smooth page
• 1:13
  transitions require strict accessibility rules. The View
• 1:16
  Transitions API looks impressive, but it demands
• 1:19
  careful setup to respect user motion settings. You can't just
• 1:22
  animate everything without considering the OS-level
• 1:25
  preferences. Sunkanmi shares seven specific recipes for this
• 1:28
  at CSS-Tricks in "7 View Transitions Recipes to Try".
• 1:32
  Scott Jenson argues that fast AI tools actually need slow human
• 1:35
  thinking to work well. The speed of generating designs often
• 1:39
  bypasses the cognitive pause required for real problem-
• 1:42
  solving. Designers must intentionally create negative
• 1:45
  space to critique and refine those outputs. Scott explores
• 1:48
  this concept of Ma on his blog in "The Ma of a New Machine".
• 1:52
  Other reads available from Codrops on digital craft
• 1:54
  experimentation and I Love Typography on font paradoxes.
• 2:05
  Today's community chatter is all about reclaiming the time we
• 2:08
  save on the basics. Over on r/UXDesign, a designer is
• 2:11
  hitting a wall trying to build a portfolio site from scratch in
• 2:15
  code or complex tools. They're rejecting the idea that this
• 2:18
  technical struggle is a learning journey and just want the lowest
• 2:21
  friction path to getting their work online. The community
• 2:24
  agrees that perfection is the enemy of better here. One user
• 2:28
  put it well, saying nothing is wrong with using Squarespace or
• 2:31
  Behance just to start seeing audience reactions. The real win
• 2:34
  isn't the tech stack you chose, it's finally publishing version
• 2:38
  one. In r/UXDesign, another designer is asking how to
• 2:41
  showcase specific features rather than whole fictional
• 2:44
  products. This tension reveals a shift away from the polished,
• 2:47
  fake case studies dominating major tech hubs toward real,
• 2:50
  gritty work. It forces us to ask if our portfolios are actually
• 2:54
  showing how we solve problems or just how we make things look
• 2:57
  pretty. Over on r/UXDesign, a practitioner is looking for
• 3:00
  weekend courses to stay relevant in an AI-driven market. This
• 3:03
  highlights a genuine anxiety about keeping up while working
• 3:07
  full time. The question isn't really about which certificate
• 3:10
  adds value, but how we balance survival with growth when our
• 3:13
  time is so scarce. In r/UserExperience, someone is
• 3:16
  struggling to map a full user journey in one wireframe without
• 3:19
  creating a sprawling mess. They found Figma too long for demos
• 3:23
  and simple drawing tools miss the edge cases. This isn't just
• 3:26
  a tool problem, it's a gap in how we visualize complex systems
• 3:29
  for stakeholders who need clarity, not chaos. Over on
• 3:32
  r/UXResearch, a researcher is proposing in-app interviews to
• 3:35
  stop the drop-off between scheduling and attending calls.
• 3:39
  They want to capture insights while the experience is fresh,
• 3:42
  potentially using AI for conversational flows. This
• 3:45
  approach could finally bridge the gap between when users feel
• 3:48
  pain and when we actually listen to them. The pattern today is
• 3:51
  clear: speed is table stakes, and the real work is deciding
• 3:55
  what to do with the time you save.
• 4:04
  Chicago Camps is hosting UX Camp Summer on Saturday, May 30th.
• 4:07
  There's an open call for speakers so submit your idea
• 4:09
  today! It's an online event, so you can join from anywhere in
• 4:12
  the world! Tickets are free, thanks to the generosity of the
• 4:15
  community! If it's within your budget, you can purchase a
• 4:17
  general admission ticket for only thirteen dollars and fifty
• 4:20
  cents. Get tickets now at Chicago Camps dot org.
• 4:29
  Sunkanmi's piece on View Transitions is a hard reminder
• 4:32
  that the API demands strict accessibility rules. You can't
• 4:35
  just animate everything without checking OS-level motion
• 4:38
  preferences first. That's the friction point. We're seeing
• 4:41
  designers in the community reject the idea that building a
• 4:44
  portfolio site from scratch is a learning journey. They just want
• 4:47
  the lowest friction path to getting their work online. So
• 4:50
  we've a tension between the technical rigor required for new
• 4:53
  APIs and the demand for zero- friction publishing tools. If
• 4:56
  everyone uses a template, who's actually testing how those
• 4:59
  transitions break for users who need reduced motion? Nobody is
• 5:02
  testing it until it's shipped. The community is right that
• 5:05
  perfection is the enemy of better, but that doesn't mean we
• 5:08
  ignore the accessibility gap. We need to stop treating "good
• 5:11
  enough" as a finish line. But if the tooling doesn't enforce
• 5:14
  those rules, the burden falls entirely on the individual.
• 5:17
  That's a systemic failure, not a portfolio problem. The real
• 5:20
  shift isn't in the code, it's in the expectation. We have to
• 5:23
  assume the default output is inaccessible until proven
• 5:26
  otherwise. Exactly. And right now, the gap between "shipping
• 5:29
  fast" and "shipping responsibly" is where the actual craft lives.
• 5:35
  That's The Feed and The Thread for today. We'll catch you next
• 5:37
  time!