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

Transcript

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

• 0:00
  Creative technologists are moving from the margins to the
• 0:02
  center. So the artists are running the product now? AI
• 0:05
  collapsed the gap between idea and execution, and we need to
• 0:08
  see how teams are restructuring around that shift.
• 0:15
  Welcome to The Feed and The Thread, brought to you by
• 0:17
  Chicago Camps. Leadership By Design is on Thursday and
• 0:20
  Friday, September 17 and 18 and tickets are available now! And
• 0:23
  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:31
  feeds, or download our app for all the feeds and threads
• 0:33
  delivered right to your pocket.
• 0:42
  The terms we use to define our work are shifting, not because
• 0:45
  the craft is changing, but because the tools are collapsing
• 0:48
  the distance between idea and execution. That tension is
• 0:52
  reshaping how we talk about value. Ioana Adriana Teleanu at
• 0:55
  UX Design.cc makes the case in "Creative Technologists are
• 0:58
  moving from the margins to the center" that creative
• 1:01
  technologists are moving from the margins to the center of
• 1:04
  product teams. AI is collapsing the gap between concept and
• 1:07
  code, so these professionals now write the first draft of what
• 1:11
  new technologies mean before standard use cases calcify. This
• 1:14
  role requires navigating both technical and creative domains,
• 1:17
  disambiguating a messy taxonomy of titles like UX engineer. It's
• 1:21
  no longer just about building prototypes; it's about defining
• 1:24
  the interface before the rules are written. Rachel Banawa at
• 1:28
  Nielsen Norman Group finds in "No New Name Has Replaced “UX”"
• 1:31
  that no new name has replaced UX, despite growing calls for
• 1:34
  change. A survey of six hundred and four professionals shows
• 1:37
  we're sticking with the default term, even as layoffs and
• 1:41
  tighter budgets pressure us to prove our value. The historical
• 1:44
  shift from usability to human- centered design created a
• 1:47
  fragmented landscape of vocabulary inflation rather than
• 1:50
  clarity. We're holding onto UX because it's the only label that
• 1:54
  still carries enough weight in boardrooms. Other reads today
• 1:57
  from UX Planet on logo design with Claude, CSS-Tricks on
• 2:00
  animation queries, and UX Design.cc on battling AI
• 2:03
  fatigue.
• 2:10
  Practitioners are wrestling with a quiet but persistent question
• 2:14
  today: does the speed of execution actually diminish the
• 2:17
  weight of the craft. The tools are collapsing the distance
• 2:20
  between idea and implementation, which forces us to redefine
• 2:23
  where the value actually lives in our daily work. Over on
• 2:26
  r/UserExperience, the standard monthly career thread sits empty
• 2:29
  of questions, which tells a story in itself. When newcomers
• 2:32
  hesitate to ask basic questions, it suggests they feel the bar
• 2:35
  for entry has shifted or that their confusion isn't unique
• 2:38
  enough to warrant space. It reveals a field where everyone
• 2:41
  is trying to figure out the rules while the rules are still
• 2:44
  being written by algorithms. In r/UI_Design, a designer is
• 2:47
  seeking feedback on a physical instrument cluster for an ESP32
• 2:50
  device, specifically asking if the RPM display has the right
• 2:53
  visual hierarchy. This is fascinating because it bridges
• 2:56
  the gap between digital interface design and tangible
• 2:59
  hardware constraints. It reminds us that even as software becomes
• 3:02
  abstract, the principles of clarity and prominence remain
• 3:05
  critical when the user is holding the device in their
• 3:08
  hands. Over on r/DesignSystems, someone is documenting day three
• 3:11
  of building a system in public, yet the silence around it's
• 3:14
  deafening. Building in public is supposed to be about
• 3:17
  transparency and shared learning, but without
• 3:19
  engagement, it feels like shouting into a void. It raises
• 3:22
  the question of whether the community is too busy consuming
• 3:25
  content to participate in the messy, iterative process of
• 3:28
  creation. In r/Design, a user posted images of a 1976 Alfa
• 3:31
  Romeo Navajo, questioning the baffling disconnect between its
• 3:34
  front and side views. This isn't just about car design; it's
• 3:37
  about coherence. When a product looks one way from the front and
• 3:41
  another from the side, it breaks trust. In UX, we face the same
• 3:44
  issue when our microcopy contradicts our macro layout.
• 3:47
  Over on r/Design, a student is asking if a Master of Design
• 3:50
  degree is worth the two-year investment in a market that
• 3:53
  increasingly values portfolios over credentials. The anxiety is
• 3:56
  palpable because the traditional ladder is becoming a ladder of
• 3:59
  rungs that keep moving. The real question isn't about the degree,
• 4:02
  but whether we're measuring value by the time spent learning
• 4:06
  or the speed of delivery. We're seeing a pattern where the
• 4:09
  medium of delivery is changing faster than the metrics for
• 4:12
  success, leaving us to define our worth in real time.
• 4:22
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:24
  & Friday, September 17 & 18. It's an online event, so you can
• 4:27
  join from anywhere in the world! Tickets are free, thanks to the
• 4:30
  generosity of the community! If it's within your budget, you can
• 4:33
  purchase a general admission ticket for only twenty six
• 4:36
  dollars - with limited early bird tickets at only fifteen
• 4:39
  dollars. Get tickets now at Chicago Camps dot org.
• 4:48
  The piece on creative technologists moving to the
• 4:51
  center of product teams connects directly to that empty career
• 4:54
  thread on Reddit. When the gap between concept and code
• 4:56
  collapses, the ambiguity of roles like UX engineer becomes a
• 4:59
  feature, not a bug, because we're defining the interface
• 5:02
  before the rules are even written. I see it as a shift in
• 5:05
  where value lives. The empty thread suggests newcomers are
• 5:07
  paralyzed because the traditional ladder is moving
• 5:10
  beneath them. If AI handles the execution speed, then the craft
• 5:13
  isn't about building the prototype anymore. It's about
• 5:15
  the judgment call of which prototype to discard. Exactly.
• 5:18
  But that judgment requires navigating a messy taxonomy. The
• 5:21
  article notes these professionals disambiguate
• 5:23
  titles while standard use cases calcify. The risk is that we
• 5:26
  treat this editorial role as optional rather than the primary
• 5:29
  deliverable. If the organization doesn't value the curation, the
• 5:32
  speed just creates more noise. And that's the tension. We're
• 5:35
  waiting for credentials to catch up to the reality of the work.
• 5:38
  The student asking if a Master of Design is worth it's looking
• 5:41
  for a static answer in a dynamic field. The value isn't in the
• 5:44
  degree or the tool. It's in the ability to define what the
• 5:46
  technology means before it becomes standard practice. So
• 5:49
  the metric for success shifts from output volume to definition
• 5:52
  clarity. Precisely. The teams that win are the ones who stop
• 5:55
  measuring speed and start measuring the quality of the
• 5:58
  questions they answer before writing a single line of code.
• 6:02
  That's The Feed and The Thread for today. We'll catch you next
• 6:05
  time!