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

Transcript

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

• 0:00
  We keep shipping the same form four different times. That
• 0:03
  fragmentation is killing our user experience. Patrick Neeman
• 0:06
  says an agentic standard is the only way to fix this mess.
• 0:14
  Welcome to The Feed and The Thread, brought to you by
• 0:16
  Chicago Camps. Leadership By Design is on Thursday and
• 0:19
  Friday, September 17 and 18 and tickets are available now! And
• 0:22
  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:27
  available online at feed and thread dot com to submit your
• 0:30
  feeds, or download our app for all the feeds and threads
• 0:33
  delivered right to your pocket.
• 0:41
  The interface is dissolving. We're moving from static screens
• 0:45
  to fluid agents, but that shift leaves us fighting over who
• 0:48
  controls the look and feel, and who manages the chaos behind the
• 0:52
  curtain. Patrick Neeman at UX Design.cc argues in "The call
• 0:55
  for an agentic standard: We need to stop shipping the same form
• 0:58
  four different times" that we need an agentic standard to stop
• 1:02
  shipping the same form four different times. He highlights
• 1:05
  the tension between Google's declarative JSON, which gives
• 1:08
  clients visual control, and sandboxed HTML, which keeps
• 1:11
  styling on the server. This isn't just about code structure;
• 1:15
  it's about governance. If we don't agree on how agents
• 1:18
  render, we're just rebuilding fragmentation with new names.
• 1:21
  Luke Wroblewski writes at his own blog in "AI Agents and
• 1:24
  Layers of Abstraction" about the new layer of abstraction where
• 1:28
  users no longer need to understand the software. He
• 1:31
  introduces Intent, a tool that uses coordinator agents to
• 1:34
  delegate tasks without constant human oversight. The real shift
• 1:37
  here is trust. As we supervise hundreds of agents, the design
• 1:41
  challenge moves from interface clarity to orchestration logic,
• 1:44
  leaving the app layer behind entirely. Anders Nielsen at
• 1:47
  Baymard Institute reveals in "Telco UX Benchmark: 3,100+
• 1:50
  Performance Scores and 2,400+ Best Practice Examples" that
• 1:54
  telco UX performance is rated poor across three thousand
• 1:57
  scores. Only AT&T reached a mediocre status in this large-
• 2:00
  scale study of major providers. The data shows significant gaps
• 2:04
  in basic usability for companies like Verizon and Vodafone. It's
• 2:07
  a reminder that industry complexity doesn't excuse bad
• 2:10
  design; it just makes the baseline lower. Other articles
• 2:13
  today from UX Planet on design thinking relevance, WebAIM on
• 2:17
  accessibility questions, and Codrops on glass effects in
• 2:20
  Three.js.
• 2:28
  Practitioners are asking who manages the work when the
• 2:31
  interface disappears. The tools are changing, but the career
• 2:34
  paths and ethical lines remain fuzzy. Over on
• 2:36
  r/UserExperience, the standard career advice thread is empty
• 2:40
  today. That silence speaks volumes. When the interface
• 2:43
  dissolves into fluid agents, the old playbook for breaking into
• 2:46
  the field feels obsolete. Beginners aren't just asking for
• 2:49
  jobs anymore. They're looking for a map to a territory that
• 2:52
  hasn't been drawn yet. The tension isn't about skills. It's
• 2:56
  about identity. If the screen is gone, what's a designer actually
• 2:59
  doing. In r/UXResearch, someone asked for community groups
• 3:03
  specifically for disabled UX professionals. The request
• 3:06
  highlights a gap in our support structures. We talk about
• 3:09
  inclusive design, but we rarely build inclusive communities for
• 3:12
  the designers themselves. That question matters because it
• 3:15
  reveals who gets left behind when the industry pivots. If we
• 3:19
  can't support our own, how can we claim to design for everyone.
• 3:22
  A senior researcher in r/UXResearch is hitting a
• 3:25
  ceiling in operations. They handle budgets, tool stacks, and
