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

Transcript

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

• 0:00
  We're redesigning the whole Human plus AI system. Not just
• 0:03
  adding a chatbot feature? Exactly, because treating it as
• 0:06
  an add-on breaks the collaboration loop we need to
• 0:08
  fix.
• 0:13
  Welcome to The Feed and The Thread, brought to you by
• 0:15
  Chicago Camps. Leadership By Design is on Thursday and
• 0:18
  Friday, September 17 and 18 and tickets are available now! And
• 0:21
  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
  The systems we design keep fighting us. Whether that's the
• 0:43
  code, the culture, or the AI itself. Today's Feed looks at
• 0:46
  how to stop wrestling with the tools and start working with the
• 0:50
  structure. Daniel Ruston at UX Design.cc makes a sharp case in
• 0:53
  "Designing the Human+AI system". He argues we're missing the
• 0:57
  point by just adding AI features. The real job is
• 0:59
  redesigning the entire human plus AI system. It's not about
• 1:02
  efficiency. It's about trust. We need clear rules for who does
• 1:06
  what. That shifts the focus from interface pixels to
• 1:09
  orchestration. And it demands we keep human empathy at the
• 1:12
  center. Because without that oversight, scale is just a
• 1:15
  faster way to fail. We've all hated writing complex CSS for
• 1:18
  staggered animations. Durgesh Pawar at Smashing Magazine
• 1:21
  offers a fix in "Advanced Tree Counting: Mathematical Layouts
• 1:24
  With `sibling-index()` And `sibling-count()`". New
• 1:27
  functions like sibling-index let's count elements naturally.
• 1:30
  No more messy nth-child workarounds. It validates what
• 1:33
  designers have wanted for years. Mathematical layouts are finally
• 1:37
  getting intuitive tools. This simplifies the code and respects
• 1:40
  the designer's intent. It's a small change that removes a big
• 1:43
  headache. Scott Berkun at On Scott Berkun's blog challenges
• 1:46
  our complaints in "The system can work for you (not against)".
• 1:50
  He says we waste energy blaming bosses or culture. But systems
• 1:53
  dictate ninety-four percent of outcomes. Individual effort
• 1:56
  rarely beats bad structure. We need to look at feedback loops.
• 2:00
  Not just symptoms. That's a hard truth to swallow. But it's the
• 2:03
  only way to actually fix things. Other articles today from
• 2:06
  Intercom on scaling teams, Codrops on gravity-based mouse
• 2:09
  trails, and CSS-Tricks on Stack Overflow.
• 2:19
  Today's discussions feel less like isolated questions and more
• 2:22
  like symptoms of a single structural friction. We're
• 2:25
  wrestling with tools that fight us, whether that's code,
• 2:28
  culture, or the AI itself. Over on r/UXDesign, a senior designer
• 2:32
  is asking if becoming a Design Engineer is the smart move for
• 2:35
  twenty twenty-six. They want to understand the architecture, not
• 2:39
  just the interface. One commenter noted that while AI
• 2:41
  speeds up the coding, the real risk is feeling overwhelmed by
• 2:45
  the unknown. It's not just about learning syntax. It's about
• 2:48
  shifting your identity from defining the problem to solving
• 2:51
  the implementation. The tension here's real. Do you double down
• 2:55
  on pure design, or do you hybridize to stay relevant in a
• 2:58
  system that increasingly demands technical fluency? In
• 3:01
  r/UXDesign, someone else is fighting a different kind of
• 3:04
  system: the remote meeting. They're stuck in verbal loops
• 3:07
  where pre-reading is rejected and engagement drops. The
• 3:10
  community advice is structural, not behavioral. Use an infinite
• 3:14
  canvas. Send visuals beforehand. Set an agenda. This connects
• 3:17
  directly to the theme. We stop wrestling with the tool when we
• 3:20
  change the structure of the collaboration. Visuals cut the
• 3:24
  noise. They align the team faster than words ever could.
