Latest / The Feed & The Thread / The Feed & The Thread - July 1, 2026

Transcript

The Feed & The Thread - July 1, 2026 · The Feed & The Thread

• 0:00
  Accessibility isn't a feature. It's an operational capability.
• 0:03
  So we treat it like security, not a checklist. That shift
• 0:06
  means your design process changes every single day, not
• 0:09
  just before launch.
• 0:15
  Welcome to The Feed and The Thread, brought to you by
• 0:17
  Chicago Camps. Leadership By Design is on Thursday and
• 0:20
  Friday, September 17 and 18 and tickets are available now! And
• 0:23
  while you're at it, get caught up on UX fundamentals with five
• 0:25
  minute UX at five em UX dot com. The Feed & The Thread is
• 0:28
  available online at feed and thread dot com to submit your
• 0:31
  feeds, or download our app for all the feeds and threads
• 0:34
  delivered right to your pocket.
• 0:42
  We're building systems that guess, not decide. That shift
• 0:46
  from certainty to probability changes everything about how we
• 0:49
  design for trust. Taras Bakusevych lays out thirty-nine
• 0:52
  principles in "39 principles for designing human-AI interaction"
• 0:56
  at UX Design.cc. He argues that product quality depends on
• 0:59
  managing uncertainty, not just model capability. Since failure
• 1:02
  is the default in AI, your interface needs to support
• 1:05
  graceful error recovery. We can't just ship the model and
• 1:09
  hope for the best. Mikhail Prosmitskiy warns in "Why
• 1:12
  Accessibility Is An Operational Capability, Not A Feature" at
• 1:15
  Smashing Magazine that accessibility is an operational
• 1:18
  capability, not a feature. Static audits create compounding
• 1:21
  debt as products evolve. AI- generated UI often defaults to
• 1:25
  non-semantic div elements instead of proper HTML controls.
• 1:28
  Without systemic engineering changes, we're speeding up the
• 1:31
  accumulation of inaccessibility. Scott Berkun draws creativity
• 1:35
  lessons from the Eiffel Tower in "Creativity lessons from The
• 1:38
  Eiffel Tower" on his blog. He challenges the lone genius myth
• 1:42
  by showing how Gustave Eiffel relied on collaborative
• 1:45
  engineering. Eiffel even invested his own fortune when
• 1:48
  government funding fell short. Innovation requires personal
• 1:51
  conviction and the willingness to face public resistance.
• 1:54
  Other reads today include A List Apart on designing for dead
• 1:58
  languages, Silicon Valley Product Group on product-company
• 2:01
  misalignment, and Rosenfeld Media on the Shift 2026
• 2:04
  conference.
• 2:12
  Designers are wrestling with a new reality today. The work is
• 2:15
  shifting from certainty to probability, and that changes
• 2:18
  how we build trust. Over on r/UXDesign, a lead is asking how
• 2:22
  to adapt processes when AI handles the visualization. The
• 2:25
  tool generates the interface, so the designer must synthesize the
• 2:29
  meaning. This moves the value away from making things look
• 2:32
  good. It moves it toward making sense of chaos. We're building
• 2:36
  systems that guess rather than decide. That shift demands we
• 2:39
  design for probability, not just pixels. In r/UXDesign, someone
• 2:43
  shared a portfolio built with AI coding tools. The silence around
• 2:47
  it's telling. It raises a quiet question about authorship and
• 2:50
  proof of skill. If the tool builds the artifact, what proves
• 2:54
  the designer's judgment? We're moving into a space where the
• 2:57
  output is easy, but the intent is hard to verify. Trust now
• 3:00
  relies on the process, not just the final image. Also on
• 3:04
  r/UXDesign, the question is whether platforms have an
• 3:07
  ethical duty to prevent crime. It's not just about neutrality.
• 3:10
  It's about complicity. When an interface enables harm, is the
• 3:14
  design neutral? We have to consider that probability models
• 3:17
  might predict risk, but human judgment must decide the
• 3:20
  boundary. That's where trust lives. Over on r/UXDesign, a
• 3:23
  lead is struggling with being the sole designer for eight
• 3:27
  developers. They're excluded from sprint planning, treating
• 3:30
  design as a handoff. This disconnect creates
• 3:33
  implementation mismatches. It reveals a tension between speed
• 3:36
  and collaboration. When design is siloed, the system fails to
• 3:40
  integrate. We need shared ownership, not just shared
• 3:43
  files. Finally, in r/UXDesign, a candidate asks about
• 3:46
  headphones for interviews. It seems small, but it points to
• 3:49
  the anxiety of remote presentation. Clarity matters,
• 3:52
  but so does the signal we send. We're optimizing for perception
• 3:56
  in a digital world. Every detail counts when the medium is the
• 3:59
  message. The common thread is clear. We're trading certainty
• 4:03
  for collaboration, and that requires a new kind of trust.
• 4:13
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:16
  & Friday, September 17 & 18. It's an online event, so you can
• 4:19
  join from anywhere in the world! Tickets are free, thanks to the
• 4:21
  generosity of the community! If it's within your budget, you can
• 4:24
  purchase a general admission ticket for only twenty six
• 4:27
  dollars - with limited early bird tickets at only fifteen
• 4:29
  dollars. Get tickets now at Chicago Camps dot org.
• 4:39
  The shift from certainty to probability is rewriting how we
• 4:42
  build trust. We're designing systems that guess rather than
• 4:45
  decide. That fundamental change means the interface must handle
• 4:48
  uncertainty gracefully. It's no longer about hiding errors. It's
• 4:51
  about making failure recoverable. That's where the
• 4:54
  operational reality hits hard. We can't just ship a model and
• 4:57
  hope for the best. If the default state is failure, the
• 5:00
  design has to support that failure. It's not a feature
• 5:02
  toggle. It's a structural requirement for the entire
• 5:05
  product lifecycle. Exactly. And that connects to the
• 5:08
  accessibility warning. Static audits create compounding debt.
• 5:11
  When AI generates UI, it often defaults to non-semantic div
• 5:14
  elements. We're speeding up the accumulation of inaccessibility
• 5:17
  because we treat accessibility as a checklist instead of an
• 5:20
  operational capability. So the value isn't in making things
• 5:23
  look good. The tool generates the interface. The designer's
• 5:26
  job is to synthesize the meaning. We have to move from
• 5:28
  crafting pixels to making sense of chaos. That requires a
• 5:31
  different kind of judgment. But who holds that judgment? The
• 5:34
  community thread asks if platforms have an ethical duty
• 5:37
  to prevent crime. When an interface enables harm, is it
• 5:40
  neutral? Probability models predict risk. But human judgment
• 5:43
  must decide the boundary. That's where trust actually lives.
• 5:46
  Right. The boundary isn't technical. It's editorial. We
• 5:48
  need designers who can read the room, not just the code. The
• 5:51
  skill isn't predicting what the user wants. It's deciding what
• 5:54
  the system should allow. We're moving from architects of
• 5:57
  certainty to editors of probability. And the ones who
• 6:00
  thrive will be the ones who stop designing for the happy path and
• 6:03
  start designing for the gray area.
• 6:07
  That's The Feed and The Thread for today. We'll catch you next
• 6:10
  time!