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

Transcript

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

• 0:00
  Well-meaning designers are building addictive systems they
• 0:02
  didn't intend to create. So we're actually complicit in
• 0:05
  harming users just by chasing engagement metrics. Exactly, and
• 0:08
  the corporate structures force us to prioritize those numbers
• 0:12
  over human health. That's where it gets interesting. Let's get
• 0:15
  into it!
• 0:19
  Welcome to The Feed and The Thread, brought to you by
• 0:22
  Chicago Camps. There's an open call for speakers for UX Camp
• 0:24
  Summer on May 30th, so now is your chance to get on stage and
• 0:27
  share your ideas! You can use our Proposal Counselor to help
• 0:30
  you get submitted today. The Feed & The Thread is available
• 0:33
  online at feed and thread dot com to submit your feeds, or
• 0:35
  download our app for all the feeds and threads delivered
• 0:38
  right to your pocket.
• 0:46
  The systems we build to make things better keep making things
• 0:50
  worse, and the fix starts with admitting we're part of the
• 0:53
  problem. Today, we face a tension between AI speed, human
• 0:56
  intent, and the metrics that drive us. Alexandra Vasquez at
• 0:59
  UX Design.cc makes this case in "Data models: the shared
• 1:02
  language your AI and team are both missing", arguing that AI
• 1:06
  will faithfully replicate our internal ambiguity if we don't
• 1:09
  first fix our data models. The transformer architecture relies
• 1:12
  on word relationships rather than definitions, so a vague
• 1:15
  term like intent can cause a product to ship with a critical
• 1:19
  misalignment. That rewrites the assumption that better prompting
• 1:22
  alone solves these gaps. Nicolas Garnier writes about
• 1:25
  this at Codrops in "Building the Maxima Therapy Website: React,
• 1:29
  GSAP, and Dabbling with AI", showing how AI accelerates
• 1:32
  creative coding without replacing design intuition. The
• 1:35
  project merges React structure with GSAP animations to reduce
• 1:38
  the stigma around therapy, using AI only to generate variations
• 1:42
  and speed up specific tasks. It proves that the tool is a subtle
• 1:45
  accelerator when human goals remain the primary driver.
• 1:48
  Heenesh Patel challenges us in "We didn’t mean to build this
• 1:51
  engagement at any cost" at UX Design.cc, noting that well-
• 1:55
  meaning designers have become complicit in creating addictive
• 1:58
  systems. Meta's recent fine proves that engagement metrics
• 2:01
  often override ethical considerations, turning human
• 2:04
  costs into invisible variables on a dashboard. We must confront
• 2:07
  the reality that platform decay happens when profit targets
• 2:11
  silence our professional judgment. Other reads available
• 2:14
  from Jeff Gothelf on AI agility risks, UX Design.cc on synthetic
• 2:17
  users, and UX Design.cc on who we're really designing for.
• 2:28
  Welcome back to the Thread, where we're digging into what
• 2:31
  the community is actually saying today. Over on r/UXDesign,
• 2:34
  senior designers are breaking down how they hit three hundred
• 2:38
  thousand dollars in total compensation. The path isn't
• 2:41
  just about design skills. It's about mastering your domain and
• 2:44
  your people so deeply that your boss trusts you to own the
• 2:47
  outcome. One designer noted that you stop waiting for permission
• 2:51
  once you understand the business goals and engineering costs.
• 2:54
  That shift from executing tasks to making calls is the real
• 2:57
  difference. But there's a real tension there between climbing
• 3:01
  the ladder and loving the work. In the same subreddit, someone
• 3:04
  admitted they love the craft but hate the corporate culture. One
• 3:08
  freelancer pointed out a hard truth: even if you leave, you're
• 3:11
  often still working for the same corporations. The only real
• 3:14
  escape might be building your own products in your own time.
• 3:18
  It forces you to confront whether you want to fix the
• 3:21
  system or leave it entirely. Meanwhile, over on r/UXDesign,
• 3:24
  people are asking about RPG game UI systems. This question
• 3:27
  highlights a gap where our tools for complex logic often feel
• 3:30
  disconnected from human intent. We build systems to manage
• 3:33
  complexity, but sometimes those systems just create more
• 3:37
  friction for the user. In r/UXResearch, there's growing
• 3:40
  interest in becoming a digital accessibility specialist. This
• 3:43
  isn't just a niche skill anymore. It's a fundamental
• 3:46
  requirement that challenges us to build for everyone, not just
• 3:49
  the average user. Ignoring this means building systems that
• 3:52
  actively exclude people. And finally, over on r/UXDesign, the
• 3:56
  conversation on MCP is getting complicated. Some users are
• 3:59
  confused about how these backend connectors work with tools like
• 4:03
  Figma. The reality is that the tools are evolving faster than
• 4:06
  our understanding of how to use them. We're rushing to integrate
• 4:09
  AI speed, but we're not always clear on the human intent behind
• 4:13
  the connection. The pattern is clear: we're building faster
• 4:16
  systems that demand more of us, while the culture that drives
• 4:20
  them often feels worse.
• 4:28
  Chicago Camps is hosting UX Camp Summer on Saturday, May 30th.
• 4:31
  There's an open call for speakers so submit your idea
• 4:34
  today! It's an online event, so you can join from anywhere in
• 4:37
  the world! Tickets are free, thanks to the generosity of the
• 4:40
  community! If it's within your budget, you can purchase a
• 4:42
  general admission ticket for only thirteen dollars and fifty
• 4:45
  cents. Get tickets now at Chicago Camps dot org.
• 4:55
  Heenesh Patel's point about invisible human costs hits hard
• 4:59
  when you see Meta's fine. We've treated engagement metrics as
• 5:03
  neutral data while they quietly override our ethical judgment.
• 5:07
  That's the trap, though. We blame the dashboard, but
• 5:10
  Alexandra Vasquez makes the real point: if our data models are
• 5:14
  vague, the AI just amplifies that ambiguity. Exactly. A
• 5:18
  transformer architecture doesn't understand definitions, so a
• 5:22
  fuzzy term like intent becomes a critical misalignment that ships
• 5:26
  to production. So better prompting won't fix it. We've to
• 5:30
  stop asking the AI to guess and start fixing the shared language
• 5:34
  our teams actually use. But fixing language is slow work.
• 5:38
  The pressure is to ship faster, not to pause and refine the
• 5:42
  definitions that drive the models. Speed without clarity is
• 5:46
  just moving fast toward the wrong place. The real
• 5:49
  opportunity is treating data modeling as the primary design
• 5:53
  constraint. We've been building systems that move faster than
• 5:57
  our understanding of them. The gap between that speed and our
• 6:01
  clarity is where the actual design work begins.
• 6:06
  That's The Feed and The Thread for today. We'll catch you next
• 6:09
  time!