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

Transcript

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

• 0:00
  Designers are now building interfaces for ideas that don't
• 0:03
  exist yet. So we're designing for empty space? Yes, and it's
• 0:06
  shifting how we define problems before they even surface.
• 0:13
  Welcome to The Feed and The Thread, brought to you by
• 0:15
  Chicago Camps. The Feed & The Thread is available online at
• 0:18
  feed and thread dot com to submit your feeds, or download
• 0:21
  our app for all the feeds and threads delivered right to your
• 0:24
  pocket.
• 0:31
  There's a quiet shift happening in how we define design work. We
• 0:35
  used to focus on solving known problems. Now, we're managing
• 0:38
  chaos, ambiguity, and the slow erosion of our own creative
• 0:41
  identity. Tanner Kohler at Nielsen Norman Group lays out
• 0:45
  the problem in "Context Libraries: How AI Power Users
• 0:48
  Manage Context Engineering", revealing that power users spend
• 0:51
  more time curating context libraries than writing prompts.
• 0:54
  The core issue is that AI handles the typing, yet humans
• 0:57
  still struggle to manage the institutional knowledge stored
• 1:01
  in markdown files or external tools. This means our bottleneck
• 1:04
  is no longer generation, but curation. We're building bespoke
• 1:07
  systems for stale files, and that manual effort is where our
• 1:11
  real value is being lost. Hiroshi Sato at UX Design.cc
• 1:14
  challenges the traditional focus on defined problems in
• 1:17
  "Designing for an idea before it exists". Sato uses the metaphor
• 1:20
  of empty seats to describe creating space for user
• 1:23
  behaviors that haven't yet formed. This approach requires
• 1:26
  embracing ambiguity to build interfaces that adapt to unknown
• 1:30
  futures. It's a call to design for the idea before it exists,
• 1:33
  rather than just reacting to current needs. Luke Wroblewski
• 1:36
  at LukeW's blog analyzes the trend in "The Convergence of
• 1:39
  Design", noting that distinct designs are converging toward an
• 1:43
  average form. This homogenization happens because
• 1:46
  mature technologies compete on specs, and physical constraints
• 1:49
  force similar shapes. Software is particularly susceptible to
• 1:52
  this trend, as clear purposes simplify design until unique
• 1:56
  identity fades. We're trading character for function, and that
• 1:59
  trade-off is becoming the new standard. Other reads available
• 2:03
  from Chicago Camps on performance art, Deque Blog on
• 2:05
  accessibility leadership, and UX Planet on model updates.
• 2:16
  A slider that leaves a trail as you drag it, a search for an
• 2:19
  icon set with a personality of its own beyond Lucide, and a
• 2:23
  running gripe that AI-built screens all share the same "off"
• 2:26
  look are each smaller than they seem. Every one is really the
• 2:29
  same question, where the human touch still has to show once the
• 2:33
  tool does the generating. Over on r/UI_Design, a designer is
• 2:36
  making the case that this specific micro-interaction
• 2:39
  transforms a standard range input into something playful.
• 2:42
  The argument is that small visual details prevent
• 2:45
  functional elements from feeling sterile. This matters because it
• 2:49
  challenges the assumption that utility and delight are separate
• 2:52
  goals. In r/UI_Design, someone is asking which icon library is
• 2:56
  gaining traction beyond the ubiquitous Lucide. The question
• 2:59
  is really about tooling saturation. We're looking for
• 3:02
  alternatives that offer distinct personality rather than just
• 3:06
  another set of generic glyphs. This is a search for identity in
• 3:09
  a crowded market. In r/UI_Design, a practitioner
• 3:12
  argues that AI-built apps share a recognizable "off" look. They
• 3:15
  point to inconsistent spacing and missing hover states as the
• 3:19
  primary tells. This isn't about functionality, but about the
• 3:22
  absence of human refinement. It highlights a gap between
• 3:25
  generated code and designed experience. Over on
• 3:28
  r/ProductDesign, someone asked how interview processes differ
• 3:31
  at AI companies. The lack of response is notable. It implies
• 3:35
  that the hiring landscape for these roles is still opaque and
• 3:38
  not yet standardized. Designers are navigating a new terrain
• 3:42
  without a map. Today's discussions circle back to the
• 3:45
  same core tension: the gap between what's generated and
• 3:48
  what's designed.
• 3:56
  The Feed and The Thread is brought to you by Chicago Camps.
• 3:59
  For a weekly and monthly exploration of the patterns and
• 4:02
  signals across UX, you can also check out Patterns and Signals
• 4:05
  at the website patterns and signals dot com. Chicago Camps
• 4:08
  will have more events in 2027. You can submit to be a speaker
• 4:10
  at a future event at Chicago Camps dot org.
• 4:20
  The idea of "empty seats" really stuck with me today. Hiroshi
• 4:23
  Sato argues we should design for the idea before it exists,
• 4:26
  creating space for user behaviors that haven't formed
• 4:28
  yet. It's a direct challenge to the traditional habit of just
• 4:31
  reacting to known problems. I hear that, and it sounds
• 4:34
  beautiful in theory. But when I look at the community
• 4:36
  discussions, the reality is much messier. People are still asking
• 4:39
  for validation on static layouts. They want to know which
• 4:42
  rebrand looks trustworthy right now. They aren't building for
• 4:45
  the future. They're polishing the present. That's the
• 4:48
  tension, isn't it. We have this new mandate to embrace
• 4:50
  ambiguity, but our tools are built for certainty. We're
• 4:53
  trying to hold space for the unknown while using a ruler to
• 4:56
  measure the known. It creates a weird friction where the
• 4:58
  designer feels like they have to justify doing less. And that's
• 5:01
  where I think the field is misreading the signal. It's not
• 5:04
  about doing less. It's about doing different work. If we keep
• 5:07
  chasing the perfect pixel for a user who doesn't exist yet,
• 5:10
  we're stuck. We need to use ambiguity as the raw material
• 5:13
  we're working with. So you're saying the skill set shifts from
• 5:16
  precision to... what, exactly. To resilience. To holding the
• 5:19
  structure without snapping it. We need to build interfaces that
• 5:22
  can absorb change without breaking. That's the real
• 5:24
  product. Not the static mockup. The capacity for evolution.
• 5:27
  That's a hard standard to set, but I think it's the right one.
• 5:30
  It is. And until we stop asking for the perfect answer to a
• 5:33
  question that hasn't been asked yet, we'll just keep designing
• 5:36
  for ghosts.
• 5:38
  That's The Feed and The Thread for today. We'll catch you next
• 5:41
  time!