Latest / The Feed & The Thread / The Feed & The Thread - June 21, 2026

Transcript

The Feed & The Thread - June 21, 2026 · The Feed & The Thread

• 0:00
  Your empty states are breaking usability. I thought they were
• 0:03
  just placeholders. They're actually the first impression,
• 0:05
  and we're ignoring the problems hiding there.
• 0:12
  Welcome to The Feed and The Thread, brought to you by
• 0:14
  Chicago Camps. Leadership By Design is on Thursday and
• 0:17
  Friday, September 17 and 18 and tickets are available now! And
• 0:19
  while you're at it, get caught up on UX fundamentals with five
• 0:22
  minute UX at five em UX dot com. The Feed & The Thread is
• 0:25
  available online at feed and thread dot com to submit your
• 0:27
  feeds, or download our app for all the feeds and threads
• 0:30
  delivered right to your pocket.
• 0:39
  We spend so much time polishing the final pixel that we forget
• 0:42
  to package the process. Today's Feed looks at how we prove
• 0:46
  value, not just visual taste. Zeeshan Khalid at UX Design.cc
• 0:49
  frames awards as career rocket fuel in "Your strategic guide to
• 0:53
  winning design awards". He argues that the preparation
• 0:56
  forces you to articulate impact, which is valuable practice in
• 0:59
  itself. Recognition helps you break through the noise in a
• 1:03
  crowded market. It turns a trophy into a tangible
• 1:05
  credibility signal for clients. Kai Wong at UX Design.cc says
• 1:09
  the old before-and-after format is dying in "How one of the
• 1:12
  oldest design portfolio formats needs to change in 2026". Static
• 1:16
  visuals no longer satisfy employers who want to see
• 1:19
  strategic impact. You need to show your decision-making
• 1:22
  journey, not just aesthetic improvements. This shift demands
• 1:25
  that you highlight business value over pretty pictures.
• 1:28
  Nick Babich at UX Planet outlines best practices for
• 1:31
  DESIGN.md files in "DESIGN.md Best Practices". This structured
• 1:35
  document helps AI understand your specific design system and
• 1:38
  constraints. Treating it as a source of truth prevents style
• 1:42
  drift in generated outputs. Keeping it updated stops
• 1:45
  hallucinations from breaking your brand guidelines. Other
• 1:48
  reads today from UX Planet on Claude Code structure, UX
• 1:51
  Design.cc on authorship, and CSS-Tricks on property usage.
• 2:02
  Four discussions today reveal a tension between polishing the
• 2:05
  final pixel and proving the value of the process. Over on
• 2:08
  r/UXResearch, a practitioner argues that empty states are
• 2:11
  where most usability problems actually hide. New users often
• 2:15
  freeze on a blank dashboard, creating friction that predicts
• 2:18
  churn better than task success rates do. This suggests we
• 2:21
  should recruit fresh accounts to observe those critical first
• 2:24
  ninety seconds. It's a reminder that the first impression
• 2:28
  matters more than the final output, and we often neglect to
• 2:31
  test the void before we fill it. In r/UI_Design, a first-time
• 2:34
  designer asked the community to choose between two media stack
• 2:37
  concepts without any user data. This highlights a common trap:
• 2:41
  choosing interfaces based on taste rather than evidence.
• 2:44
  Since no comments have formed yet, the question itself reveals
• 2:47
  how often we prioritize visual preference over functional
• 2:50
  validation. We need to ask which interface serves the purpose,
• 2:54
  not just which one looks cleaner. Another thread in
• 2:57
  r/UI_Design asks how to display a premium-only cooldown mode to
• 3:00
  non-paying users without hiding it completely. The challenge is
• 3:04
  showing value before purchase while maintaining a good
• 3:06
  experience. This balances business goals with user
• 3:09
  empathy, forcing us to design transparency instead of
• 3:12
  deception. It's about proving the feature's worth, not just
• 3:15
  gating access. Finally, over on r/UXResearch, a junior
• 3:18
  researcher worries about long- term employability amid team
• 3:22
  fragmentation and AI automation. The anxiety stems from seeing
• 3:25
  roles change faster than skills can adapt. This isn't just about
• 3:28
  job security; it's about defining what human insight
• 3:31
  still holds value when tools can automate persona creation. We
• 3:35
  must prove our strategic worth, not just our technical output.
• 3:38
  We're spending less time arguing about pixels and more time
• 3:41
  defending why the process itself deserves a seat at the table.
• 3:52
  Chicago Camps is hosting Leadership By Design on Thursday
• 3:55
  & Friday, September 17 & 18. It's an online event, so you can
• 3:58
  join from anywhere in the world! Tickets are free, thanks to the
• 4:01
  generosity of the community! If it's within your budget, you can
• 4:05
  purchase a general admission ticket for only twenty six
• 4:07
  dollars - with limited early bird tickets at only fifteen
• 4:10
  dollars. Get tickets now at Chicago Camps dot org.
• 4:20
  The push to replace before-and- after visuals with strategic
• 4:23
  narratives is essentially a demand for proof of value. Kai
• 4:26
  Wong argues that static images no longer satisfy employers
• 4:29
  because they hide the decision- making process. We're moving
• 4:32
  from aesthetic validation to evidence-based justification.
• 4:34
  But that creates a dangerous gap for early-career designers who
• 4:37
  haven't yet built that strategic muscle. When we stop showing the
• 4:40
  pixel work, we risk making the barrier to entry impossibly
• 4:43
  high. It's not just about being pretty anymore, it's about being
• 4:46
  a business consultant who happens to design. And that's
• 4:49
  exactly why the DESIGN.md file matters so much. If you can't
• 4:52
  articulate your constraints in a structured document for AI, you
• 4:55
  certainly can't articulate your value in a portfolio. Treating
• 4:58
  the design system as a source of truth prevents style drift, but
• 5:01
  it also proves you understand the logic behind the look. I
• 5:04
  see it differently. The DESIGN.md is a technical
• 5:06
  constraint, but the portfolio is a human story. One prevents
• 5:09
  hallucinations in code, the other prevents assumptions in
• 5:12
  hiring. We need to stop treating documentation as a chore and
• 5:15
  start treating it as our primary communication tool. So the real
• 5:18
  shift isn't just visual. It's structural. We're trading visual
• 5:21
  taste for systemic clarity. Right. And until we value the
• 5:23
  architecture of the process over the polish of the output, we'll
• 5:27
  keep hiring for decoration instead of strategy.
• 5:31
  That's The Feed and The Thread for today. We'll catch you next
• 5:34
  time!