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

Transcript

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

• 0:00
  Sales teams are vibe coding UIs now. That actually happened to a
• 0:03
  listener. They bypassed design entirely, so we're breaking down
• 0:07
  why this shortcut fails.
• 0:13
  Welcome to The Feed and The Thread, brought to you by
• 0:15
  Chicago Camps. Leadership By Design is on Thursday and
• 0:18
  Friday, September 17 and 18 and tickets are available now! And
• 0:21
  while you're at it, get caught up on UX fundamentals with five
• 0:24
  minute UX at five em UX dot com. The Feed & The Thread is
• 0:27
  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
  We keep building faster, but we aren't building better. The gap
• 0:45
  between speed and quality is widening. Jeff Gothelf and
• 0:48
  Barry O'Reilly make the case in "Traits before tools: rethinking
• 0:52
  when to insert AI into your ways of working". They note that
• 0:55
  while AI adoption has surged, only a fraction of companies see
• 0:59
  real returns. Why? Because AI amplifies existing habits. If
• 1:02
  your process is broken, AI just breaks it faster. They propose
• 1:05
  starting with traits and tasks before picking tools. This flips
• 1:09
  the script on tool-first thinking. It means fixing your
• 1:12
  workflow before you automate it. Pavel Samsonov warns against
• 1:15
  this in "Thoughtless features never add up to a thoughtful
• 1:19
  product". He argues that stacking thoughtless features
• 1:22
  never creates a thoughtful product. Stakeholders often
• 1:25
  implement superficial fixes that confuse users. AI makes this
• 1:28
  worse by speeding up shallow execution. You're not raising
• 1:31
  the ceiling of design quality. You're just lowering the floor.
• 1:35
  The result is a product that feels rushed and confused.
• 1:38
  Takuma Kakehi offers a different lens in "The weakest channel".
• 1:41
  He suggests that universality isn't a design goal you chase.
• 1:45
  It's a byproduct of surviving real constraints. Human
• 1:48
  limitations are those constraints. When you treat
• 1:50
  diverse needs as limits to work within, you build stronger
• 1:54
  systems. This shifts focus from abstract ideals to practical
• 1:57
  problem-solving. It turns exclusion into a structural
• 2:00
  challenge. Other articles today from Codrops on digital craft
• 2:03
  and UX Design.cc on latency.
• 2:12
  Practitioners are hitting a wall where speed is no longer a proxy
• 2:16
  for quality. The tools generate output faster than we can verify
• 2:19
  the intent behind it. Over on r/UXDesign, a solo designer
• 2:22
  shared a frustrating story about returning from vacation to find
• 2:26
  the sales team had already built landing pages using AI. They
• 2:29
  viewed that rapid output as a win. The product team saw
• 2:32
  generic, low-quality work that lacked any strategic depth. It
• 2:35
  highlights the widening gap between how fast we can generate
• 2:38
  pixels and how well those pixels actually serve the user. We're
• 2:42
  building faster, but we aren't necessarily building better. In
• 2:45
  r/UXDesign, a professional with three years of experience is
• 2:48
  pushing back on the expectation to handle both research and
• 2:52
  visual interface design. They prefer the hands-on problem
• 2:55
  solving of research over the aesthetic demands of UI. This
• 2:58
  tension reveals a real misalignment in how roles are
• 3:01
  defined today. When we force designers to be everything, we
• 3:04
  risk losing the specialized rigor that makes either
• 3:07
  discipline strong. Another thread in r/UXDesign asks why
• 3:10
  modern interfaces often prioritize visual flair over
• 3:12
  functional clarity. The poster notes that excessive animations
• 3:16
  and noise obscure the core message. It makes navigation
• 3:19
  harder rather than easier. We're optimizing for aesthetics at the
• 3:22
  expense of usability, which suggests we've lost sight of
• 3:25
  what design is actually for. The conversation shifts to tool
• 3:29
  adoption in r/UXDesign, where users are asking who's actually
• 3:32
  using new AI design skills. There's surprise at the
• 3:35
  technical depth required to integrate these tools
• 3:37
  effectively. It raises the question of whether designers,
• 3:40
  developers, or design engineers are the primary adopters. The
• 3:44
  workflow is changing, but the human judgment remains the
• 3:47
  critical bottleneck. Finally, practitioners in r/UXDesign are
• 3:50
  sharing how their end-to-end workflows have adapted since AI
• 3:53
  became part of daily work. They're distinguishing between
• 3:56
  tasks that benefit from automation and those that
• 3:59
  require manual, human thought. The goal is to keep the
• 4:02
  strategic intent intact while leveraging efficiency. We need
• 4:05
  to protect the quality of our thinking even as we accelerate
• 4:08
  the execution. The real challenge today isn't generating
• 4:11
  the work, but deciding what's worth keeping.
• 4:21
  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:34
  purchase a general admission ticket for only twenty six
• 4:37
  dollars - with limited early bird tickets at only fifteen
• 4:40
  dollars. Get tickets now at Chicago Camps dot org.
• 4:49
  The sales team treating AI- generated landing pages as a win
• 4:52
  while product sees generic garbage is the perfect
• 4:55
  illustration of what Pavel Samsonov warned about. We're
• 4:58
  stacking thoughtless features at machine speed, and it's not
• 5:01
  raising the ceiling of quality. It's just lowering the floor.
• 5:04
  And that's where the r/UXDesign thread hits home. The speed is
• 5:07
  no longer a proxy for quality because we can't verify intent
• 5:10
  fast enough. When you prioritize visual flair and rapid output
• 5:13
  over functional clarity, you aren't building a product.
• 5:15
  You're building noise. But I look at Jeff Gothelf's point
• 5:18
  about traits before tools, and I think the problem isn't just the
• 5:22
  noise. It's that we're applying AI to broken workflows. If your
• 5:25
  process is flawed, AI just breaks it faster. We need to fix
• 5:28
  the workflow before we hand anyone a generator. I disagree
• 5:31
  that fixing the workflow comes first. The workflow is broken
• 5:34
  because we're ignoring human limitations as constraints.
• 5:36
  Takuma Kakehi argues that universality is a byproduct of
• 5:39
  surviving those limits. We need to treat diverse needs as
• 5:42
  structural challenges, not abstract ideals. That's the only
• 5:45
  way to stop the shallow execution. So you're saying we
• 5:48
  should design for the constraints first, and the tools
• 5:50
  will follow? Exactly. When we treat exclusion as a structural
• 5:53
  problem to solve, we build stronger systems. The AI doesn't
• 5:56
  care about the user, but the design process must. That's a
• 5:59
  tough sell to stakeholders who see speed as the only metric
• 6:02
  that matters. It is. Until they realize that a confused product
• 6:05
  doesn't convert, no matter how fast it was built.
• 6:10
  That's The Feed and The Thread for today. We'll catch you next
• 6:13
  time!