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

Transcript

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

• 0:00
  We're replacing hard meetings with AI to avoid conflict. But
• 0:03
  isn't that just hiding the work? Exactly, because sense-making
• 0:06
  only works when it's truly collective.
• 0:12
  Welcome to The Feed and The Thread, brought to you by
• 0:15
  Chicago Camps. Leadership By Design is on Thursday and
• 0:17
  Friday, September 17 and 18 and tickets are available now! And
• 0:20
  while you're at it, get caught up on UX fundamentals with five
• 0:23
  minute UX at five em UX dot com. The Feed & The Thread is
• 0:26
  available online at feed and thread dot com to submit your
• 0:29
  feeds, or download our app for all the feeds and threads
• 0:32
  delivered right to your pocket.
• 0:40
  We trade friction for speed, assuming the tools will do the
• 0:44
  heavy lifting. But avoiding difficult conversations often
• 0:47
  creates deeper problems downstream. Pavel Samsonov at
• 0:50
  Product Picnic argues in "Sense- making is only productive when
• 0:53
  it is collective" that sense- making only works when it's
• 0:56
  collective. He challenges the trend of using AI to skip
• 0:59
  meetings, noting that poor collaboration leads to mangled
• 1:03
  product visions. LLMs might offer an escape from
• 1:05
  interpersonal friction, but they foster isolation and reduce your
• 1:09
  influence over execution. We risk automating decisions while
• 1:12
  losing the shared understanding that makes work productive.
• 1:15
  Kevin Muldoon at UX Design.cc critiques color scales in "Stop
• 1:19
  using OKLCH lightness for your color scale", specifically
• 1:22
  advising against using Oklch lightness. The Oklab space was
• 1:25
  built to fix muddy grays and hue shifts in gradients, yet
• 1:28
  applying its lightness metric for scales creates new issues.
• 1:32
  Ottosson designed it for image processing, not necessarily for
• 1:35
  systematic color palettes. Designers must understand the
• 1:38
  original intent of a tool before applying it to a different
• 1:41
  problem. Jeffrey Zeldman shares a quiet moment in "Her Glamorous
• 1:45
  Life", observing his cat Snow White resting on the sofa. She
• 1:48
  nestles her face between her paws, ignoring attention or
• 1:51
  food, offering a stillness that contrasts with professional
• 1:55
  urgency. This brief narrative highlights the value of
• 1:58
  mindfulness and personal connection outside of work. In
• 2:01
  high-pressure careers, these small pauses are necessary for
• 2:04
  mental health and empathy. Other articles today from UX
• 2:07
  Design.cc on AI designer roles and vibe-coded portfolios.
• 2:17
  Designers are trading friction for speed, assuming tools will
• 2:20
  do the heavy lifting, while avoiding the difficult
• 2:23
  conversations that create deeper problems downstream. Over on
• 2:26
  r/hci, a graduate student is asking how to choose a
• 2:29
  dissertation topic that balances academic value with future
• 2:32
  industry relevance. They're looking at rapidly evolving
• 2:35
  fields like online communities, mental health, and large
• 2:37
  language models. The tension here's real because we often
• 2:40
  avoid the hard work of defining scope, hoping the tool or the
• 2:43
  trend will make the decision for us. But picking a topic that
• 2:47
  matters for both research and your career requires facing the
• 2:50
  uncertainty head on, rather than letting the speed of innovation
• 2:53
  dictate your path. In r/hci, a rising sophomore is weighing
• 2:56
  whether to major in user experience with a technical
• 2:59
  minor, or vice versa, aiming for product design roles. They're
• 3:02
  worried about the competitive entry-level market and the
• 3:05
  return on investment of a pure design degree. This highlights a
• 3:08
  fear that technical skills are the only safety net, which can
• 3:11
  lead us to skip conversations about what design actually
• 3:14
  brings to the table. We need to value the design perspective
• 3:17
  itself, not just its ability to mimic engineering workflows.
