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

Transcript

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

• 0:00
  AI prototyping is creating digital Winchester Mystery
• 0:02
  Houses. So we're just stacking features without a map? Exactly,
• 0:06
  and the code is becoming a maze no one can untangle.
• 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:24
  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:32
  delivered right to your pocket.
• 0:41
  AI has made it cheaper than ever to build features, but that
• 0:44
  speed is now the biggest threat to product coherence. We're
• 0:47
  seeing a trade-off between velocity and structure that
• 0:50
  every design team needs to manage. Patrick Neeman at UX
• 0:53
  Design.cc makes the case in "Don’t let AI build a Winchester
• 0:56
  Mystery House" that we're building software like the
• 0:58
  Winchester Mystery House, where features accumulate without a
• 1:02
  master plan. The problem is that AI removes the friction that
• 1:05
  used to force teams to define a coherent structure first. Now,
• 1:08
  each feature operates in isolation with its own
• 1:11
  vocabulary, creating an unusable experience. Neeman argues for a
• 1:14
  retrofit approach to restore order. Lucas Plabst and
• 1:17
  colleagues at MeasuringU challenge the assumption that AI
• 1:20
  moderators are equivalent to humans in "Do Participants Say
• 1:23
  Less to AI Than to Human Moderators?". They note that
• 1:25
  most existing studies compare AI to surveys or static questions,
• 1:29
  rather than testing it in complex, rapport-heavy
• 1:31
  interviews. Their controlled experiment tests whether
• 1:34
  participants actually speak less to AI than to human moderators.
• 1:37
  This matters because if users withhold information, the data
• 1:41
  you collect is fundamentally flawed. Phil Morton writes in
• 1:44
  "Building your first side project with AI, a step-by-step
• 1:47
  guide" at his blog about building your first side project
• 1:50
  with AI, a step-by-step guide for non-technical UX
• 1:52
  professionals. He argues that side projects are the fastest
• 1:55
  way to upskill in the AI era, and you don't need to become a
• 1:58
  traditional software engineer. The guide walks through building
• 2:02
  a dashboard that visualizes UK electricity grid fuel sources
• 2:05
  using a public API. This is a practical path for designers who
• 2:08
  want to ship functional products without learning every line of
• 2:11
  code. Other reads available from UX Planet on design tools,
• 2:15
  Rosenfeld Media on conference tickets, and UX Design.cc on the
• 2:18
  future of deliverables.
• 2:26
  Practitioners are asking who decides when a design is
• 2:29
  actually finished, and the answers are revealing a fracture
• 2:32
  in how we build. Over on r/UXResearch, a senior
• 2:34
  researcher is wrestling with how to present their hybrid skillset
• 2:38
  to big tech recruiters, specifically wondering if they
• 2:41
  should highlight basic methodologies or focus on
• 2:43
  strategic impact. The tension here's real, because experience
• 2:46
  inflation is making it hard to distinguish genuine depth from a
• 2:49
  checklist of buzzwords. My take is that strategic impact only
• 2:52
  matters if you can prove the behavioral science behind it,
• 2:55
  and that's the story you need to tell. In r/UXResearch, a novice
• 2:59
  is asking if generating survey responses with AI is an
• 3:02
  acceptable workaround for failing to recruit enough senior
• 3:05
  citizens. This creates a dangerous shortcut, because if
• 3:07
  you synthesize the data, you're not testing a product, you're
• 3:10
  testing your own assumptions. The field needs to reject this,
• 3:14
  because validity is the only currency that matters when
• 3:16
  you're making decisions for real people. Over on
• 3:19
  r/DesignSystems, someone is looking for a wireframing tool
• 3:22
  that supports messy, early-stage exploration, because high-
• 3:25
  fidelity tools like Figma create an illusion of finality. This is
• 3:28
  a structural problem, because when the canvas looks polished,
• 3:31
  stakeholders treat exploratory sketches as locked decisions.
• 3:34
  The so-what's that we need to deliberately choose lower-
• 3:37
  fidelity tools to keep the conversation open and prevent
• 3:40
  the premature closure of design thinking. In r/ProductDesign, a
• 3:43
  user shared a link to a store selling mass-market goods with a
• 3:47
  luxury brand pattern copy, prompting questions about the
• 3:50
  ethics of imitation. This isn't just about legality, it's about
• 3:53
  design integrity, because when we copy established motifs
• 3:56
  without attribution or innovation, we dilute the value
• 3:58
  of the craft. It's a reminder that originality is a form of
• 4:01
  respect for the user and the designer alike. Over on
• 4:04
  r/DesignSystems, a practitioner is asking what the source of
• 4:07
  truth looks like in twenty twenty-six, noting a shift away
• 4:10
  from third-party bridges toward native variables. This signals a
• 4:14
  maturation in the industry, because we're finally moving
• 4:16
  from patchwork solutions to integrated systems. The takeaway
• 4:19
  is that the tools are catching up to our need for coherence,
• 4:23
  and that's a good thing. The common thread today is that
• 4:25
  speed is tempting, but structure is what makes the work stick.
• 4:36
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:39
  & Friday, September 17 & 18. It's an online event, so you can
• 4:42
  join from anywhere in the world! Tickets are free, thanks to the
• 4:45
  generosity of the community! If it's within your budget, you can
• 4:48
  purchase a general admission ticket for only twenty six
• 4:51
  dollars - with limited early bird tickets at only fifteen
• 4:53
  dollars. Get tickets now at Chicago Camps dot org.
• 5:03
  Neeman's "Winchester Mystery House" metaphor is hitting
• 5:06
  differently today because the structural decay isn't
• 5:08
  hypothetical anymore. AI removed the friction that used to force
• 5:11
  teams to define a coherent system before adding features,
• 5:14
  and now we're seeing isolated components with mismatched
• 5:17
  vocabularies that don't connect. I've seen this in the community
• 5:20
  threads too. People are using high-fidelity tools for early
• 5:22
  exploration because it's faster, and that speed creates an
• 5:25
  illusion of finality. When the canvas looks polished,
• 5:28
  stakeholders treat exploratory sketches as locked decisions, so
• 5:31
  the conversation about structure dies before it starts. That's
• 5:34
  the systemic risk. If we accept that speed replaces structural
• 5:37
  integrity, we're not building products, we're just
• 5:39
  accumulating digital junk. The retrofit approach Neeman
• 5:42
  suggests is necessary, but it's expensive to tear down bad
• 5:44
  foundations after you've already built them. I'd push back on
• 5:47
  the idea that retrofitting is the only path. The real issue is
• 5:50
  that we're valuing output over alignment. We need to
• 5:53
  deliberately choose lower- fidelity tools to keep the
• 5:55
  conversation open, not because we can't build fast, but because
• 5:58
  we need to preserve the space for disagreement and iteration.
• 6:01
  So you're saying the problem isn't the lack of structure, but
• 6:04
  the premature closure of design thinking? Exactly. Structure
• 6:07
  isn't a deliverable, it's a habit. And right now, the habit
• 6:09
  is skipping the habit because the tools make it feel
• 6:12
  unnecessary. The gap between what we can build and what we
• 6:15
  should build is widening, and that gap is where the real work
• 6:18
  lives. It's about knowing when to stop building and start
• 6:20
  connecting.
• 6:23
  That's The Feed and The Thread for today. We'll catch you next
• 6:26
  time!