• 3:27
  Over in r/uxwriting, a designer asked how to write microcopy
• 3:30
  without breaking their visual flow. There were no comments,
• 3:33
  but the question reveals a deeper truth. We treat copy as
• 3:36
  an afterthought, a separate task that interrupts the creative
• 3:40
  momentum. It shouldn't be. If the structure forces you to
• 3:43
  switch contexts constantly, the structure is broken. Good design
• 3:46
  integrates the text into the layout from the start. In
• 3:49
  r/UI_Design, a designer shared a dark-themed marketplace UI but
• 3:53
  received no feedback. It's a solitary post in a void. This
• 3:56
  highlights the isolation we often feel when seeking
• 3:59
  critique. We want validation, but we need honest structural
• 4:02
  feedback. Without it, we're just designing in a vacuum. Finally,
• 4:06
  over on r/UXDesign, a lone designer in industrial
• 4:08
  automation described a chaotic workflow. Product managers hand
• 4:12
  off vague requests. The designer has to do the discovery alone.
• 4:15
  It leads to late-stage friction. This isn't a tool problem. It's
• 4:19
  a process failure. When the system lacks clear requirements,
• 4:22
  the designer becomes the bottleneck. The common thread
• 4:25
  today is clear. We keep trying to fix symptoms with better
• 4:28
  tools, but the real issue is the underlying structure of how we
• 4:32
  work.
• 4:39
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:42
  & Friday, September 17 & 18. It's an online event, so you can
• 4:45
  join from anywhere in the world! Tickets are free, thanks to the
• 4:48
  generosity of the community! If it's within your budget, you can
• 4:51
  purchase a general admission ticket for only twenty six
• 4:54
  dollars - with limited early bird tickets at only fifteen
• 4:57
  dollars. Get tickets now at Chicago Camps dot org.
• 5:07
  Scott Berkun argues that ninety- four percent of outcomes are
• 5:10
  dictated by systems, not individual effort. It's a hard
• 5:12
  truth. We blame culture or bosses, but the structure itself
• 5:15
  is usually the problem. That systemic view hits home when you
• 5:18
  look at those remote meeting threads. People are stuck in
• 5:21
  verbal loops because the structure of the collaboration
• 5:24
  is broken. Pre-reading gets rejected. Engagement drops. It's
• 5:27
  not a behavioral issue. It's a structural one. Exactly. The
• 5:30
  community advice to use an infinite canvas or send visuals
• 5:33
  beforehand is brilliant. It shifts the load from memory to
• 5:35
  structure. But I worry we're treating the symptom. If the
• 5:38
  underlying incentive structure still rewards quick verbal
• 5:41
  consensus over deep visual alignment, the canvas just
• 5:44
  becomes another place to procrastinate. I see it
• 5:46
  differently. The canvas isn't just a tool. It's a boundary.
• 5:49
  When you force a visual agenda, you're redesigning the human
• 5:52
  plus AI system Daniel Ruston talks about. You're establishing
• 5:55
  clear rules for who does what. The tool enforces the trust.
• 5:58
  Trust is the right word. But Ruston warns that without human
• 6:01
  empathy at the center, scale is just a faster way to fail. A
• 6:04
  visual agenda can be rigid. It can shut down nuance. We need to
• 6:07
  ensure the system allows for the messy, human parts of discovery,
• 6:10
  not just the clean handoff. That's where the tension lives.
• 6:13
  We're moving from pixel-pushing to orchestration. The designer's
• 6:16
  job isn't to make the canvas pretty. It's to ensure the
• 6:19
  system captures the intent before the code is written. So
• 6:22
  the metric for success shifts. It's no longer about how fast we
• 6:25
  ship. It's about whether the system can hold the complexity
• 6:28
  of human intent without breaking. And right now, most of
• 6:30
  our workflows can't.
• 6:33
  That's The Feed and The Thread for today. We'll catch you next
• 6:37
  time!