• 3:28
  AI vendor analysis, yet the market treats them like entry-
• 3:31
  level support. This is the chaos behind the curtain. The
• 3:34
  strategic work is real, but the title doesn't reflect the value.
• 3:38
  It forces us to ask who decides what counts as senior work when
• 3:41
  the job description is evolving faster than the hiring manager.
• 3:45
  On r/ProductDesign, a user asked for free access to a paid icon
• 3:48
  library. It's a small request, but it touches on a bigger
• 3:51
  tension. We want premium tools without paying for them. That
• 3:55
  desire clashes with the professional standards we claim
• 3:58
  to uphold. It's not just about saving money. It's about
• 4:01
  respecting the labor behind the tools we use to build our
• 4:04
  products. A young designer in r/ProductDesign shared a
• 4:07
  portfolio project for a modern MP3 player. They stripped
• 4:10
  features to avoid pain points, focusing on usability over
• 4:13
  density. That restraint is rare. In a world of feature bloat,
• 4:16
  choosing what to remove is often harder than choosing what to
• 4:20
  add. It shows a maturity that goes beyond just making things
• 4:23
  look good. The common thread today is control. We're losing
• 4:26
  control of the interface, our careers, and even our tools. The
• 4:30
  question is whether we're building systems that serve
• 4:32
  people, or just managing the chaos for ourselves.
• 4:42
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:45
  & Friday, September 17 & 18. It's an online event, so you can
• 4:49
  join from anywhere in the world! Tickets are free, thanks to the
• 4:52
  generosity of the community! If it's within your budget, you can
• 4:56
  purchase a general admission ticket for only twenty six
• 4:58
  dollars - with limited early bird tickets at only fifteen
• 5:01
  dollars. Get tickets now at Chicago Camps dot org.
• 5:11
  The tension between Google's declarative JSON and sandboxed
• 5:14
  HTML isn't just a technical debate about code structure,
• 5:17
  it's a governance crisis waiting to happen. Patrick Neeman argues
• 5:20
  that without an agentic standard, we're simply
• 5:22
  rebuilding fragmentation with new names. And that governance
• 5:25
  piece is exactly what's missing from the community conversation.
• 5:28
  We see researchers handling vendor analysis and budgets, yet
• 5:31
  the market treats that strategic work as entry-level support. The
• 5:34
  tools are changing, but the career paths remain fuzzy.
• 5:37
  Right. If the interface dissolves into fluid agents, who
• 5:40
  controls the look and feel. Neeman says the current split
• 5:42
  leaves us fighting over visual control versus server-side
• 5:45
  styling. It's a structural problem that no amount of
• 5:48
  portfolio polish can fix. But the portfolio example from
• 5:50
  r/ProductDesign shows restraint is still a viable strategy.
• 5:53
  Stripping features to focus on usability suggests that clarity
• 5:56
  matters more than density. Maybe the solution isn't a global
• 5:59
  standard, but a return to intentional design choices.
• 6:02
  Intentionality doesn't scale without agreement on the
• 6:04
  underlying layer. If every agent renders differently, the user
• 6:07
  experience becomes a minefield of inconsistent interactions. We
• 6:10
  need a shared language for how these agents behave, not just
• 6:13
  how they look. Agreed, but that language has to include human
• 6:16
  judgment. The researcher hitting a ceiling isn't failing because
• 6:19
  they lack technical skills, they're failing because the
• 6:22
  value of their strategic oversight isn't being
• 6:24
  recognized. We need to define that value before we codify the
• 6:27
  agent. So we land on different entry points. One is technical
• 6:30
  standardization, the other is professional recognition. But
• 6:33
  both require us to stop treating the interface as a static
• 6:36
  screen. Exactly. The work shifts from building the
• 6:38
  container to defining the rules of engagement. And that's a much
• 6:41
  more durable skill than any single framework.
• 6:45
  That's The Feed and The Thread for today. We'll catch you next
• 6:48
  time!