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

Transcript

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

• 0:00
  Honey Mehta says our obsession with zero friction is actually
• 0:03
  dangerous now. Wait, so making things faster is somehow hurting
• 0:06
  high-stakes decisions? Exactly, because when AI decides in
• 0:09
  milliseconds, we need intentional slowness to build
• 0:12
  trust. That's where it gets interesting.
• 0:18
  Welcome to The Feed and The Thread, brought to you by
• 0:20
  Chicago Camps. There's an open call for speakers for UX Camp
• 0:23
  Summer on May 30th, so now is your chance to get on stage and
• 0:26
  share your ideas! You can use our Proposal Counselor to help
• 0:29
  you get submitted today. The Feed & The Thread is available
• 0:31
  online at feed and thread dot com to submit your feeds, or
• 0:34
  download our app for all the feeds and threads delivered
• 0:37
  right to your pocket.
• 0:45
  Speed is no longer the only metric that matters. In fact,
• 0:48
  moving faster sometimes just accelerates our uncertainty. And
• 0:51
  when systems execute instantly, humans often need more time to
• 0:55
  feel safe. That tension between velocity and trust defines
• 0:58
  today's Feed. Vibe coding with AI tools surfaces questions, but
• 1:02
  it rarely answers them. Jeff Gothelf makes this case in "Vibe
• 1:05
  coding surfaces the questions. Product management answers
• 1:08
  them.". He argues that rapid prototyping without product
• 1:11
  discovery leaves teams with a now what dilemma. Speed without
• 1:15
  direction just creates more work for later. Sustainable
• 1:18
  advantage comes from learning faster than your rivals. Zeeshan
• 1:21
  Khalid writes about this at UX Design.cc in "Designing adaptive
• 1:25
  teams". The piece urges a shift from linear problem-solving to a
• 1:28
  biological, systemic view. Teams must recognize circular cause-
• 1:32
  and-effect relationships to truly adapt. Eliminating all
• 1:35
  friction is becoming counterproductive for high-
• 1:38
  stakes interactions. Honey Mehta introduces the trust-latency gap
• 1:41
  in "The trust-latency gap: why the future of UX is
• 1:44
  intentionally slower". Users often perceive instant speed as
• 1:47
  carelessness when the stakes are high. Deliberate slowness can
• 1:51
  actually build confidence in complex decisions. Other reads
• 1:54
  available from UX Planet on creating diagrams with Claude
• 1:57
  Code and UX Design.cc on why products need a point.
• 2:08
  Welcome to the daily pulse of what designers are actually
• 2:11
  talking about today. Over on r/UXDesign, a designer is asking
• 2:14
  how to build a portfolio case study when their company blocks
• 2:17
  all file exports. One commenter shared a workaround: signing
• 2:21
  into Figma with a personal browser account to copy designs
• 2:24
  from the work desktop version. Another pointed out a deeper
• 2:27
  issue, saying employers seem allergic to process these days.
• 2:30
  This reveals a real tension where protecting intellectual
• 2:33
  property accidentally hides the very work that proves our value.
• 2:37
  In r/UI_Design, someone posted two versions of a compact side
• 2:40
  panel to ask which feels cleaner and more premium. The community
• 2:43
  rejected both, identifying a highly saturated green as the
• 2:46
  main visual offender that strains the eyes. Commenters
• 2:49
  suggested unifying the palette with the existing blue button to
• 2:53
  create a more cohesive look. This highlights how a single
• 2:56
  color choice can override all other layout decisions and ruin
• 2:59
  the user experience. It also highlights that you're going to
• 3:02
  get designer feedback from designers and not user feedback
• 3:06
  from users. This is still such a challenge for folks. Still in
• 3:09
  r/UI_Design, a designer posted a mini bar chart to ask if the
• 3:12
  visual representation is confusing without comments yet.
• 3:15
  The question itself is vital because simplified data often
• 3:18
  lacks the necessary context like labels or scales. If we
• 3:21
  prioritize speed over clarity, we risk shipping interfaces that
• 3:25
  users simply can't interpret. Over on r/UXDesign again, a
• 3:28
  dropout from art school is asking for advice on securing
• 3:31
  jobs without a formal degree. One responder noted that
• 3:34
  everyone is discouraged lately because the job market is tough
• 3:37
  right now. Another designer shared their own path from music
• 3:40
  performance to UX through bootcamps and self-study. This
• 3:43
  conversation validates that real-world experience often
• 3:46
  outweighs credentials when the market is tight. Finally, in
• 3:50
  r/UXResearch, a researcher asked how to incorporate AI into their
• 3:53
  workflow after their company mandated it for performance
• 3:56
  reviews. The discussion reveals a spectrum from using AI for
• 3:59
  tedious formatting to generating rapid competitive analysis. This
• 4:03
  tension between genuine utility and forced automation defines
• 4:06
  the current reality for many research teams. Today's topics
• 4:10
  show that while systems execute instantly, humans still need
• 4:13
  time to feel safe with our work and our careers.
• 4:23
  Chicago Camps is hosting UX Camp Summer on Saturday, May 30th.
• 4:25
  There's an open call for speakers so submit your idea
• 4:28
  today! It's an online event, so you can join from anywhere in
• 4:30
  the world! Tickets are free, thanks to the generosity of the
• 4:33
  community! If it's within your budget, you can purchase a
• 4:36
  general admission ticket for only thirteen dollars and fifty
• 4:38
  cents. Get tickets now at Chicago Camps dot org.
• 4:48
  Honey Mehta's point about the trust-latency gap flips the
• 4:51
  script on speed. She argues that in high-stakes moments, instant
• 4:54
  execution actually signals carelessness to users. That
• 4:56
  hits hard when you look at r/UI_Design thread about the
• 4:59
  saturated green button. The community rejected a perfectly
• 5:02
  functional layout just because the color felt too aggressive
• 5:05
  and rushed. Exactly. The speed of the tool generated the green,
• 5:08
  but the slowness of human perception flagged it as unsafe.
• 5:11
  We're treating velocity as the only metric while ignoring the
• 5:14
  time humans need to feel safe. And that's the trap with vibe
• 5:16
  coding. Jeff Gothelf noted that rapid prototyping without
• 5:19
  discovery just creates a "now what" dilemma. We're building
• 5:22
  faster than we can understand the problem we're solving. So
• 5:25
  the systemic issue is that we optimized for the machine's
• 5:28
  speed but forgot the biological need for pause. Deliberate
• 5:30
  slowness isn't a bug in the system. It's the feature that
• 5:33
  builds confidence. But here's where I diverge. I don't think
• 5:36
  we need to slow down the whole process. We just need to move
• 5:39
  the friction to the right place. The slowness should happen in
• 5:42
  the discovery phase, not the execution phase. That's a fair
• 5:45
  split, but I worry that separating them too cleanly
• 5:47
  breaks the loop. If the team learns faster than rivals, they
• 5:50
  need that biological, systemic view where discovery and
• 5:53
  execution feed each other constantly. Maybe. But if we
• 5:56
  force slowness into every click, we just create more work for
• 5:59
  later. The real shift is knowing when to hit the gas and when to
• 6:02
  let the user breathe. So the goal isn't to move slower. It's
• 6:05
  to move with intention. Right. The difference between a glitch
• 6:08
  and a feature is simply whether the delay feels like a barrier
• 6:11
  or a moment of care.
• 6:14
  That's The Feed and The Thread for today. We'll catch you next
• 6:17
  time!