Latest / The Feed & The Thread / The Feed & The Thread - May 25, 2026

Transcript

The Feed & The Thread - May 25, 2026 · The Feed & The Thread

• 0:00
  You're no longer the user. So we're just principals now?
• 0:03
  Exactly. We stop clicking and start authorizing agents. We
• 0:06
  need to map this shift.
• 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: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:32
  delivered right to your pocket.
• 0:41
  The screen is disappearing. Not fading, but vanishing as the
• 0:44
  primary interface. We're moving from a world of clicks to a
• 0:47
  world of commands, and that shift breaks every rule we
• 0:50
  learned about usability. Adrian Levy at UX Design.cc makes this
• 0:54
  case in "You are no longer the user. You are the principal.".
• 0:57
  He argues that Google's recent announcements mark a hard pivot.
• 1:01
  We're no longer users operating tools. We're principals
• 1:04
  authorizing agents. Tools like Gemini Spark run in the
• 1:07
  background, making the physical screen obsolete for many tasks.
• 1:10
  This breaks our current design vocabulary. Affordances and
• 1:13
  navigation maps don't apply when the interface is invisible. We
• 1:17
  need a new language for delegated authority. Jeff
• 1:20
  Gothelf at his own blog explores this tension in "Karpathy said
• 1:23
  vibe coding is obsolete. What he described instead is product
• 1:26
  management.". He looks at Andrej Karpathy's claim that vibe
• 1:30
  coding is dead. Karpathy says agentic engineering is the new
• 1:33
  standard. But Gothelf points out a funny truth. Writing specs and
• 1:37
  inspecting diffs is just product management. The bottleneck is no
• 1:40
  longer execution. It's decision making. Engineers might call it
• 1:44
  technical work, but the core skill is prioritization. The
• 1:47
  constraint has moved from code to choice. Other articles today
• 1:50
  from UX Design.cc on bank card colors and Jeffrey Zeldman on
• 1:54
  memory.
• 2:01
  The screen is vanishing as the primary interface. We're moving
• 2:05
  from clicks to commands. That shift breaks every usability
• 2:08
  rule we learned. Over on r/UXDesign, designers are asking
• 2:11
  why SaaS products force password creation before single sign-on
• 2:15
  ships. It's a redundant friction point that stems from poor long-
• 2:18
  term planning. The tension here's immediate security
• 2:21
  theater versus actual user experience. If we're moving
• 2:24
  toward voice and command interfaces, memorizing passwords
• 2:28
  becomes obsolete faster. We need to stop designing for legacy
• 2:31
  authentication models that don't fit the new flow. In
• 2:34
  r/UXDesign, a veteran designer questions if the field has
• 2:37
  regressed to valuing visual execution over strategy. Clients
• 2:41
  often confuse user experience with graphic design. This
• 2:44
  reveals a dangerous gap between deep research and surface-level
• 2:47
  aesthetics. If the screen disappears, visual polish
• 2:50
  matters less than intent clarity. We risk losing the
• 2:53
  strategic core of the profession if we only sell pixels. Over on
• 2:57
  r/UI_Design, a creator seeks feedback on merging Newgrounds
• 3:00
  nostalgia with neon aesthetics. The result feels cluttered
• 3:03
  despite high-energy intentions. This highlights the struggle
• 3:07
  between conceptual inspiration and clean execution. When
• 3:10
  interfaces vanish, visual noise becomes even more distracting.
• 3:13
  Clarity must win over style, especially when the medium
• 3:16
  itself is fading away. In r/UI_Design, another developer
• 3:20
  shares a community site with an inconsistent sidebar style. They
• 3:23
  want to move away from a messy aesthetic. This shows the
• 3:26
  tension between experimentation and usability standards.
• 3:29
  Innovation shouldn't compromise consistency. As interfaces
• 3:33
  become invisible, trust in the system relies on predictable
• 3:36
  behavior, not novelty. The industry is fighting to preserve
• 3:39
  visual identity while the canvas itself disappears.
• 3:49
  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
  Adrian Levy argues we're shifting from users to
• 4:18
  principals. We stop operating tools and start authorizing
• 4:21
  agents. That pivot breaks our entire design vocabulary because
• 4:24
  the screen is no longer the primary interface. That shift
• 4:27
  terrifies me because trust becomes the only affordance
• 4:30
  left. When the interface is invisible, you can't rely on
• 4:33
  navigation maps. You have to rely on the system behaving
• 4:36
  predictably. If the agent makes a mistake, there's no undo
• 4:39
  button to click. Exactly. The Newgrounds thread proves that
• 4:42
  visual noise is a distraction we can no longer afford. When the
• 4:45
  medium fades, clarity must win over style. We're seeing a
• 4:48
  tension between conceptual inspiration and the need for
• 4:50
  clean execution. But clarity isn't just about removing
• 4:53
  clutter. It's about consistent behavior. The sidebar discussion
• 4:56
  shows that inconsistency kills trust faster than ugly
• 4:59
  aesthetics. Innovation shouldn't compromise the user's mental
• 5:02
  model of how the system works. So we're building a new language
• 5:05
  for delegated authority. It isn't about pixels. It's about
• 5:08
  defining the boundaries of what the agent is allowed to do on
• 5:11
  your behalf. And those boundaries need to be explicit.
• 5:14
  If we don't define them, the system defines them for us. We
• 5:17
  need to design the constraints, not just the outcomes. We're
• 5:20
  moving from designing screens to designing trust. And trust is
• 5:23
  the only interface that survives when the screen disappears.
• 5:28
  That's The Feed and The Thread for today. We'll catch you next
• 5:31
  time!