Latest / The Feed & The Thread / The Feed & The Thread - November 5, 2026

Transcript

The Feed & The Thread - November 5, 2026 · The Feed & The Thread

• 0:00
  AI is burning gasoline on a fire we already lit. So the speed we
• 0:03
  celebrate is actually the problem. We're measuring
• 0:06
  outputs, not outcomes, and that's eroding user trust.
• 0:14
  Welcome to The Feed and The Thread, brought to you by
• 0:16
  Chicago Camps. The Feed & The Thread is available online at
• 0:19
  feed and thread dot com to submit your feeds, or download
• 0:22
  our app for all the feeds and threads delivered right to your
• 0:24
  pocket.
• 0:32
  The industry is debating whether AI replaces designers, but we
• 0:36
  stopped asking what users actually need. We're measuring
• 0:39
  speed, not empathy. Russell Pinkston at UX Design.cc argues
• 0:42
  in "Design by numbers: is AI ruining UX or just pouring
• 0:45
  gasoline on the fire?" that AI is just pouring gasoline on a
• 0:48
  fire we already lit. The issue is our obsession with outputs
• 0:52
  over outcomes. Pinkston uses the analogy of a microwave versus
• 0:55
  fine dining to show that while AI speeds up production, it
• 0:58
  lacks the nuance required for true user-centered design. We
• 1:02
  risk shipping shallow solutions every time we prioritize a
• 1:05
  faster interface over a deeper understanding of human behavior.
• 1:08
  Nick Babich at UX Planet shares his method in "How to Become One
• 1:12
  of the Top 1% Most Effective Claude Code Users" for becoming
• 1:15
  a top-tier Claude Code user. He argues that effectiveness comes
• 1:19
  from structuring context. Babich highlights iterative feedback
• 1:22
  loops to catch hallucinations and using the tool for
• 1:25
  architectural planning. The difference between a novice and
• 1:29
  an expert is the user's ability to refine the output. Geoff
• 1:32
  Graham at CSS-Tricks addresses AI fatigue in "Smashing AI
• 1:35
  Conference" by pointing to the Smashing AI Conference. He
• 1:38
  argues that the noise surrounding the hype spectrum
• 1:41
  often obscures the practical utility of AI in development.
• 1:44
  The conference prioritizes thoughtful consideration over
• 1:47
  hype, focusing on AI's role in design systems. Graham
• 1:50
  emphasizes learning from experienced practitioners who
• 1:53
  demonstrate how AI translates to real-world work for designers
• 1:57
  and front-end developers. Other reads available from UX
• 2:00
  Design.cc on the value of human judgment and what AI has changed
• 2:04
  in design systems.
• 2:12
  Today's discussions circle a single friction point, where the
• 2:15
  tools we rely on for speed are quietly eroding the trust and
• 2:18
  clarity that users actually need. Over in r/uxwriting, a
• 2:21
  content designer describes a manager who bypasses their work
• 2:25
  by editing Figma files directly, leaving them feeling watched
• 2:28
  rather than trusted. This isn't just about workflow friction,
• 2:31
  it's about how the pressure to move fast can strip away the
• 2:34
  professional dignity that sustains creative work. When
• 2:37
  speed becomes the only metric, the human element of the craft
• 2:41
  gets flattened into a resource to be optimized. In
• 2:43
  r/DesignSystems, the core question is whether our design
• 2:46
  systems are readable by AI tools, or if they remain
• 2:49
  exclusively for human consumption. The argument is
• 2:52
  that current AI coding tools lack the context to interpret
• 2:55
  our proprietary components, leading to inconsistent spacing
• 2:58
  and usage. This reveals a gap in how we build, because if the
• 3:01
  machine can't read the rules, the output will drift. We need
• 3:05
  to design systems that are legible to both humans and
• 3:07
  algorithms if we want to maintain consistency in an
• 3:10
  automated workflow. In r/Design, a user shares a failed
