Latest / The Feed & The Thread / The Feed & The Thread - May 13, 2026

Transcript

The Feed & The Thread - May 13, 2026 · The Feed & The Thread

• 0:00
  That blank prompt box is killing your retention. Seventy percent
• 0:03
  churn on the very first try? It's a design failure, so we're
• 0:06
  breaking down what actually keeps users engaged.
• 0:13
  Welcome to The Feed and The Thread, brought to you by
• 0:15
  Chicago Camps. Leadership By Design is on Thursday and
• 0:18
  Friday, September 17 and 18 and tickets are available now! And
• 0:21
  while you're at it, get caught up on UX fundamentals with five
• 0:24
  minute UX at five emm 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:41
  We often mistake minimalism for good design. But sometimes, that
• 0:44
  blank slate is actually a failure to guide the user.
• 0:47
  Today's Feed looks at how we measure success when we lack
• 0:50
  history, and who's actually behind the type we use. Adi
• 0:53
  Leviim at UX Design.cc makes a hard case against the empty
• 0:56
  state in AI products. In "The death of the empty state in AI
• 1:00
  products", he calls out that blank prompt box with the
• 1:03
  blinking cursor. He says it causes a seventy percent churn
• 1:06
  rate in his own extension. This isn't minimalism. It's an
• 1:09
  absence of design that ignores signifiers. We force users to
• 1:12
  invent their own starting points instead of giving them
• 1:15
  templates. That rewrites the assumption that less is always
• 1:18
  more. Jim Lewis and Jeff Sauro tackle a common research problem
• 1:22
  at MeasuringU. In "How to Interpret a Rating Scale Without
• 1:25
  Historical Data", they explain how to interpret rating scales
• 1:29
  without historical data. They note that UX scales usually skew
• 1:32
  negative. So the mathematical midpoint doesn't match the
• 1:35
  statistical median. They suggest setting the average benchmark at
• 1:39
  seventy percent of the range. This gives us a concrete way to
• 1:42
  judge usability when we don't have past numbers to compare
• 1:45
  against. John Boardley introduces a new series at I
• 1:48
  Love Typography. In "Font Faces: Nick Shinn", he interviews type
• 1:51
  designer Nick Shinn. The piece focuses on the person behind the
• 1:55
  craft. It aims to demystify the creative process through core
• 1:58
  questions. By highlighting personal nuances, we see how
• 2:01
  individual drivers shape typographic innovation. It
• 2:04
  reminds us that design is human work. Other articles today from
• 2:08
  Intercom Blog on brand changes, Codrops on canvas proposals, and
• 2:11
  CSS-Tricks on JavaScript realms.
• 2:20
  The community is talking about the gap between what we build
• 2:23
  and why it works. Over on r/UXDesign, a designer shared a
• 2:27
  hard truth after their team was cut in half. They attribute the
• 2:30
  downsizing to AI tools like Claude allowing companies to
• 2:33
  maintain output with fewer people. It's a stark reminder
• 2:36
  that efficiency isn't the same as empathy. When we mistake
• 2:39
  minimalism for good design, we risk stripping away the guidance
• 2:43
  users actually need. A blank slate isn't always clean.
• 2:46
  Sometimes it's just empty. In r/UXDesign, the conversation
• 2:49
  shifted to how we explain our jobs. One user loves the door
• 2:52
  analogy. They say their job is making sure you don't have to
• 2:55
  think about whether to push or pull. Then they add the
• 2:58
  punchline. People still assume they make doors. It highlights a
• 3:01
  persistent disconnect. We spend so much time refining interfaces
• 3:05
  that we forget to articulate the cognitive load we're removing.
• 3:08
  If you can't explain the value, the design feels invisible. And
• 3:12
  invisibility is dangerous. Over on r/UXDesign, a career changer
• 3:15
  from management consulting is feeling overwhelmed by the speed
• 3:19
  of AI integration. They're asking whether to learn Figma or
• 3:22
  jump straight into vibe coding. The tension here's real. We're
• 3:25
  measuring success without historical benchmarks. Without a
• 3:28
  foundation in traditional interaction patterns, AI-
• 3:31
  generated interfaces often lack the subtle guidance that
• 3:34
  prevents user error. You can't automate intuition. In
• 3:37
  r/uxwriting, practitioners are debating the ROI of expensive
• 3:40
  courses like UX Content Collective. One alum notes the
• 3:43
  material was good, but it won't guarantee a job. It's a
• 3:46
  cautionary tale about investing in credentials versus
• 3:49
  competence. The market is shifting. Recruiters are looking
• 3:52
  for impact, not just certificates. Over on
• 3:55
  r/UI_Design, juniors are asking how detailed their case studies
• 3:58
  should be. The anxiety is palpable. They want to balance
• 4:01
  visual polish with product thinking. But here's the thing.
• 4:04
  A portfolio isn't just a showcase. It's proof you can
• 4:07
  solve problems. If the work doesn't show impact, the
• 4:10
  platform doesn't matter. The thread reveals a field trying to
• 4:13
  define value in an era where tools do the heavy lifting. We
• 4:16
  need to remember that guidance is a feature, not a bug.
• 4:27
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:29
  & 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:35
  generosity of the community! If it's within your budget, you can
• 4:38
  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:53
  The math from that MeasuringU piece is striking. They suggest
• 4:57
  setting usability benchmarks at seventy percent of the range
• 4:59
  because scales naturally skew negative. It gives us a concrete
• 5:03
  anchor when we lack historical data. That anchor feels
• 5:05
  dangerous if we ignore the context. The r/UXDesign thread
• 5:08
  highlighted how teams cut staff while relying on AI to fill the
• 5:11
  gap. If we treat that seventy percent as a universal standard,
• 5:14
  we might mistake an empty prompt box for a successful design. I
• 5:17
  see the risk. But without a baseline, we're just guessing.
• 5:20
  The Lewis and Sauro method provides a statistical floor. It
• 5:23
  stops us from accepting mediocre usability just because we have
• 5:26
  no previous data to compare it against. But a statistical
• 5:29
  floor isn't a user experience ceiling. Adi Leviim noted that
• 5:32
  blank AI states cause seventy percent churn. The numbers might
• 5:35
  look stable on a spreadsheet, but the user is leaving because
• 5:38
  there's no guidance. We're optimizing for metrics while
• 5:41
  losing the human element. So we need to decouple the metric from
• 5:44
  the outcome. The seventy percent rule helps us judge the
• 5:47
  interface mechanics. It doesn't dictate the content strategy. We
• 5:50
  can use the benchmark to validate the scale itself, then
• 5:53
  layer on qualitative judgment for the actual user journey.
• 5:56
  That separation is where the real work happens. We stop
• 5:59
  treating the benchmark as the goal and start treating it as a
• 6:02
  diagnostic tool. The goal remains empathy, even when the
• 6:04
  tools are automated. Exactly. The benchmark tells us the
• 6:07
  instrument works. It doesn't tell us what we should build.
• 6:10
  And right now, confusing the instrument for the insight is
• 6:13
  the most expensive mistake a team can make.
• 6:17
  That's The Feed and The Thread for today. We'll catch you next
• 6:20
  time!