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

Transcript

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

• 0:00
  CEOs aren't ignoring design because they don't value it. So
• 0:03
  what's actually blocking the signal? It's noise. They're
• 0:06
  filtering out constant departmental chatter just to
• 0:08
  function. And that explains why your best work gets lost in the
• 0:12
  daily shuffle.
• 0:16
  Welcome to The Feed and The Thread, brought to you by
• 0:19
  Chicago Camps. Leadership By Design is on Thursday and
• 0:21
  Friday, September 17 and 18 and tickets are available now! And
• 0:24
  while you're at it, get caught up on UX fundamentals with five
• 0:27
  minute UX at five em UX dot com. The Feed & The Thread is
• 0:29
  available online at feed and thread dot com to submit your
• 0:32
  feeds, or download our app for all the feeds and threads
• 0:35
  delivered right to your pocket.
• 0:43
  The tools we use to build interfaces are changing how we
• 0:47
  define good design, shifting the burden from human intuition to
• 0:50
  machine-readable rules. Michael Buckley at UX Design.cc argues
• 0:54
  in "Defining ethical design for machines" that we need to
• 0:57
  translate abstract ethics into concrete DESIGN.md files. He
• 1:00
  proposes a five-pillar framework covering inclusion, autonomy,
• 1:04
  transparency, privacy, and well- being. This moves ethical
• 1:07
  guidance out of scattered visual assets and into the code itself.
• 1:11
  It means AI systems can actually enforce these values instead of
• 1:15
  just ignoring them. Scott Berkun at On Scott Berkun's blog
• 1:18
  makes a sharp case in "Why CEOs ignore design leaders" that CEOs
• 1:22
  ignore design leaders because of noise, not lack of value. He
• 1:25
  calls out the designer ego trap where complaints replace
• 1:28
  curiosity about organizational dynamics. Designers often ask
• 1:32
  why they're excluded instead of asking how decisions actually
• 1:35
  get made. Complaining sounds like selfish static to
• 1:38
  executives who are already filtering out distractions.
• 1:41
  Julie Zhuo writes at The Looking Glass about the gap between
• 1:45
  taste and execution in "Eye, Hand, AI: a letter to my
• 1:48
  daughter". She distinguishes the eye, which is taste, from the
• 1:51
  hand, which is the ability to produce work. Beginners often
• 1:55
  suffer because their high standards outpace their current
• 1:58
  skill level. True taste requires deep study of craft history, not
• 2:02
  just a desire to be unique. Without that rigorous study,
• 2:05
  what feels fresh is often just amateurish. Other reads today
• 2:08
  from UX Planet on DESIGN.md mistakes, UIE on overcoming
• 2:12
  doubt, and UX Design.cc on bottling judgment.
• 2:21
  Practitioners are hitting a wall where the metrics of success no
• 2:25
  longer match the skills they've spent years building. Over on
• 2:28
  r/UXDesign, one designer shared the exhausting reality of
• 2:31
  completing fifty interview processes and reaching six final
• 2:34
  rounds without securing a single offer. The portfolio passes the
• 2:37
  screen, the presentation impresses the panel, but the
• 2:40
  offer never comes. It suggests that the gatekeeping mechanism
• 2:43
  has shifted from evaluating visible craft to assessing
• 2:46
  intangible fit, or perhaps machine-readable compliance with
• 2:49
  rigid, unspoken rules. We're seeing a disconnect where strong
• 2:52
  work doesn't guarantee entry, leaving designers to wonder if
• 2:55
  they're failing the test or if the test itself is broken. In
• 2:58
  another thread on r/UXDesign, a senior designer asked if it's
• 3:01
  reasonable to push back against a last-minute, six-hour unpaid
• 3:05
  take-home assignment. The company swapped a portfolio
• 3:07
  review for a deep-dive case study that looks suspiciously
• 3:10
  like free production work. This isn't just about fairness; it's
• 3:14
  about whether the industry respects design as intellectual
• 3:17
  labor or treats it as disposable output. When we accept unpaid
• 3:20
  work as a standard filter, we lower the bar for what
• 3:22
  constitutes professional engagement. Over on r/UXDesign,
• 3:25
  someone looked for examples of apps that let users install
• 3:28
  widgets directly from within the interface, bypassing the
• 3:31
  standard OS settings. It's a small interaction, but it
• 3:34
  reveals a larger trend toward reducing friction in feature