• 3:13
  attempt at a viral laser printer t-shirt hack, where the process
• 3:17
  resulted in faded images and no color transfer. It sounds
• 3:20
  trivial, but it highlights a broader issue where we outsource
• 3:23
  our problem-solving to unverified internet trends
• 3:26
  instead of relying on tested methods. When we chase quick
• 3:29
  hacks over fundamental design principles, we end up with
• 3:32
  broken artifacts and lost time. The common thread is a reliance
• 3:35
  on shortcuts that sacrifice the deeper understanding of user
• 3:38
  needs and process integrity.
• 3:47
  The Feed and The Thread is brought to you by Chicago Camps.
• 3:50
  For a weekly and monthly exploration of the patterns and
• 3:53
  signals across UX, you can also check out Patterns and Signals
• 3:56
  at the website patterns and signals dot com. Chicago Camps
• 3:59
  will have more events in 2027. You can submit to be a speaker
• 4:02
  at a future event at Chicago Camps dot org.
• 4:12
  Russell Pinkston's microwave analogy really stuck with me
• 4:14
  today. He argues that AI is just pouring gasoline on a fire we
• 4:17
  already lit, and that fire is our obsession with outputs over
• 4:20
  outcomes. We've stopped asking what users actually need because
• 4:23
  we're too busy measuring how fast we can ship an interface.
• 4:26
  I hear that, but I think we're looking at the symptom, not the
• 4:29
  cause. The r/uxwriting community is describing a different kind
• 4:32
  of erosion. It's not just about speed, it's about trust. A
• 4:35
  manager is bypassing a content designer to edit Figma files
• 4:38
  directly because the AI tool can generate copy in seconds. The
• 4:41
  designer feels watched, not trusted. That's a relationship
• 4:44
  breakdown, not just a workflow one. That's a fair point, but
• 4:47
  look at the structural gap. In r/DesignSystems, people are
• 4:50
  asking if our components are even readable by these tools. If
• 4:53
  the machine can't interpret our proprietary rules, the output
• 4:56
  drifts. We're trying to use a hammer to fix a clock. The
• 4:58
  system wasn't built for algorithmic legibility, so the
• 5:01
  AI fills the gaps with generic, shallow solutions that look fine
• 5:04
  on the surface but fail in practice. Exactly. And that's
• 5:07
  where the "microwave" idea gets dangerous. It's not that the
• 5:10
  food is bad, it's that we stopped caring if it was cooked
• 5:12
  properly. We're prioritizing the act of production over the act
• 5:15
  of understanding. When a manager edits a file because it's faster
• 5:19
  than talking to a human, they're choosing speed over empathy.
• 5:22
  That's a cultural shift, not a technical one. So the technical
• 5:25
  fix is making our systems legible to both humans and
• 5:27
  algorithms. The cultural fix is remembering that speed is a
• 5:30
  metric, not a value. We've confused the two. We're
• 5:32
  measuring efficiency when we should be measuring impact. If
• 5:35
  the system doesn't reflect human nuance, the AI will amplify that
• 5:38
  lack of nuance. I think we need to ask how we make our process
• 5:41
  worth fitting into AI. That means building systems that are
• 5:44
  explicit, clear, and human- centered enough that the AI has
• 5:47
  no choice but to respect the intent. It's about designing for
• 5:50
  clarity, not just for consumption. So the skill we
• 5:53
  need to build isn't prompt engineering. It's the ability to
• 5:55
  articulate our design logic so clearly that both humans and
• 5:58
  machines understand the "why" behind the "what." The barrier
• 6:01
  to entry now is this articulation. Right. Clarity is
• 6:04
  the new control. If we can't explain our reasoning, we don't
• 6:07
  own the outcome. And that's a standard every designer,
• 6:09
  researcher, and strategist should be holding themselves to,
• 6:12
  regardless of the tools they use.
• 6:16
  That's The Feed and The Thread for today. We'll catch you next
• 6:18
  time!