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

Transcript

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

• 0:00
  Designers are trading screens for judgment. So the mockups
• 0:03
  don't matter anymore? Not if AI generates them, meaning your
• 0:06
  real value is the externalized process, not the pixels.
• 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: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:28
  feeds, or download our app for all the feeds and threads
• 0:31
  delivered right to your pocket.
• 0:40
  The tools that generate screens are getting faster, but the
• 0:43
  judgment that holds them together is getting harder to
• 0:46
  fake. That tension is reshaping how we work. Kai Wong at UX
• 0:49
  Design.cc makes the case in "If you can externalize your design
• 0:53
  process, you can win back your time" that externalizing your
• 0:56
  process wins back your time. The value of a designer is shifting
• 1:00
  from the screens they produce to the judgment they exercise. AI
• 1:03
  can generate mockups, but it often lacks consistency because
• 1:07
  models rely on short prompts without broader context. The
• 1:10
  solution is to define the lowest layer of workflow that runs
• 1:13
  consistently every time. By formalizing these processes, you
• 1:17
  guide AI tools to produce coherent results instead of
• 1:20
  random variations. This turns design judgment into a scalable
• 1:23
  asset rather than a bottleneck. Nick Babich at UX Planet shows
• 1:26
  how GPT-6 Astra streamlines UI workflows in "GPT-6 Astra for UI
• 1:30
  Design". He uses a three-step process to build interfaces,
• 1:33
  starting with Markdown format prompts. The key is explicitly
• 1:37
  requesting an image rather than code and providing detailed
• 1:40
  functional layouts. This approach helps designers move
• 1:43
  from exploration to refined interfaces more efficiently. It
• 1:46
  proves that structured prompting matters more than raw model
• 1:50
  power. You get better results when you speak the model's
• 1:53
  language clearly. Mathis Biabiany explores rendering lit
• 1:56
  volumetric lines in "Drawing With Light: An Exploration of
• 1:59
  Lit GPU Tubes with TSL and WebGPU" at Codrops. He critiques
• 2:02
  standard meshline libraries for lacking true surface normals.
• 2:06
  His technique defines geometry in parameter space, allowing the
• 2:09
  GPU to compute positions per frame. This enables dynamic
• 2:12
  tubes that maintain proper lighting and occlusion. It's a
• 2:16
  technical leap for real-time graphics on the web. You get
• 2:19
  realistic light interaction without sacrificing performance.
• 2:22
  Other reads today from UX Design.cc on the sycophancy trap
• 2:25
  and information architecture flaws.
• 2:35
  Designers are spending less time arguing about pixel perfection
• 2:38
  and more time defending their judgment against tools that can
• 2:41
  generate screens in seconds. Over on r/UXResearch, a senior
• 2:45
  researcher is asking how to pivot from consumer-facing work
• 2:48
  to internal operations. They're worried about losing access to
• 2:51
  traditional brand metrics and data science support, wondering
• 2:55
  what happens when the stakeholders are internal system
• 2:58
  builders rather than external customers. It's a sharp reminder
• 3:01
  that internal research often lacks the clear revenue signals
• 3:04
  we're used to, forcing us to find value in efficiency and
• 3:07
  risk reduction instead. In r/ProductDesign, someone is
• 3:10
  asking what portfolio projects actually matter now that AI
• 3:14
  handles the heavy lifting of layout and styling. They want to
• 3:17
  move beyond redesigns and replicas to show genuine
• 3:20
  problem-solving. The tension here's real, because if the tool
• 3:23
  can do the visual work, the designer's value shifts entirely
• 3:26
  to the strategy and the logic behind the decisions. Over on
• 3:30
  r/Design, a fast-food entrepreneur admits they keep
• 3:32
  filling packaging space without a clear hierarchy, leading to
• 3:36
  unsatisfied results. It's a common trap, where we prioritize
• 3:39
  fullness over clarity. When you strip away the decorative
• 3:42
  intent, you're left with whether the design actually guides the
• 3:46
  user's eye or just distracts it. Also in r/Design, a user shares
• 3:49
  an observation from Sarkhej Roza about the contradictory social
• 3:53
  norms around dress codes. Casual attire gets ignored while
• 3:56
  specific items get policed, highlighting how ambiguous
• 3:59
  appropriate behavior can be in public spaces. It's a
• 4:02
  fascinating look at how different groups enforce
• 4:04
  different standards simultaneously, reminding us
• 4:07
  that context is never just one thing. The common thread today
• 4:10
  is that execution is getting easier, but the judgment
• 4:13
  required to hold it all together is becoming the most critical
• 4:16
  skill we have.
• 4:25
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:27
  & Friday, September 17 & 18. It's an online event, so you can
• 4:30
  join from anywhere in the world! Tickets are free, thanks to the
• 4:34
  generosity of the community! If it's within your budget, you can
• 4:37
  purchase a general admission ticket for only twenty six
• 4:39
  dollars - with limited early bird tickets at only fifteen
• 4:42
  dollars. Get tickets now at Chicago Camps dot org.
• 4:52
  Nick Babich's three-step prompt structure for GPT-6 Astra
• 4:55
  suggests that the bottleneck isn't the model's intelligence
• 4:58
  but the clarity of the request. When you explicitly ask for an
• 5:01
  image layout in Markdown instead of raw code, you're essentially
• 5:04
  forcing the AI to think like a designer rather than a
• 5:06
  developer. It's a structural win. But Kai Wong's point on
• 5:09
  externalizing process cuts deeper. If you don't have a
• 5:12
  formalized workflow, that perfect prompt is just a lucky
• 5:14
  guess. The real issue is that most teams are trying to use AI
• 5:17
  to generate screens without having defined the judgment
• 5:20
  criteria that decide which screen is actually useful.
• 5:23
  You're optimizing for speed, not coherence. Exactly. The
• 5:25
  r/Design thread about fast-food packaging highlights this trap.
• 5:28
  They filled every inch of space because they thought fullness
• 5:31
  equaled value. It's the same mistake we make with AI. We
• 5:34
  treat the output as the product, ignoring that the value lies in
• 5:37
  the editorial process of deciding what gets cut. So the
• 5:40
  shift isn't about learning new prompting syntax. It's about
• 5:43
  treating design judgment as a scalable asset. If you can
• 5:45
  document why you chose one layout over another, you can
• 5:48
  train the tool to replicate that logic. Otherwise, you're just
• 5:51
  generating random variations and hoping one sticks. Which means
• 5:54
  the new senior role isn't about making the most beautiful
• 5:57
  mockups. It's about building the systems that make those mockups
• 6:00
  consistent. Right. Because if your design system can't explain
• 6:03
  its own decisions, it's not a system. It's just a wish.
• 6:07
  That's The Feed and The Thread for today. We'll catch you next
• 6:11
  time!