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

Transcript

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

• 0:00
  Ten thousand AI agents just solved a math problem. That
• 0:03
  scale is terrifying for coordination. We need to see how
• 0:06
  they actually talk to each other.
• 0:12
  Welcome to The Feed and The Thread, brought to you by
• 0:15
  Chicago Camps. Leadership By Design is on Thursday and
• 0:17
  Friday, September 17 and 18 and tickets are available now! And
• 0:20
  while you're at it, get caught up on UX fundamentals with five
• 0:23
  minute UX at five em 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:31
  delivered right to your pocket.
• 0:40
  We're building systems that talk to each other, but we haven't
• 0:44
  agreed on the rules of conversation. That gap creates
• 0:47
  friction between human intent and machine execution. Sharang
• 0:50
  Sharma at UX Design.cc maps this terrain in "8 voice AIUX
• 0:54
  patterns". He traces the shift from simple voice triggers to
• 0:57
  complex LLM interactions. Latency improvements now support
• 1:00
  storytelling and enterprise workflows. The real tension lies
• 1:04
  in managing the uncanny valley. Designers must choose between
• 1:07
  stylized avatars and photorealism. That choice
• 1:10
  defines how users perceive the AI's role. Luke Wroblewski
• 1:13
  explores scale in "Large Scale Agent Coordination". He looks at
• 1:17
  coordinating thousands of agents on single tasks. OpenAI recently
• 1:21
  used ten thousand agents for one math problem. Effective
• 1:24
  coordination needs structure, not just power. The Intent
• 1:27
  platform shows how isolated workspaces prevent data
• 1:30
  conflicts. Defined roles mimic human team structures.
• 1:33
  Intelligent handoffs keep the process moving. This moves us
• 1:37
  from prompting to orchestration. Jeffrey Zeldman warns of
• 1:40
  fragmentation in "AI, Disruption, and Standards". He
• 1:43
  compares today's AI landscape to the browser wars. Without
• 1:46
  standards, agents will break the web experience. Proprietary
• 1:50
  platforms threaten the separation of content and
• 1:52
  design. This separation enabled accessibility and future-
• 1:56
  proofing. AI tools often ignore those principles. We risk losing
• 1:59
  the open web to walled gardens. Other articles today from UX
• 2:03
  Planet on design critique, Codrops on digital architecture,
• 2:06
  and UX Design.cc on UX eras.
• 2:15
  Designers are asking how to organize their teams while
• 2:18
  simultaneously questioning whether the interview process
• 2:21
  still measures actual problem- solving skills. Over on
• 2:24
  r/ProductDesign, someone is digging into the structural
• 2:27
  relationship between design and engineering, specifically
• 2:30
  looking at headcount ratios and squad management layers. This
• 2:34
  isn't just about org charts. It's about defining who holds
• 2:37
  the authority when human intent meets machine execution. If the
• 2:40
  rules of conversation aren't clear, friction happens at the
• 2:44
  handoff. In r/ProductDesign, another designer is asking how
• 2:47
  problem-solving interviews have evolved with the rise of AI
• 2:50
  tools. The traditional whiteboard challenge is fading.
• 2:53
  Now, candidates can use AI assistance, which shifts the
• 2:56
  focus from raw sketching to strategic oversight. We need to
• 2:59
  know if we're hiring for execution or for direction. On
• 3:02
  r/UserExperienceDesign, the community is listing UI best
• 3:05
  practices they've abandoned, like the three-click rule or
• 3:09
  strict adherence to the fold. Real-world data is replacing
• 3:12
  rigid heuristics. This matters because evidence-based design
• 3:15
  requires us to break rules that no longer serve the user
• 3:18
  context. In r/design_critiques, a designer is seeking feedback
• 3:21
  on a workspace called Mesh, specifically how to make the
• 3:25
  handoff from whiteboard work to an AI agent feel intuitive. The
• 3:28
  core tension is discoverability. Is a command-based approach
• 3:31
  clear enough, or does the layout need to guide the user toward
• 3:35
  seeking assistance? The field is moving from defining static
• 3:38
  rules to managing dynamic conversations between humans,
• 3:41
  systems, and each other.
• 3:50
  Chicago Camps is hosting Leadership By Design on Thursday
• 3:52
  & Friday, September 17 & 18. It's an online event, so you can
• 3:55
  join from anywhere in the world! Tickets are free, thanks to the
• 3:58
  generosity of the community! If it's within your budget, you can
• 4:01
  purchase a general admission ticket for only twenty six
• 4:04
  dollars - with limited early bird tickets at only fifteen
• 4:06
  dollars. Get tickets now at Chicago Camps dot org.
• 4:16
  The math problem solved by ten thousand agents isn't just a
• 4:19
  flex on processing power. It's a structural warning. We're seeing
• 4:22
  a shift from prompting individual tools to
• 4:24
  orchestrating entire teams of digital workers, and the current
• 4:27
  lack of standards means we're building coordination protocols
• 4:30
  on sand. I see the coordination piece differently. The real
• 4:33
  friction isn't in the backend orchestration. It's in the
• 4:36
  handoff moment. That thread on Mesh highlights how designers
• 4:39
  are still trying to map human intuition onto command-line
• 4:41
  interfaces. We're asking people to type out their intent instead
• 4:44
  of guiding them through it. And that's where the browser wars
• 4:47
  comparison lands. If we treat every agent workspace as a
• 4:50
  walled garden, we lose the separation of content and logic.
• 4:53
  We need a protocol for how these agents talk to each other, not
• 4:56
  just how humans talk to them. Otherwise, we're just building
• 4:59
  proprietary silos with better chatbots. But protocols don't
• 5:02
  fix discoverability. You can have perfect standards, but if
• 5:04
  the interface doesn't tell the user when to ask for help, the
• 5:07
  system fails. The tension is between rigid structure and
• 5:10
  fluid interaction. We need design systems that adapt to the
• 5:13
  agent's confidence level, not just static rules. So we're
• 5:16
  trading execution speed for strategic oversight. The
• 5:18
  designer's job becomes defining the guardrails for the
• 5:21
  conversation, not the output itself. Exactly. The skill set
• 5:24
  is shifting from making things to managing the conditions under
• 5:27
  which things get made. We're building the infrastructure for
• 5:30
  collective intelligence. And the interface is the contract
• 5:32
  that makes it trustworthy.
• 5:36
  That's The Feed and The Thread for today. We'll catch you next
• 5:39
  time!