Latest / The Feed & The Thread / The Feed & The Thread - October 24, 2026

Transcript

The Feed & The Thread - October 24, 2026 · The Feed & The Thread

• 0:00
  AI saves time on every task, yet designers are unhappy. That
• 0:03
  disconnect is the real problem. Efficiency isn't the goal, and
• 0:07
  we need to find what is.
• 0:13
  Welcome to The Feed and The Thread, brought to you by
• 0:15
  Chicago Camps. The Feed & The Thread is available online at
• 0:18
  feed and thread dot com to submit your feeds, or download
• 0:20
  our app for all the feeds and threads delivered right to your
• 0:23
  pocket.
• 0:31
  AI is saving us time, yet we don't feel faster. That tension
• 0:34
  sits at the heart of today's Feed. Maria Rosala and Rachel
• 0:37
  Banawa at Nielsen Norman Group found in "AI in UX: Work Is
• 0:41
  Faster, But Practitioners Have Mixed Feelings" that ninety-nine
• 0:44
  percent of practitioners use AI, but most remain lukewarm. The
• 0:48
  issue is reliability. When output is inconsistent, the
• 0:51
  efficiency gains feel hollow. That rewrites the assumption
• 0:54
  that speed alone builds trust. Vitaly Friedman at Smashing
• 0:57
  Magazine argues in "Accordion Icons: Which Work Best?" that
• 1:01
  the downward caret is the most reliable icon for expansion.
• 1:04
  Right-facing arrows create confusing dual actions, where
• 1:07
  text links to a page and the icon opens a menu. Reserve the
• 1:11
  entire clickable area for the accordion function. Clarity
• 1:14
  beats cleverness here. Nick Babich at UX Planet tests three
• 1:17
  approaches in "Can Claude Code Design Professional UI
• 1:20
  Animations? I Tested 3 Approaches" to see if Claude
• 1:23
  Code can design professional UI animations. The results show
• 1:27
  potential for rapid prototyping, but clear limitations in nuanced
• 1:30
  motion design. AI helps with structure, not yet with soul.
• 1:34
  Other articles today from UX Design.cc on buy versus build
• 1:37
  decisions and Nielsen Norman Group on UX disciplines.
• 1:47
  Today's discussions circle a frustrating reality: we're
• 1:50
  handing over more control to AI and new tools, yet the core
• 1:53
  human work of design is still being skipped, questioned, or
• 1:56
  micromanaged. It's a day about who gets to decide what good
• 1:59
  looks like. Over on r/UXDesign, a veteran designer shared a
• 2:03
  painful story where their volunteer work for a charity was
• 2:06
  bypassed entirely, with the final site built using AI
• 2:08
  without their input. The tension here isn't just about the loss
• 2:12
  of a project, but the signal it sends that design expertise is
• 2:15
  becoming optional. When AI can generate a site in minutes, the
• 2:18
  industry risks treating the process as disposable rather
• 2:21
  than valuable. In r/UXDesign, someone proposed building a tool
• 2:24
  that lets you search for UI components by the specific
• 2:27
  problem you're trying to solve, rather than just looking at what
• 2:31
  other companies have built. This flips the script on inspiration.
• 2:34
  Instead of copying a pattern, you're looking for a functional
• 2:37
  solution. It's a smart pivot that acknowledges that knowing
• 2:40
  what worked elsewhere is less useful than knowing how to fix
• 2:43
  your current bug. Over on r/UXDesign, the conversation
• 2:46
  turned to the ethical line between optimization and
• 2:49
  manipulation. Specifically, why is it so easy to sign up for a
• 2:52
  service but so hard to cancel it? This friction is often
• 2:55
  justified by business metrics, but it erodes trust. If we
• 2:58
  design for retention by making exit difficult, we aren't
• 3:01
  designing for users; we're designing for the bottom line at
• 3:04
  the expense of respect. In r/UXDesign, a designer in
• 3:07
  healthcare asked how to handle a manager who uses micromanagement
• 3:10
  to undermine their seniority. This is less about design
• 3:13
  decisions and more about power dynamics. When a manager
• 3:16
  nitpicks trivial details to assert control, the team loses
• 3:19
  momentum. Navigating this requires protecting your
• 3:22
  professional credibility without escalating into a personal
• 3:25
  conflict. Over on r/UXDesign, someone asked if an iPad Pro is
• 3:28
  sufficient for professional UX work. The answer isn't just
• 3:31
  about hardware specs, but about the ecosystem. If your tools
• 3:34
  don't sync with the team's workflow, the portability is a
• 3:37
  feature that becomes a bottleneck. Professionalism is
• 3:40
  defined by your ability to deliver, not just the device in
• 3:43
  your hand. The through-line today is that speed and
• 3:46
  automation are changing the rules, but the need for human
• 3:49
  judgment, ethical boundaries, and professional respect remains
• 3:52
  the anchor.
• 4:00
  The Feed and The Thread is brought to you by Chicago Camps.
• 4:03
  For a weekly and monthly exploration of the patterns and
• 4:06
  signals across UX, you can also check out Patterns and Signals
• 4:09
  at the website patterns and signals dot com. Chicago Camps
• 4:12
  will have more events in 2027. You can submit to be a speaker
• 4:15
  at a future event at Chicago Camps dot org.
• 4:24
  Ninety-nine percent of practitioners use AI, yet most
• 4:27
  remain lukewarm about it. The gap between usage and
• 4:30
  satisfaction defines the situation. I think that
• 4:32
  lukewarm feeling comes from a mismatch in expectations. We're
• 4:35
  treating AI like a senior partner when it's really more
• 4:38
  like a very fast, very inconsistent intern. And that
• 4:41
  inconsistency is exactly what kills the trust. When the output
• 4:44
  varies every time, the efficiency gain feels hollow
• 4:47
  because you have to spend your mental energy verifying the work
• 4:50
  instead of doing the work. Right. So the problem is the
• 4:53
  tool's unpredictability. We need to focus on "how reliable is
• 4:56
  this specific part of the workflow?" rather than "how fast
• 4:59
  can this generate a design?" That's a crucial distinction.
• 5:02
  We've been measuring speed as a proxy for value, but reliability
• 5:05
  is what actually builds the habit. If I can't count on the
• 5:08
  output, I can't build a process around it. Exactly. And that
• 5:11
  means the skill we need to build is verification. We need to get
• 5:15
  better at knowing what to check, and what to ignore. So the
• 5:18
  metric for success in our field is how much confidence we have
• 5:21
  in the result. And that confidence has to be earned by
• 5:24
  the tool, not assumed by the user.
• 5:27
  That's The Feed and The Thread for today. We'll catch you next
• 5:31
  time!