Latest / The Feed & The Thread / The Feed & The Thread - April 12, 2026

Transcript

The Feed & The Thread - April 12, 2026 · The Feed & The Thread

• 0:00
  Traditional design critiques might be failing because they
• 0:03
  seek validation. So we're just patting each other on the back
• 0:06
  instead of learning? Exactly, and shifting to collective
• 0:09
  learning changes everything. So, let's unpack that.
• 0:16
  Welcome to The Feed and The Thread, brought to you by
• 0:18
  Chicago Camps. There's an open call for speakers for UX Camp
• 0:20
  Summer on May 30th, so now is your chance to get on stage and
• 0:23
  share your ideas! You can use our Proposal Counselor to help
• 0:26
  you get submitted today. The Feed & The Thread is available
• 0:28
  online at feed and thread dot com to submit your feeds, or
• 0:31
  download our app for all the feeds and threads delivered
• 0:33
  right to your pocket.
• 0:41
  The best feedback doesn't validate the designer, and the
• 0:45
  most useful stats might not mean what you think. Today's Feed
• 0:48
  challenges how we critique work and interpret data. Critique
• 0:51
  often fails because it judges the person instead of the work.
• 0:55
  Filipe Nzongo at UX Design.cc argues in "Rethinking design
• 0:58
  critique" that we must separate the designer from the design to
• 1:02
  build shared knowledge. This shift requires teams to frame
• 1:05
  feedback around user needs rather than personal validation.
• 1:08
  Small sample sizes in research create a tricky gap between
• 1:12
  what's statistically valid and what's intuitively true. Jeff
• 1:15
  Sauro and Jim Lewis at MeasuringU explain in "Credible
• 1:18
  vs. Confidence Intervals: Different Meanings but Similar
• 1:21
  Decisions" that confidence intervals describe the method,
• 1:24
  not the probability of the specific result. Understanding
• 1:28
  this distinction prevents teams from making false claims about
• 1:31
  their data. Using AI tools effectively means learning the
• 1:34
  specific commands the creators intend for you to use. Nick
• 1:38
  Babich at UX Planet shares ten tips in "10 Claude Code Tips &
• 1:41
  Tricks from Boris Cherny for Product Teams" that Boris Cherny
• 1:44
  says streamline product workflows. Adopting these
• 1:47
  creator-endorsed techniques helps teams move faster without
• 1:50
  relying on trial and error. Other reads today from UX
• 1:53
  Design.cc on future-building notes, UX Planet on Figma
• 1:57
  workflows, and Brad Frost on Storybook.
• 2:06
  Drop into the community pulse today and pick up the vibes
• 2:09
  being put down. Over on r/UI_Design, someone posted a
• 2:12
  baffling interface and asked which of us actually built it.
• 2:15
  That question cuts deeper than just frustration. It forces us
• 2:18
  to ask if we're critiquing the work or just validating our own
• 2:22
  bias against the unfamiliar. The real test is whether the
• 2:25
  feedback helps the designer or just makes the critic feel
• 2:28
  superior. In r/UXDesign, two threads split the room between
• 2:31
  seasoned professionals and early career hunters asking for
• 2:34
  portfolio reviews. The tension here's about what counts as real
• 2:37
  experience when the job market demands perfection. Experienced
• 2:41
  designers want to negotiate offers, while newcomers are
• 2:44
  still trying to prove they belong. Both groups are hunting
• 2:47
  for validation in a field that rarely gives it freely. The
• 2:50
  conversation over on r/UXDesign shifts to handling low quality
• 2:53
  research and product thinking generated by AI. One designer
• 2:56
  noted that AI is making product managers more articulate, even
• 3:00
  if their inputs are flawed. The community agrees that garbage in
• 3:03
  means garbage out, no matter how polished the output looks. We've
• 3:06
  got to stop accepting coherent nonsense just because it sounds
• 3:10
  professional. Finally, a designer on r/UXDesign is asking
• 3:13
  for coding basics to transition from pure design into a builder
• 3:16
  role. They list everything from CSS to databases, admitting that
• 3:20
  coding is no longer just a nice to have. This shift reveals a
• 3:23
  field where generalists are becoming the only option for
• 3:26
  survival. The gap between designing and building is
• 3:29
  closing, and we need to bridge it. Today's discussions show a
• 3:32
  clear divide between defending our expertise and adapting to
• 3:35
  tools that challenge it.
• 3:44
  Chicago Camps is hosting UX Camp Summer on Saturday, May 30th.
• 3:47
  There's an open call for speakers so submit your idea
• 3:49
  today! It's an online event, so you can join from anywhere in
• 3:52
  the world! Tickets are free, thanks to the generosity of the
• 3:55
  community! If it's within your budget, you can purchase a
• 3:58
  general admission ticket for only thirteen dollars and fifty
• 4:01
  cents. Get tickets now at Chicago Camps dot org.
• 4:10
  Jeff Sauro and Jim Lewis make a sharp distinction between
• 4:13
  credible intervals and confidence intervals in their
• 4:16
  latest piece. They argue that confidence intervals describe
• 4:19
  the method, not the probability of the specific result we see on
• 4:22
  the screen. That distinction matters because we're already
• 4:25
  treating polished AI outputs as facts just because they sound
• 4:28
  professional. The community on r/UXDesign is calling out
• 4:30
  garbage in, garbage out, but the output still looks coherent
• 4:33
  enough to fool a rushed team. Exactly. When the data feels
• 4:36
  intuitive but the sample size is too small, we risk making false
• 4:39
  claims about user needs. If we don't understand that the
• 4:42
  interval describes the process, we validate the wrong decisions
• 4:45
  with a false sense of security. But here's where I diverge. The
• 4:48
  problem isn't just that we misunderstand the math, it's
• 4:51
  that we've stopped trusting our own intuition when the numbers
• 4:54
  look clean. We need to stop accepting coherent nonsense just
• 4:57
  because the tool made it sound authoritative. I worry that
• 4:59
  shifting back to intuition without the math creates its own
• 5:02
  blind spots. The real danger is assuming we can spot the flaw in
• 5:05
  the data just by looking at it, when the statistical gap is
• 5:08
  often invisible to the naked eye. True, but the alternative
• 5:11
  is becoming a passive consumer of algorithmic confidence. The
• 5:14
  field needs to demand that every claim comes with a clear
• 5:17
  explanation of how the method works, not just a pretty chart.
• 5:20
  So the metric of success isn't whether we can read the chart,
• 5:23
  but whether we can explain the gap between the method and the
• 5:26
  outcome. Right. And if your team can't articulate why a
• 5:28
  result is credible, then the result itself is the real
• 5:31
  problem.
• 5:33
  That's The Feed and The Thread for today. We'll catch you next
• 5:37
  time!