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

Transcript

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

• 0:00
  Designers are swapping coding for constant context switching.
• 0:03
  So the burnout isn't about volume, it's cognitive load.
• 0:05
  It's the fatigue of verifying machine work, and we're digging
• 0:09
  into that.
• 0:13
  Welcome to The Feed and The Thread, brought to you by
• 0:16
  Chicago Camps. The Feed & The Thread is available online at
• 0:18
  feed and thread dot com to submit your feeds, or download
• 0:21
  our app for all the feeds and threads delivered right to your
• 0:24
  pocket.
• 0:32
  Influence is shifting from logic to belonging, from human
• 0:35
  intuition to model precision, and from static content to
• 0:38
  living systems. These three stories map the new terrain
• 0:41
  where design practice meets institutional reality. Kai Wong
• 0:45
  at UX Design.cc argues in "What being the new kid taught me
• 0:48
  about persuasion as a designer" that persuasion isn't about
• 0:51
  winning a debate, it's about speaking to a team's identity.
• 0:55
  Drawing on the idea that a story is a deal, Wong suggests that
• 0:58
  designers earn respect by aligning solutions with how the
• 1:02
  group sees itself, rather than just proving the data is right.
• 1:05
  This reframes office politics as a storytelling discipline, where
• 1:09
  your position as the new kid becomes a strategic asset for
• 1:12
  building trust. Nick Babich at UX Planet tests the limits of
• 1:16
  "Claude Fable 5.2 for UI Design: Better, but at What Cost?",
• 1:19
  asking if the latest model update is worth the cost. Babich
• 1:23
  finds that while the model handles complex reasoning well,
• 1:26
  it comes with specific trade- offs for standard UI tasks. The
• 1:29
  analysis reveals that optimizing for autonomous agent workflows
• 1:33
  can make the tool less effective for straightforward mobile app
• 1:37
  flows, forcing designers to weigh capability against
• 1:40
  practicality. Geoff Graham at CSS-Tricks details the version
• 1:43
  twenty update in "CSS-Tricks, Version 20", which is less a
• 1:46
  redesign and more a cleanup. Graham describes excavating
• 1:50
  ghosts like unused JavaScript and retiring the forum to reduce
• 1:53
  database bloat. By replacing outdated tools with modern
• 1:56
  practices and using AI for a security audit, the site becomes
• 2:00
  faster and easier to maintain, proving that iterative rollups
• 2:03
  often outperform full overhauls. Also out today: UX Design.cc on
• 2:07
  the politics of new media and UX Planet on fixing Claude Code's
• 2:11
  biggest problems.
• 2:19
  Today's conversations range from the anxiety of AI-driven
• 2:22
  workflow changes to the practical challenge of managing
• 2:25
  client data, highlighting a field that's actively redefining
• 2:28
  its core skills. Over on r/Design, a contractor describes
• 2:31
  the mental fatigue that comes with switching from manual
• 2:34
  coding to managing AI tools. The role is shifting from building
• 2:38
  interfaces to reviewing outputs, which demands constant context
• 2:41
  switching. This creates a new kind of burnout that isn't about
• 2:45
  volume, but about the cognitive load of verifying machine-
• 2:48
  generated work. In r/Design, a junior designer is asking for
• 2:51
  advice on how to systematically collect data from clients
• 2:54
  without forgetting follow-ups. This is a common pain point in
• 2:57
  agency work, where the lack of a standardized process for data
• 3:01
  collection leads to gaps in research. A simple checklist or
• 3:04
  a structured intake form can solve this, but the question
• 3:07
  reveals that many teams still rely on memory rather than
• 3:10
  system design. Also in r/Design, a designer is seeking
• 3:13
  resources to move beyond intuitive color choices and
• 3:16
  understand the underlying principles. This request signals
• 3:19
  a desire for deeper technical fluency, moving past "it looks
• 3:22
  good" to understanding why certain palettes work in
• 3:25
  specific contexts. It's a reminder that foundational
• 3:28
  skills remain critical, even as tools become more automated.
• 3:31
  The common thread here is the shift from manual execution to
• 3:34
  strategic oversight, whether that means auditing AI code or
• 3:38
  systematizing client data.
• 3:46
  The Feed and The Thread is brought to you by Chicago Camps.
• 3:49
  For a weekly and monthly exploration of the patterns and
• 3:52
  signals across UX, you can also check out Patterns and Signals
• 3:55
  at the website patterns and signals dot com. Chicago Camps
• 3:58
  will have more events in 2027. You can submit to be a speaker
• 4:01
  at a future event at Chicago Camps dot org.
• 4:10
  So, Kai Wong's piece on persuasion really stuck with me,
• 4:13
  specifically the idea that a story is a deal. It's not about
• 4:16
  winning the debate with data, it's about aligning your
• 4:18
  solution with how the team sees itself. That's a shift from
• 4:21
  logic to belonging, which is a huge move for how we operate. I
• 4:24
  hear the appeal of that, but I'm worried we're romanticizing
• 4:27
  office politics. If persuasion is just about fitting into a
• 4:30
  group's identity, where does the hard push for better user
• 4:32
  outcomes go? I've seen teams get stuck in a comfortable loop
• 4:35
  because everyone felt heard, but the product didn't actually
• 4:38
  improve. That's a fair concern, but Wong isn't saying we drop
• 4:41
  the evidence. They're saying the evidence has to be framed in a
• 4:44
  way that respects the group's existing narrative. It's about
• 4:47
  trust. If you walk in as the new kid, you have less authority, so
• 4:50
  you build credibility by speaking their language
• 4:52
  directly. I think that's where the effort lies. It's not just
• 4:55
  speaking their language, it's translating our constraints into
• 4:58
  their values. But here's the thing, I've seen junior
• 5:01
  designers get burned by trying to be too diplomatic. They end
• 5:03
  up compromising on accessibility or performance just to keep the
• 5:06
  peace. And that's the trade- off. You're optimizing for
• 5:09
  adoption, which can sometimes mean accepting a lower bar. But
• 5:12
  if the stakeholder doesn't buy in, the project fails anyway. So
• 5:15
  maybe the goal is progress that the team can actually sustain.
• 5:18
  I'd push back on that. Progress that ignores user pain isn't
• 5:21
  progress, it's just maintenance. We need to be careful that we
• 5:24
  don't confuse being liked with being effective. The goal should
• 5:27
  be a product that works for the people using it, even if the
• 5:30
  team has to change their minds to get there. I think the key
• 5:32
  is that belonging doesn't mean surrendering standards. It means
• 5:35
  finding the overlap where the team's identity and the user's
• 5:38
  needs actually align. That's where persuasion succeeds.
• 5:41
  Exactly. We need to build the muscle to find that overlap
• 5:44
  without losing our footing. It's strategic alignment that serves
• 5:47
  as the foundation for effective collaboration. That's the skill
• 5:50
  we need to develop next.
• 5:53
  That's The Feed and The Thread for today. We'll catch you next
• 5:56
  time!