Latest / The Feed & The Thread / The Feed & The Thread - August 20, 2026

Transcript

The Feed & The Thread - August 20, 2026 · The Feed & The Thread

• 0:00
  AI ethics is actually a UX problem. Wait, you mean the
• 0:03
  interface frames the morality? Exactly, because how we explain
• 0:06
  the decision changes what the user accepts, so let's look at
• 0:10
  the data.
• 0:14
  Welcome to The Feed and The Thread, brought to you by
• 0:17
  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
  The words we choose around AI shape how people judge it. That
• 0:45
  shifts the blame from code to character. Slava Polonski at UX
• 0:49
  Design.cc makes this case in "What nobody tells you about AI
• 0:52
  ethics". Experimental research shows that framing changes moral
• 0:56
  responses. Saying the AI decided something feels different than
• 0:59
  saying we designed the system. The outcome is identical, but
• 1:03
  the accountability shifts. Designers must own the narrative
• 1:06
  they build into the interface. Bob Baxley argues that courage
• 1:09
  is our scarcest resource in "Live event: Design Courage,
• 1:12
  with Bob Baxley". Scott Berkun hosts this live conversation
• 1:16
  with the veteran leader. No external authority will champion
• 1:19
  your work. You have to become your own advocate. It means
• 1:22
  owning decisions rather than just advising on them. Nick
• 1:26
  Babich points out a critical error in "7 Critical Mistakes
• 1:29
  You’re Likely Making with Claude Code". Users often jump straight
• 1:32
  to implementation with Claude Code. They skip the context that
• 1:36
  gives the AI real understanding. Without a CLAUDE.md file, you
• 1:39
  waste tokens on mediocre solutions. Ask the model to
• 1:42
  explore your codebase before it changes anything. Other
• 1:46
  articles today from Rosenfeld Media on Shift UX 2026, Jeffrey
• 1:49
  Zeldman on industrial design history, and Codrops on
• 1:52
  relighting images with depth maps.
• 2:01
  Practitioners aren't just asking what tools to use anymore.
• 2:04
  They're asking who gets to define the work when the
• 2:07
  boundaries blur. Over on r/hci, an incoming master's student is
• 2:10
  choosing between two thesis paths. One advisor focuses on
• 2:14
  human-centered design for medical AI agents, while the
• 2:16
  other prioritizes raw algorithm development. The tension here
• 2:20
  isn't just about mentorship. It's about whether we judge AI
• 2:23
  by its code or by its character. If we lean into the technical
• 2:26
  side, we risk blaming the machine for bad outcomes. But if
• 2:29
  we center the human experience, we hold the designers
• 2:32
  accountable. That shift matters because it changes where we look
• 2:36
  for solutions. In r/uxresearch, a senior researcher is
• 2:39
  questioning whether to pivot away from the field entirely.
• 2:42
  After five years at major tech companies, they're facing
• 2:45
  ghosting and stalled interviews. They're wondering if doubling
• 2:48
  down on SQL or Python will save their career. This highlights a
• 2:51
  deeper anxiety. The market is demanding technical skills that
• 2:55
  often belong to data science roles. When we force researchers
• 2:58
  to code, we dilute their core value. The question isn't just
• 3:01
  about survival. It's about whether the field can retain its
• 3:04
  human insight while chasing technical credibility. Also in
• 3:08
  r/uxresearch, someone is pushing back against the term full-stack
• 3:11
  UX designer. Job postings now demand qualitative research,
• 3:14
  design systems, and advanced coding skills in one hire. The
• 3:17
  author argues this is unrealistic. It tries to merge
• 3:20
  three distinct professional roles into a single person. This
• 3:23
  trend shifts blame from organizational structure to
• 3:26
  individual capability. If we can't hire for these roles
• 3:29
  separately, we shouldn't expect one person to do them all. It's
• 3:32
  a recipe for burnout and shallow work. A final-year student in
• 3:36
  r/uxresearch is asking whether UX research or design offers
• 3:39
  better opportunities over the next decade. With a background
• 3:42
  in psychology and HR, they're worried about market saturation.
• 3:46
  This question reveals a lack of clarity about where value is
• 3:49
  created. Research provides the evidence. Design executes the
• 3:52
  solution. Both are vulnerable to AI automation. But research
• 3:55
  grounds the decision-making. Without it, design is just
• 3:58
  decoration. The market may fluctuate, but the need for
• 4:01
  understanding users remains constant. Finally, a researcher
• 4:04
  in r/uxresearch is looking for a free and open source alternative
• 4:08
  to Atlas.ti. They run Linux and can't use the university-
• 4:11
  licensed Windows version. They're using R for quantitative
• 4:14
  analysis but need something for qualitative data. This
• 4:17
  highlights a tooling gap. We often rely on proprietary
• 4:20
  software that locks us out of certain platforms. When we
• 4:23
  choose tools based on convenience rather than
• 4:25
  accessibility, we exclude parts of the community. It's a small
• 4:29
  friction point, but it points to a larger issue. Our tools should
• 4:32
  serve our workflows, not the other way around. We're seeing
• 4:35
  a pattern where technical demands are reshaping
• 4:38
  professional identity. The words we choose around these skills
• 4:41
  shape how we judge our worth.
• 4:50
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:53
  & Friday, September 17 & 18. It's an online event, so you can
• 4:56
  join from anywhere in the world! Tickets are free, thanks to the
• 5:00
  generosity of the community! If it's within your budget, you can
• 5:03
  purchase a general admission ticket for only twenty six
• 5:06
  dollars - with limited early bird tickets at only fifteen
• 5:09
  dollars. Get tickets now at Chicago Camps dot org.
• 5:19
  The framing debate in Slava Polonski's piece hits a nerve.
• 5:22
  If we say the system decided, we shift blame from code to
• 5:24
  character. But looking at the r/uxresearch thread on full-
• 5:27
  stack designers, I see the same dynamic. We're blaming
• 5:30
  individual capability for what's actually an organizational
• 5:33
  failure to hire for distinct roles. Exactly. It's about who
• 5:36
  owns the narrative. In the thread, the author argues that
• 5:39
  merging research, design systems, and coding into one
• 5:41
  hire is unrealistic. It shifts the burden from bad structure to
• 5:44
  the person trying to survive it. We need to stop treating burnout
• 5:47
  as a personal failing and start treating it as a design flaw in
• 5:51
  how we build teams. But isn't there a risk that if we always
• 5:54
  point to the structure, we absolve the practitioner of
• 5:56
  agency? Bob Baxley's point on design courage suggests we have
• 5:59
  to become our own advocates. If we wait for the org to fix the
• 6:02
  hiring model, we're stuck. Maybe the issue is that we haven't
• 6:05
  defined what it means to own a decision in a hybrid role. I
• 6:08
  disagree with that pivot. Courage doesn't mean accepting
• 6:11
  an impossible workload as a badge of honor. It means
• 6:13
  refusing to let the definition of the role expand until it
• 6:16
  breaks you. The r/uxresearch community is right to push back.
• 6:19
  If we don't protect the boundaries of these roles, we
• 6:22
  lose the depth required to do any of them well. So we're
• 6:25
  saying the structure is the enemy, not the lack of grit.
• 6:27
  I'm saying the structure sets the trap, but our willingness to
• 6:30
  fall into it because we fear looking inflexible is what keeps
• 6:33
  us there. Then the work isn't about doing more. It's about
• 6:36
  defining what we refuse to do. Right. And until we articulate
• 6:39
  that boundary clearly, the job posting will keep writing
• 6:42
  itself.
• 6:44
  That's The Feed and The Thread for today. We'll catch you next
• 6:48
  time!