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

Transcript

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

• 0:00
  AI didn't delete complexity, it just moved it out of sight. So
• 0:03
  the user still pays that cost, just invisibly. Exactly, and we
• 0:07
  need to find where that hidden work is hiding.
• 0:14
  Welcome to The Feed and The Thread, brought to you by
• 0:16
  Chicago Camps. The Feed & The Thread is available online at
• 0:19
  feed and thread dot com to submit your feeds, or download
• 0:22
  our app for all the feeds and threads delivered right to your
• 0:25
  pocket.
• 0:32
  Speed used to be a competitive advantage. Now it's table
• 0:35
  stakes, and the time you save is only worth what you spend it on.
• 0:39
  We're seeing a shift where AI accelerates output, but
• 0:42
  complexity just moves to a different part of the journey.
• 0:45
  Sophie Shrimpton at UX Design.cc argues in "AI-generated UI is
• 0:49
  fast design, not UX" that AI- generated UI is fast design, not
• 0:52
  true UX. She draws a parallel to the furniture industry, noting
• 0:56
  that cheap, throwaway materials caused a four hundred and fifty
• 0:59
  percent increase in landfill waste. The digital equivalent is
• 1:02
  low-effort, disposable interfaces that lack the
• 1:05
  durability of hand-carved antiques. We risk shipping
• 1:08
  shallow solutions if we confuse speed with substance.
• 1:11
  Emadaldeen Barham at UX Planet curates fifteen tools in "15
• 1:14
  Figma Tools That Solve Problems Nobody Wants to Deal With" that
• 1:18
  solve tedious, repetitive problems. The goal is to
• 1:21
  eliminate busy work so designers can focus on strategic thinking
• 1:24
  and user-centered design. By automating minor tasks, teams
• 1:27
  reduce friction in their workflows. This frees up
• 1:30
  cognitive load for the higher- level work that actually
• 1:33
  matters. Patrick Neeman at UX Design.cc revisits Tesler's Law
• 1:37
  in "Tesler’s Law: complexity moved to a different part of the
• 1:40
  journey", arguing that AI hasn't eliminated complexity, just
• 1:43
  transferred it. The burden has shifted to users who must write
• 1:47
  specifications and review outputs, and to developers
• 1:50
  managing evaluation plumbing. This creates a new, unstaffed
• 1:53
  role for reviewers who certify AI-generated work. The
• 1:56
  complexity is still there, just hidden behind a convenient
• 1:59
  interface. Other reads available from Rosenfeld Media
• 2:02
  on machine ethics, UX Design.cc on ethical gamification, and UX
• 2:06
  Design.cc on using Jev for better user decisions.
• 2:16
  Today's discussions center on the tension between visual
• 2:19
  novelty and functional clarity, asking whether speed and polish
• 2:22
  are actually improving our work or just shifting the complexity
• 2:26
  elsewhere. Over in r/UI_Design, a designer is seeking feedback
• 2:29
  on a "neumorphic futurism" overhaul, specifically asking
• 2:32
  how to balance 3D color streaks with usable navigation. The core
• 2:36
  question is whether these heavy visual effects serve the user or
• 2:39
  just distract from the task. It's a reminder that speed in
• 2:42
  building these interfaces doesn't help if the resulting
• 2:45
  interface is hard to read. Also in r/UI_Design, someone is
• 2:49
  asking if a medical site's mix of dark hero sections and light
• 2:52
  clinical data feels consistent. The concern is that AI is
• 2:55
  accelerating the creation of these distinct visual zones, but
• 2:59
  we're not asking if the hierarchy actually helps
• 3:01
  clinicians find critical information. This highlights how
• 3:04
  AI can generate layout quickly, but it doesn't solve the
• 3:07
  underlying problem of information architecture. In
• 3:10
  the same subreddit, a designer is wondering if interfaces are
• 3:14
  converging into a single generic look, or if another major shift
• 3:17
  is coming. The fear is that tools are making it too easy to
• 3:20
  copy the same gradients and card styles, leading to visual
• 3:24
  sameness. This suggests that while we can produce more
• 3:26
  designs faster, the differentiation is disappearing,
• 3:29
  leaving us with a sea of similar options. Over in r/UI_Design, a
• 3:33
  user is marveling at Airbnb's tap animations, comparing them
• 3:36
  to opening a tiny passport. Teams manage to ship this level
• 3:39
  of polish into production despite the time it takes. It's
• 3:43
  a stark contrast to the rapid generation tools we have,
• 3:46
  reminding us that human craft still holds value in the
• 3:49
  details. In r/hci, a prospective PhD student is
• 3:51
  looking for "safe backup" programs, noting their lack of
• 3:54
  coding experience. This reflects a broader anxiety about where
• 3:58
  the field is heading, and whether traditional research
• 4:01
  paths are still viable when tools are changing so fast. It's
• 4:04
  a moment of uncertainty about what skills actually matter in
• 4:07
  the long run. Ultimately, today's threads reveal that
• 4:10
  while we can move faster and look better, we're still
• 4:13
  struggling to define what makes an interface truly good beyond
• 4:16
  the surface.
• 4:24
  The Feed and The Thread is brought to you by Chicago Camps.
• 4:27
  For a weekly and monthly exploration of the patterns and
• 4:30
  signals across UX, you can also check out Patterns and Signals
• 4:34
  at the website patterns and signals dot com. Chicago Camps
• 4:37
  will have more events in 2027. You can submit to be a speaker
• 4:40
  at a future event at Chicago Camps dot org.
• 4:49
  Sophie Shrimpton's comparison of AI-generated interfaces to cheap
• 4:52
  furniture that ends up in landfill is the detail that
• 4:55
  stuck with me today. It's not just about speed, it's about the
• 4:58
  material value of the work itself. That's a sharp way to
• 5:01
  put it, but I think it misses the danger here. The issue isn't
• 5:04
  that the interface is cheap. The issue is that we're treating
• 5:06
  "fast" as a substitute for "understood." Exactly. And if
• 5:09
  you look at the broader feed, Patrick Neeman's point about
• 5:12
  Tesler's Law reinforces this. The complexity hasn't vanished.
• 5:15
  It's just moved. Now it sits with the user, who has to verify
• 5:18
  the output, and the developer, who has to manage the evaluation
• 5:21
  plumbing. So we're shifting the labor. We're taking the
• 5:24
  cognitive load of design and dumping it onto the person
• 5:26
  trying to use the product. That's not efficiency. That's
• 5:29
  just a different kind of friction. And here's where I
• 5:32
  think the field has an opportunity. If we accept that
• 5:34
  complexity is just moving, then the new skill is curation. It's
• 5:37
  the ability to look at a rapid prototype and ask, "does this
• 5:40
  hold up?" I agree that curation is key, but I worry we're making
• 5:43
  it sound like a passive act. It's active resistance against
• 5:46
  the pressure to ship. We need to build the habit of stopping
• 5:49
  before the polish happens. So the metric is how much trust you
• 5:52
  can build in the user. Precisely. The value is in the
• 5:54
  judgment.
• 5:57
  That's The Feed and The Thread for today. We'll catch you next
• 6:00
  time!