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

Transcript

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

• 0:00
  Designers are now being called glorified janitors for cleaning
• 0:03
  up engineering messes. That hits hard. It means we're fixing
• 0:06
  broken products instead of preventing them. And the
• 0:08
  frustration is that we're losing our seat at the table before a
• 0:11
  line is coded. We should unpack that.
• 0:17
  Welcome to The Feed and The Thread, brought to you by
• 0:19
  Chicago Camps. There's an open call for speakers for UX Camp
• 0:22
  Summer on May 30th, so now is your chance to get on stage and
• 0:25
  share your ideas! You can use our Proposal Counselor to help
• 0:28
  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:33
  download our app for all the feeds and threads delivered
• 0:36
  right to your pocket.
• 0:44
  We keep building smarter bots, yet users still feel like
• 0:47
  they're shouting into a void. The gap isn't about intelligence
• 0:51
  anymore. It's about whether our interfaces acknowledge where the
• 0:54
  person actually is right now. Small design choices like how a
• 0:57
  bot introduces itself determine if users trust it or quit.
• 1:01
  Georgia Kenderova, Maria Rosala, and Tanner Kohler at Nielsen
• 1:04
  Norman Group found that bots failing to signal awareness of
• 1:07
  the current page cause immediate frustration. Their piece, "10
• 1:10
  Guidelines for Designing Your Site’s AI Chatbots", argues that
• 1:14
  we must clearly state capabilities and offer prompt
• 1:17
  suggestions to fix this. Moving from abstract ethics to concrete
• 1:20
  patterns is no longer optional for high-stakes AI work. Dora
• 1:23
  Czerna at UX Design.cc notes that Microsoft and Google are
• 1:27
  now publishing specific guidelines to manage the full
• 1:30
  lifecycle of interactions. In "The rulebook for designing AI
• 1:33
  experiences", she highlights the need for appropriate reliance so
• 1:36
  users trust systems only as much as they're capable. The
• 1:40
  industry's obsession with the user might actually be the wrong
• 1:43
  focus for the next generation of tools. Luke W. argues on his
• 1:46
  blog that we should design for goals people accomplish without
• 1:50
  thinking about the interface at all. His podcast, "Podcast:
• 1:53
  Agents, Interfaces, and More", warns about the tension between
• 1:56
  users who want total transparency and those who just
• 1:59
  want clean results. Other reads today include Codrops on
• 2:02
  watercolor shaders and Nielsen Norman Group on why user panels
• 2:06
  fail.
• 2:13
  Today's conversations feel less about building smarter tools and
• 2:17
  more about where people actually are. Over on r/UXDesign,
• 2:20
  practitioners are listing companies to avoid, calling out
• 2:23
  private equity firms for turning workplaces into health hazards.
• 2:26
  One commenter noted that these ownership structures eventually
• 2:30
  hurt everyone involved. The tension here's clear: when
• 2:33
  financial engineering drives decisions, user empathy becomes
• 2:36
  the first casualty. In r/UXDesign, a designer asks if
• 2:39
  we've become glorified janitors cleaning up products built
• 2:42
  without design input. Developers feel the same way, calling
• 2:45
  themselves codebase janitors too. And with AI accelerating
• 2:48
  the build phase, the fight to be the last one employed feels
• 2:51
  intense. We're building faster, yet acknowledging the human cost
• 2:55
  of that speed is harder than ever. Over on r/UXDesign, a
• 2:58
  senior designer fed twenty pages of specs into an AI tool and
• 3:01
  generated a full app in thirty minutes. The developers got
• 3:04
  scared because the software worked flawlessly. This proves
• 3:08
  that rigorous documentation is the missing key to effective AI
• 3:11
  collaboration. If we want AI to succeed, we need to stop cutting
• 3:14
  corners on our specs. It also proves that someone here is not
• 3:18
  telling the entire truth. In r/UXResearch, someone starting a
• 3:21
  dream job at a company with recent layoffs seeks advice on
• 3:24
  navigating that high-stakes environment. The thrill of the
• 3:27
  opportunity clashes with the pragmatism of instability. This
• 3:31
  question reveals that even in a dream role, the shadow of job
• 3:34
  loss is changing how we approach Day One. Over on r/UI_Design, a
• 3:37
  creator seeks feedback on a dashboard meant to reduce
• 3:40
  fatigue for indie developers. The goal is balancing feature
• 3:43
  richness with the simplicity needed for a lightweight tool.
• 3:47
  It shows we're finally trying to design for the actual
• 3:50
  constraints of our users, not just the features we want to
• 3:53
  sell. We're building interfaces that work perfectly, yet users
• 3:56
  still feel like they're shouting into a void. The gap isn't
• 3:59
  intelligence anymore; it's whether our work acknowledges
• 4:02
  where the person actually is right now.
• 4:12
  Chicago Camps is hosting UX Camp Summer on Saturday, May 30th.
• 4:15
  There's an open call for speakers so submit your idea
• 4:17
  today! It's an online event, so you can join from anywhere in
• 4:20
  the world! Tickets are free, thanks to the generosity of the
• 4:23
  community! If it's within your budget, you can purchase a
• 4:26
  general admission ticket for only thirteen dollars and fifty
• 4:29
  cents. Get tickets now at Chicago Camps dot org.
• 4:38
  The Nielsen Norman Group piece on chatbots failing to signal
• 4:41
  page awareness hits a specific nerve. When a bot acts like it
• 4:44
  doesn't know where you're, trust evaporates instantly. That's
• 4:47
  the gap between intelligence and presence. We're building systems
• 4:50
  that can write code but can't read the room. The user feels
• 4:53
  like they're shouting into a void because the interface
• 4:56
  ignores their context. It connects to the "glorified
• 4:58
  janitor" sentiment in the design thread. If we automate the build
• 5:02
  phase without fixing this contextual awareness, we just
• 5:04
  speed up the frustration. Or we shift the definition of value.
• 5:07
  The designer who spends thirty minutes generating a spec isn't
• 5:10
  the one who matters. It's the one who defines what the bot
• 5:13
  should know about the current page before it speaks. So the
• 5:16
  metric changes from how fast we can generate output to how
• 5:19
  deeply the system understands the user's immediate reality.
• 5:21
  Exactly. The interface that acknowledges where the person
• 5:24
  actually is right now will be the only one that survives.
• 5:29
  That's The Feed and The Thread for today. We'll catch you next
• 5:32
  time!