• 3:37
  adoption. The question matters because it challenges the
• 3:40
  traditional boundary between app and system, asking how much
• 3:43
  control we should give users without overwhelming them. In
• 3:46
  r/hci, a PhD candidate in computer science worried that
• 3:49
  their academic background makes them unemployable in practical
• 3:52
  UX roles. They've grants and publications, but lack the
• 3:55
  portfolio pieces that hiring managers expect. This highlights
• 3:58
  the growing chasm between theoretical research and applied
• 4:01
  design, where academic rigor doesn't always translate to
• 4:04
  commercial viability. Finally, over on r/UXDesign, a junior
• 4:07
  designer expressed frustration with the lack of structured
• 4:10
  learning paths for high-level product thinking, unlike the
• 4:13
  clear algorithms in software engineering. They're searching
• 4:16
  for a way to practice strategy outside of their day job. It's a
• 4:19
  reminder that while tools change, the desire for mastery
• 4:22
  remains constant, even when the path isn't clearly mapped. The
• 4:25
  tension today is clear: we're trying to prove our value in
• 4:28
  systems that increasingly measure us by convenience rather
• 4:31
  than craft.
• 4:39
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:42
  & Friday, September 17 & 18. It's an online event, so you can
• 4:45
  join from anywhere in the world! Tickets are free, thanks to the
• 4:48
  generosity of the community! If it's within your budget, you can
• 4:51
  purchase a general admission ticket for only twenty six
• 4:54
  dollars - with limited early bird tickets at only fifteen
• 4:56
  dollars. Get tickets now at Chicago Camps dot org.
• 5:06
  Julie Zhuo's distinction between taste and execution hits a nerve
• 5:09
  when you look at Michael Buckley's proposal for DESIGN.md
• 5:12
  files. If we codify ethics into machine-readable rules, we risk
• 5:15
  turning taste into a checklist. The danger is that we optimize
• 5:18
  for compliance rather than craft, leaving the messy, human
• 5:21
  judgment out of the loop. I see it as the opposite. Right now,
• 5:24
  taste is too often a luxury good, reserved for those who can
• 5:27
  afford to iterate without constraints. By moving those
• 5:29
  values into the code, we make good judgment the default, not
• 5:32
  the exception. It levels the playing field for teams that
• 5:35
  don't have a senior design leader breathing down their
• 5:38
  necks every step of the way. But does code actually capture
• 5:41
  the nuance of taste? Zhuo argues that true taste comes from deep
• 5:44
  study of craft history, not just a desire to be unique. A
• 5:46
  DESIGN.md file can enforce transparency or privacy, sure.
• 5:49
  But can it enforce the subtlety of knowing when to break a rule
• 5:52
  for the sake of delight? Or does it just flatten everything into
• 5:55
  binary pass or fail states? Maybe we're asking the machine
• 5:58
  to do too much. The code shouldn't replace the designer's
• 6:01
  eye. It should handle the floor, the baseline of ethical
• 6:04
  behavior. That frees up the designer to focus on the
• 6:06
  ceiling, the actual craft and nuance Zhuo is talking about.
• 6:09
  It's not about replacing judgment. It's about automating
• 6:12
  the guardrails so we can actually climb higher. That's a
• 6:14
  compelling reframe. So the tool handles the hygiene factors, and
• 6:18
  the human handles the artistry. But only if the organization
• 6:20
  actually values that artistry. If the metric is speed to
• 6:23
  market, the DESIGN.md becomes a ceiling, not a floor. We end up
• 6:26
  with efficient, ethical, but soulless products because the
• 6:29
  incentive structure hasn't changed, only the tooling has.
• 6:32
  Exactly. The tool is just a lever. If you're pulling it to
• 6:35
  cut corners, you'll get corner- cutting. But if you use it to
• 6:37
  remove the cognitive load of basic compliance, you create
• 6:40
  space for the kind of rigorous study Zhuo advocates. The shift
• 6:43
  isn't in the code. It's in what we choose to spend our mental
• 6:46
  energy on once the basics are automated. We're moving from
• 6:49
  manual enforcement of standards to automated enforcement of
• 6:52
  values. And the real test isn't whether the code works. It's
• 6:55
  whether we're brave enough to let it handle the basics so we
• 6:58
  can finally get back to the hard work of making things that
• 7:01
  matter.
• 7:03
  That's The Feed and The Thread for today. We'll catch you next
• 7:06
  time!