• 3:20
  Over on r/ProductDesign, a designer with two years of
• 3:23
  experience is asking if software development knowledge is now
• 3:26
  mandatory for transitioning into product design. They feel
• 3:29
  overwhelmed by the rise of AI coding tools and the expectation
• 3:32
  that designers must ship end-to- end products. This anxiety
• 3:35
  drives us to adopt tools that promise speed, but it often
• 3:38
  means we stop having honest conversations about role
• 3:40
  boundaries and team collaboration. Knowing how to
• 3:43
  code helps, but it shouldn't replace the need to define clear
• 3:46
  responsibilities. In r/ProductDesign, a researcher is
• 3:49
  asking how people use everyday products in unintended ways,
• 3:52
  framing these behaviors as valuable data points for
• 3:54
  understanding user ingenuity. This shifts the focus from
• 3:57
  fixing errors to understanding adaptation, which is a crucial
• 4:00
  conversation we often skip because it's harder to quantify.
• 4:03
  Recognizing that users repurpose tools reveals needs that
• 4:06
  standard usability tests might miss, and it reminds us to look
• 4:09
  deeper than the surface level of interaction. We're seeing a
• 4:12
  pattern where the drive for efficiency is replacing the
• 4:15
  depth of understanding, whether in education, role definition,
• 4:18
  or research methods.
• 4:27
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:30
  & Friday, September 17 & 18. It's an online event, so you can
• 4:32
  join from anywhere in the world! Tickets are free, thanks to the
• 4:36
  generosity of the community! If it's within your budget, you can
• 4:39
  purchase a general admission ticket for only twenty six
• 4:41
  dollars - with limited early bird tickets at only fifteen
• 4:44
  dollars. Get tickets now at Chicago Camps dot org.
• 4:54
  Samsonov's point about collective sense-making hits
• 4:56
  hard when you look at the r/ProductDesign thread where
• 4:59
  junior designers are panicking that they need to learn software
• 5:02
  engineering. We're treating AI as a bridge across role
• 5:04
  boundaries, but it's actually widening the gap in shared
• 5:07
  understanding. If you automate the handoff, you lose the
• 5:09
  friction that aligns the team. That friction is exactly what
• 5:12
  people are trying to escape. The anxiety in that thread isn't
• 5:15
  just about coding skills, it's about the fear that if you can't
• 5:18
  ship the code yourself, you're irrelevant. But Samsonov is
• 5:21
  right that skipping the meeting to let the LLM draft the spec
• 5:24
  creates a mangled vision. You might save time on the doc, but
• 5:26
  you lose influence over the execution. And that's the
• 5:29
  systemic trap. We trade interpersonal friction for
• 5:31
  speed, assuming the tool does the heavy lifting. But without
• 5:34
  that difficult conversation, the product vision becomes a black
• 5:37
  box. The designer stops being a collaborator and starts being a
• 5:40
  prompt engineer for a process they don't control. It's not
• 5:43
  efficiency, it's isolation. I see it as a failure of role
• 5:45
  definition rather than just tool abuse. The community is asking
• 5:48
  if coding is mandatory because no one is defining what the
• 5:51
  designer's job actually is anymore. If the answer is "ship
• 5:54
  the product," then yes, you need to code. If the answer is
• 5:56
  "define the experience," you need to talk to the engineer.
• 5:59
  The tool doesn't fix the lack of clarity. So the risk isn't the
• 6:02
  AI, it's the ambiguity. When we stop negotiating meaning in real
• 6:05
  time, we automate decisions without shared context. The
• 6:08
  downstream problem isn't a bad feature, it's a team that
• 6:10
  doesn't know why they built it. The work isn't writing better
• 6:13
  prompts. It's building the organizational muscle to
• 6:15
  disagree, align, and move forward together, even when the
• 6:18
  tools make it tempting to just go it alone.
• 6:22
  That's The Feed and The Thread for today. We'll catch you next
• 6:25
  time!