Latest / The Feed & The Thread / The Feed & The Thread - March 7, 2026

Transcript

The Feed & The Thread - March 7, 2026 · The Feed & The Thread

• 0:00
  So Adrian Levy says we're still designing for a forty-year-old
• 0:03
  architecture that no longer exists. But Kate Moran just
• 0:06
  argued that real-time buttons and checkboxes are finally
• 0:09
  becoming reality. That means our entire WIMP framework is
• 0:12
  obsolete, yet we're still optimizing for it. And if we
• 0:15
  don't pivot now, we're just building for a ghost. That's
• 0:18
  where it gets interesting. Let's dive in!
• 0:24
  Welcome to The Feed and The Thread, brought to you by
• 0:26
  Chicago Camps. There's an open call for speakers for UX Camp
• 0:29
  Summer on May 30th, so now is your chance to get on stage and
• 0:31
  share your ideas! You can use our Proposal Counselor to help
• 0:34
  you get submitted today. The Feed & The Thread is available
• 0:36
  online at feed and thread dot com to submit your feeds, or
• 0:39
  download our app for all the feeds and threads delivered
• 0:41
  right to your pocket.
• 0:49
  Today's Feed tackles a hard truth: the interface maps we've
• 0:52
  mastered for forty years might soon vanish. We're still
• 0:55
  designing for a window-based architecture that no longer
• 0:59
  exists. That's Adrian Levy's argument in a piece called
• 1:02
  "You're Still Designing for an Architecture That No Longer
• 1:05
  Exists," at UX Design.cc. The future isn't about navigating
• 1:08
  menus, but stating intent while AI agents execute the work. This
• 1:12
  rewrites the assumption that users must manually find tools
• 1:15
  to get things done. And yet, we still need buttons. Kate Moran
• 1:18
  at Nielsen Norman Group, in "The Most Exciting Development in
• 1:22
  GenUI: Buttons and Checkboxes," shows how Generative UI now
• 1:25
  dynamically creates checkboxes and buttons inside chat
• 1:28
  interfaces. These aren't static designs, but real-time elements
• 1:31
  that reduce memory load and gather context instantly. It
• 1:35
  proves AI is shifting from a design assistant to a dynamic
• 1:38
  interface builder. This shift demands a new kind of
• 1:41
  leadership. Jared Spool at the Center Centre, in "Experience
• 1:44
  Strategists Approach UX Differently," introduces
• 1:47
  Experience Strategy as a discipline that connects user
• 1:50
  lives directly to executive revenue goals. It's not just
• 1:53
  about product features, but solving deep business problems
• 1:56
  through ethnographic research. That's where real impact
• 1:59
  happens. Also worth your time this week: Tami Evnin at Chicago
• 2:02
  Camps on using AI as a thought partner for design leadership,
• 2:06
  Carrie Webster at Smashing Magazine on shifting from maker
• 2:09
  to director of intent, and Declan Ivory at the Intercom
• 2:12
  Blog on how customer support teams are setting the blueprint
• 2:15
  for company-wide AI adoption.
• 2:24
  It sure does seem like the community is hitting a wall of
• 2:27
  exhaustion and looking for simple ways to just get the job
• 2:30
  done. The real tension isn't about job hunting, it's about
• 2:34
  what to actually do while you wait. "What are you doing while
• 2:37
  job hunting," over on r/UXDesign, has people sharing
• 2:40
  side projects and burnout stories. It's a raw reminder
• 2:42
  that the gap between roles is often a gap in identity.
• 2:45
  Sometimes you get a solution instead of a problem when
• 2:48
  assigned a task, and that feels wrong. "Is it common that you're
• 2:52
  presented with solution rather than a problem," over on
• 2:55
  r/UXDesign, is where the real friction lies. u/wdpgn put it
• 2:58
  bluntly: "If you unravel every single thing a PM or engineer
• 3:01
  comes to you with they'll think you're a wanker." The divide is
• 3:04
  clear: do you push back to find the real root, or do you just
• 3:07
  ship the work to keep the team moving? And for the solo
• 3:10
  practitioners out there, the isolation is real. "Advice for a
• 3:14
  UX team-of-one working in government," over on r/UXDesign,
• 3:17
  brings up the struggle of wearing every hat. You are the
• 3:20
  researcher, the designer, and the advocate all at once. It's a
• 3:23
  lonely but powerful position if you can manage the scope. The
• 3:26
  mood today feels heavy with practical survival, not just
• 3:29
  abstract theory. People are tired of perfecting footers and
• 3:32
  are focused on getting through the day.
• 3:42
  Chicago Camps is hosting UX Camp Summer on Saturday, May 30th.
• 3:45
  There's an open call for speakers so submit your idea
• 3:47
  today! It's an online event, so you can join from anywhere in
• 3:50
  the world! Tickets are free, thanks to the generosity of the
• 3:52
  community! If it's within your budget, you can purchase a
• 3:55
  general admission ticket for only thirteen dollars and fifty
• 3:58
  cents. Get tickets now at Chicago Camps dot org.
• 4:07
  I'm stuck on Kate Moran's point about Generative UI creating
• 4:10
  buttons inside chat interfaces in real time. It feels like a
• 4:13
  massive win for reducing memory load by gathering context
• 4:16
  instantly. I see the efficiency, but it ignores the exhaustion
• 4:19
  we're seeing in the community right now. People are already
• 4:22
  tired of being handed solutions instead of problems, and now the
• 4:25
  interface itself is just handing them answers. That's a fair push
• 4:28
  back, but isn't that the point of shifting from a maker to a
• 4:31
  director of intent? The tool handles the busy work so the
• 4:34
  designer can focus on the root problem. The problem is the root
• 4:37
  problem often gets buried. If a PM or engineer hands you a
• 4:40
  finished AI prototype, you can't just push back to find the real
• 4:43
  issue without looking like a roadblock. So you think this
• 4:45
  dynamic interface builder just accelerates that pressure to
• 4:48
  ship without questioning the brief? Exactly. The interface
• 4:51
  adapts to the user, but the user is just trying to survive the
• 4:54
  day without unraveling every single thing the team throws at
• 4:57
  them. I still think there's a silver lining if we treat these
• 5:00
  dynamic elements as a way to prototype intent faster, not
• 5:03
  just to finish the work. I hope you're right, but when the
• 5:06
  interface maps we've mastered for forty years vanish, I worry
• 5:09
  we lose the friction that actually forces us to think.
• 5:13
  That's The Feed and The Thread for today. We'll catch you next
• 5:16
  time!