Latest / The Feed & The Thread / The Feed & The Thread - May 3, 2026

Transcript

The Feed & The Thread - May 3, 2026 · The Feed & The Thread

• 0:00
  We're bolting AI onto old interfaces. It's a band-aid on a
• 0:03
  broken process. And the work suffers for it. So how do we
• 0:06
  actually rethink this? We're gonna have to take a look and
• 0:09
  figure it out.
• 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: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:26
  minute UX at five emm UX dot com. The Feed & The Thread is
• 0:29
  available online at feed and thread dot com to submit your
• 0:32
  feeds, or download our app for all the feeds and threads
• 0:35
  delivered right to your pocket.
• 0:44
  We keep adding AI to old interfaces, and the results are
• 0:47
  mixed. That's the tension in today's Feed. Revanth Krishna
• 0:51
  at UX Design.cc argues we need to rethink products from the
• 0:54
  ground up in "Don’t simply bolt on AI. Rethink from the ground
• 0:58
  up.". Simply bolting on an assistant fails because users
• 1:01
  still have to learn complex system concepts. True AI-native
• 1:04
  design should let users state their goals and let the AI
• 1:07
  handle the execution. That shifts the paradigm from
• 1:10
  command-based inputs to intent- based outcomes. Nick Babich
• 1:14
  reviews Anthropic's tool in "Claude Design: Good, Bad, and
• 1:17
  Ugly" at UX Planet. He finds the generated mockups often lack
• 1:20
  structural integrity and accessibility standards. While
• 1:23
  the tool helps with early ideation, it frequently
• 1:26
  misunderstands layout logic. This suggests current AI is
• 1:29
  better for brainstorming than for final, professional-grade
• 1:33
  design work. Artem Shcherban details a two-year portfolio
• 1:36
  redesign in "Designing Against the Gallery: A Two-Year Journey
• 1:39
  to a Layered Portfolio Experience" at Codrops. He
• 1:42
  argues traditional galleries fail to show the depth of a
• 1:45
  designer's process. A layered experience prioritizes
• 1:48
  storytelling over simple visual display. This challenges the
• 1:52
  norm of treating portfolios as static showcases rather than
• 1:55
  dynamic narratives. Other reads today from UX Design.cc on AI
• 1:59
  team playbooks and UX Planet on troubleshooting Claude code
• 2:02
  skills.
• 2:10
  Dropping into the community chatter today. In r/UI_Design,
• 2:13
  a designer is wrestling with unused rewards in a productivity
• 2:16
  app. Should they expire weekly or stay forever? This reveals a
• 2:20
  deeper conflict in gamification. We want to motivate users
• 2:23
  without making them feel cheated. Expiring rewards drive
• 2:26
  action. But they also breed resentment. Keeping them simple
• 2:29
  often feels safe. Yet simplicity can kill long-term engagement.
• 2:33
  The question matters because we're designing for human
• 2:35
  psychology, not just features. We need to balance fairness with
• 2:39
  momentum. Otherwise, the gamification feels manipulative
• 2:42
  rather than helpful. Also in r/UI_Design, an early childhood
• 2:45
  assessment app needs critique. The current color palette is
• 2:49
  overwhelming for a sensitive context. This touches on
• 2:51
  emotional design. Assessing a child's development is high-
• 2:55
  stakes. The interface should feel calm and trustworthy.
• 2:58
  Bright colors might signal fun. But they can also signal chaos.
• 3:01
  Designers often forget that restraint is a feature.
• 3:04
  Especially in healthcare or education. A muted palette
• 3:07
  reduces anxiety. It lets the content breathe. Finally, a
• 3:10
  software engineer is redesigning their site with a brutalist
• 3:13
  palette. Black backgrounds and scarlet red headers. They
• 3:16
  acknowledge their UI weakness but aim for an industrial
• 3:19
  aesthetic. This highlights the gap between coding and design.
• 3:23
  Engineers often prioritize function. But aesthetics build
• 3:26
  trust. A harsh palette might look cool. But it can feel
• 3:29
  aggressive. It's worth asking who the user is. And what
• 3:32
  emotion the brand should evoke. Style without strategy is just
• 3:35
  noise. We're seeing a pattern today. Designers are fighting
• 3:38
  against complexity. Whether it's dense healthcare data or flashy
• 3:42
  interfaces. The solution isn't adding more tech. It's stripping
• 3:45
  away the noise.
• 3:54
  Chicago Camps is hosting Leadership By Design on Thursday
• 3:57
  & Friday, September 17 & 18. It's an online event, so you can
• 4:00
  join from anywhere in the world! Tickets are free, thanks to the
• 4:03
  generosity of the community! If it's within your budget, you can
• 4:07
  purchase a general admission ticket for only twenty six
• 4:09
  dollars - with limited early bird tickets at only fifteen
• 4:12
  dollars. Get tickets now at Chicago Camps dot org.
• 4:22
  Revanth Krishna argues we must shift from command-based inputs
• 4:26
  to intent-based outcomes. It's not about bolting an assistant
• 4:29
  onto a legacy form. It's about rethinking the product
• 4:32
  architecture entirely. That's the ideal. But Nick Babich's
• 4:35
  review of Claude Design shows the reality. The generated
• 4:37
  mockups lack structural integrity. They fail
• 4:40
  accessibility standards because the AI doesn't understand layout
• 4:43
  logic. It understands aesthetics, not systems. So we
• 4:46
  have a paradox. The vision demands we remove complexity by
• 4:49
  letting users state goals. The tooling currently produces
• 4:52
  complexity by ignoring foundational design rules. We're
• 4:55
  asking for magic while the engine is still learning
• 4:57
  physics. I see it as a timing issue. We're using brainstorming
• 5:00
  tools for production work. The thread about stripping away
• 5:03
  noise in healthcare apps proves the point. Simplicity wins. If
• 5:07
  the AI output requires heavy manual cleanup, we haven't
• 5:09
  simplified anything. We've just added a translation layer.
• 5:12
  Exactly. The gap isn't in the technology. It's in the
• 5:15
  workflow. We need to stop judging AI by its ability to
• 5:18
  replace the pixel-pusher. We need to judge it by its ability
• 5:21
  to accelerate the intent-to- outcome loop. Right. But that
• 5:24
  requires designers to be stricter editors, not just
• 5:27
  faster producers. If we accept flawed structures because they
• 5:30
  were generated quickly, we degrade the whole system. The
• 5:33
  risk isn't that AI replaces the designer. It's that bad design
• 5:36
  becomes the default because it's cheap to generate. Then the new
• 5:39
  standard isn't speed. It's the refusal to ship structural debt.
• 5:45
  That's The Feed and The Thread for today. We'll catch you next
• 5:48
  time!