Latest / The Feed & The Thread / The Feed & The Thread - March 8, 2026

Transcript

The Feed & The Thread - March 8, 2026 · The Feed & The Thread

• 0:00
  Nick DiLallo says firing UX writers is a losing move for
• 0:02
  everyone. But companies are cutting those roles to save
• 0:05
  money right now. And the bill comes due with confused users
• 0:08
  and higher support costs down the road. So the savings for
• 0:12
  today are just gonna create a mess tomorrow. Let's get into
• 0:15
  it.
• 0:19
  Welcome to The Feed and The Thread, brought to you by
• 0:21
  Chicago Camps. There's an open call for speakers for UX Camp
• 0:24
  Summer on May 30th, so now is your chance to get on stage and
• 0:27
  share your ideas! You can use our Proposal Counselor to help
• 0:30
  you get submitted today. The Feed & The Thread is available
• 0:32
  online at feed and thread dot com to submit your feeds, or
• 0:35
  download our app for all the feeds and threads delivered
• 0:38
  right to your pocket.
• 0:46
  Today's Feed tackles the gap between data points and real
• 0:49
  impact, plus the hidden cost of cutting writing roles. A
• 0:52
  statistically significant result doesn't mean it matters. Rachel
• 0:56
  Banawa argues in "Statistical Significance Isn't the Same as
• 0:59
  Practical Significance," at Nielsen Norman Group, that big
• 1:02
  sample sizes can flag tiny, useless differences as
• 1:05
  important. This rewrites the assumption that a p-value alone
• 1:09
  justifies a design change. Freezing headers and columns
• 1:12
  changes how we read complex survey data. Jim Lewis
• 1:15
  demonstrates this in "Banner Table Demo," at MeasuringU,
• 1:18
  showing how frozen rows let users compare metrics across
• 1:21
  demographics without losing context. And here's the catch:
• 1:24
  the free version of TablePress still lacks independent vertical
• 1:28
  scrolling. Removing writers from design teams makes products
• 1:31
  clunkier and erodes trust. Nick DiLallo writes in "When design
• 1:35
  teams get rid of writers, nobody wins," at UX Design.cc, that
• 1:38
  engineers can't simply replace the specific expertise needed to
• 1:42
  craft tone. Without that specialist, brand voice drifts
• 1:45
  and support costs rise. Also publishing recently: UX Planet
• 1:48
  and Chicago Camps.
• 1:56
  The community is asking some uncomfortable questions this
• 1:59
  week. A senior designer with twenty years in the field just
• 2:03
  threw a grenade. "UX does not exist," is the post over on
• 2:06
  r/UXDesign, and the argument is that the whole discipline is a
• 2:09
  corporate construct built to serve revenue, not users. The
• 2:12
  community is split. One commenter puts it bluntly: we
• 2:15
  live in a capitalist hellscape, sure, but also, it's just a job.
• 2:19
  Another pushes back harder: good UX can still be a dark pattern.
• 2:22
  They argue we keep confusing UX with ethics, and those are not
• 2:26
  the same thing. That distinction matters because it changes how
• 2:29
  we talk about responsibility in what we build. On the freelance
• 2:33
  side, a designer over on r/UXDesign is asking how solo
• 2:36
  practitioners actually manage the business of design. The post
• 2:39
  is called "How do freelance designers manage their work,"
• 2:42
  and the real tension is that everyone seems to be duct-taping
• 2:46
  together Figma, Google Drive, and Notion instead of having a
• 2:49
  real system. Comments are still rolling in on that one.
• 2:52
  Meanwhile, someone over on r/DesignSystems built a CLI tool
• 2:55
  that generates design system specifications as skill files
• 2:58
  for AI coding assistants. "I built a CLI tool to generate
• 3:02
  design system specifications," is the thread, and the idea is
• 3:05
  to force AI tools like Claude Code to follow your design
• 3:08
  system constraints instead of guessing. It is early, but the
• 3:11
  concept of encoding design decisions as machine-readable
• 3:14
  rules is worth watching. Bit of a restless energy in the
• 3:17
  community this week.
• 3:26
  Chicago Camps is hosting UX Camp Summer on Saturday, May 30th.
• 3:29
  There's an open call for speakers so submit your idea
• 3:31
  today! It's an online event, so you can join from anywhere in
• 3:34
  the world! Tickets are free, thanks to the generosity of the
• 3:37
  community! If it's within your budget, you can purchase a
• 3:40
  general admission ticket for only thirteen dollars and fifty
• 3:43
  cents. Get tickets now at Chicago Camps dot org.
• 3:53
  The piece on statistical significance really stuck with
• 3:55
  me, especially Rachel Banawa's point that a p-value alone
• 3:58
  doesn't justify a design change. That's the trap, isn't it? We
• 4:01
  see a tiny difference flagged as significant because of a huge
• 4:04
  sample size, and we rush to fix something that doesn't actually
• 4:07
  matter. Exactly, and that's why I think this is a silver lining
• 4:10
  for the field. It forces us to stop chasing numbers and start
• 4:13
  asking about practical impact on the user. I get the logic, but I
• 4:17
  worry about the pressure from stakeholders who just want a
• 4:20
  green light from the data. Telling them a result is
• 4:22
  statistically real but practically useless feels like a
• 4:25
  losing battle. It's a hard sell, sure, but if we don't make that
• 4:28
  distinction, we're just optimizing for vanity metrics
• 4:31
  instead of real product value. And that's where the risk lies.
• 4:34
  If we ignore the cost of implementing these tiny changes,
• 4:36
  we burn team morale on work that delivers zero real benefit. So I
• 4:40
  see this as a necessary filter to protect our time, while you
• 4:43
  see it as another hurdle in a system that rewards speed over
• 4:46
  substance. That's fair. I just think until the metrics change,
• 4:49
  that filter is going to feel like a roadblock rather than a
• 4:52
  safety net.
• 4:54
  That's The Feed and The Thread for today. We'll catch you next
• 4:57
  time!