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

Transcript

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

• 0:00
  AI coding agents are creating a new psychological trap. Design
• 0:03
  fixation? That sounds expensive. It costs your creativity, so
• 0:06
  we're breaking down the four distinct AI design jobs to fix
• 0:10
  it.
• 0:14
  Welcome to The Feed and The Thread, brought to you by
• 0:16
  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:31
  feeds, or download our app for all the feeds and threads
• 0:34
  delivered right to your pocket.
• 0:42
  We built tools to remove friction from our workflow, but
• 0:45
  that very absence of resistance is now trapping us in bad ideas.
• 0:49
  When building becomes effortless, we lose the pause
• 0:52
  that lets us question whether we're solving the right problem.
• 0:55
  Meg Kurdziolek at UX Design.cc makes this case in "The
• 0:58
  psychological cost of moving too fast". She argues that AI coding
• 1:01
  agents have slashed financial costs but introduced a heavy
• 1:05
  psychological toll through design fixation. When teams move
• 1:08
  too fast from idea to functional prototype, they harden those
• 1:11
  ideas prematurely. This speed creates confirmation bias and
• 1:14
  makes designers defensive about their work, even when the sunk
• 1:18
  cost is low. We stop pivoting because we've already built it.
• 1:21
  The danger isn't the cost; it's the loss of curiosity. Sarah
• 1:24
  Gibbons at Nielsen Norman Group clarifies this in "The Four
• 1:27
  Design Jobs AI Created (So Far)". She argues that the term
• 1:30
  AI design is too broad and misleading because it masks four
• 1:34
  distinct types of work. These roles range from generating
• 1:37
  component variations to defining behavioral parameters for large
• 1:40
  language models. Recognizing these differences matters
• 1:43
  because each requires a fundamentally different skill
• 1:46
  set. Treating them as one discipline dilutes the expertise
• 1:49
  needed for each. Diogo Andrea details this shift in "The
• 1:52
  Making of the New Lesse Studio Website: Clarity, Performance,
• 1:56
  and Intentionality" at Codrops. He shows how rebuilding the
• 1:59
  Lesse Studio website with self- hosting and deliberate tool
• 2:02
  selection improved performance and clarity. Moving away from
• 2:05
  bloated third-party dependencies reduces technical debt and gives
• 2:09
  designers greater control over the user experience. Intentional
• 2:12
  choices in infrastructure directly impact the perceived
• 2:15
  quality of the interface. Control comes from stripping
• 2:18
  back, not adding on. Other articles today from Nielsen
• 2:21
  Norman Group on behavioral economics and UX Design.cc on
• 2:24
  workplace loyalty.
• 2:32
  The ease of modern tools is stripping away the necessary
• 2:35
  friction that forces us to pause and question whether we're
• 2:38
  solving the right problem. Over on r/UI_Design, a developer
• 2:42
  admits their word puzzle game menu feels boring because they
• 2:45
  relied on React Bootstrap to mask limited design skills. This
• 2:48
  reveals a dangerous comfort zone where technical convenience
• 2:51
  overrides intentional craft. When building becomes
• 2:54
  effortless, we lose the resistance that usually signals
• 2:57
  we're taking shortcuts. In r/UXDesign, a design leader
• 3:00
  shares a plugin that automates the entire design system
• 3:03
  lifecycle, cutting setup time from weeks to hours. While speed
• 3:06
  is tempting, removing the manual labor of token setup and code
• 3:09
  deployment might also remove the deep understanding of how those
• 3:13
  systems actually function. We risk deploying solutions we no
• 3:16
  longer truly comprehend. A cognitive science student in
• 3:19
  r/UXResearch asks how to transition into design, seeking
• 3:22
  clarity on daily workflows and portfolio building. Their
• 3:25
  psychology background is valuable, but the shift from
• 3:27
  academic inquiry to practical application requires a different
• 3:31
  kind of rigor. The question matters because it highlights
• 3:34
  the gap between theoretical knowledge and the messy reality
• 3:37
  of user engagement. Over on r/UI_Design, a beginner
• 3:40
  struggles to create distinct icons for locked and unblocked
• 3:43
  doors in a retro sci-fi game without using generic symbols.
• 3:46
  This specific challenge underscores the tension between
• 3:49
  thematic style and universal usability. Good design must
• 3:52
  communicate clearly even when it tries to look unique. A solo
• 3:55
  developer in r/UI_Design shares their first app, a study
• 3:58
  tracker, noting that while users praise the aesthetics, retention
• 4:01
  is dropping significantly. Positive UI feedback doesn't
• 4:04
  guarantee long-term engagement if the core problem isn't being
• 4:08
  solved. This disconnect proves that visual polish can't mask a
• 4:11
  lack of functional value. We're seeing a pattern where removing
• 4:14
  friction from the workflow removes the critical thinking
• 4:17
  required to validate the work itself.
• 4:27
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:29
  & Friday, September 17 & 18. It's an online event, so you can
• 4:32
  join from anywhere in the world! Tickets are free, thanks to the
• 4:36
  generosity of the community! If it's within your budget, you can
• 4:39
  purchase a general admission ticket for only twenty six
• 4:41
  dollars - with limited early bird tickets at only fifteen
• 4:44
  dollars. Get tickets now at Chicago Camps dot org.
• 4:54
  That piece on the psychological cost of speed is the real
• 4:57
  headline here. We removed friction from our workflows, but
• 5:00
  we accidentally removed the resistance that forces us to
• 5:03
  question our assumptions. Exactly. When building is
• 5:05
  effortless, we lose the pause. I keep thinking about that solo
• 5:08
  developer in the threads whose app looks great but retains no
• 5:11
  one. Visual polish can't mask a lack of functional value. And
• 5:15
  that connects to the confirmation bias Meg Kurdziolek
• 5:17
  mentioned. We harden ideas prematurely because the
• 5:20
  prototype exists. The sunk cost is low, but the emotional
• 5:23
  attachment is high. So the problem isn't the speed. It's
• 5:25
  that we're treating the first draft as the final answer. We
• 5:28
  need to reintroduce friction intentionally. Not to slow down,
• 5:31
  but to force a review of whether we're solving the right problem.
• 5:35
  I see it differently. I think the issue is that we haven't
• 5:38
  defined what that pause actually looks like in a new workflow. If
• 5:41
  we just add steps, we create bottlenecks. We need new
• 5:44
  rituals, not just more meetings. Agreed. But until we have those
• 5:47
  rituals, the default is momentum. And momentum favors
• 5:49
  the wrong ideas. We have to stop confusing velocity with
• 5:52
  progress. It's a shift in how we measure success. Right. If
• 5:55
  your process doesn't include a mechanism for killing your
• 5:58
  favorite idea, you aren't designing. You're just
• 6:01
  decorating.
• 6:03
  That's The Feed and The Thread for today. We'll catch you next
• 6:06
  time!