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

Transcript

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

• 0:00
  Companies are merging UX and product roles into single
• 0:02
  builder positions. So the context advantage of human
• 0:05
  design is disappearing? Not if you leverage it, but the title
• 0:08
  just vanished.
• 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:23
  pocket.
• 0:31
  The industry is rushing to merge design and engineering into
• 0:34
  single roles, betting that AI can handle the heavy lifting.
• 0:37
  The risk is that we're trading necessary friction for speed,
• 0:40
  and in doing so, we're losing the ability to ask if a feature
• 0:44
  should exist at all. Jeff Gothelf at his own blog makes
• 0:47
  this case in "How to manage the inevitable mess of running a
• 0:50
  company where everyone is a builder", arguing that the
• 0:53
  "builder" role removes the bureaucratic friction that used
• 0:56
  to act as a quality filter for shipping code. AI tools like
• 0:59
  Claude can generate viable proposals and wireframes
• 1:02
  rapidly, yet they lack the discipline to question whether
• 1:05
  the feature is even needed. That rewrites the assumption that
• 1:08
  speed is always a net positive. Companies keep bolting the same
• 1:11
  generic AI chat panel onto their products, the little "sparkle
• 1:14
  button" that users immediately go hunting for a way to shut
• 1:18
  off. Jon Sabutis at UX Design.cc names the pattern in "Nobody
• 1:21
  asked for the sparkle button": teams forward their model
• 1:24
  vendor's demo instead of designing around a real user
• 1:27
  goal, so every product lands on the same hollow feature.
• 1:30
  Microsoft has already pulled some of these entry points back,
• 1:33
  a quiet admission that the backlash is real. Slava
• 1:36
  Polonski at UX Design.cc offers a counterpoint in "The context
• 1:39
  advantage of human UX", suggesting human advantage lies
• 1:42
  in deep contextual understanding. AI is learning to
• 1:44
  absorb this context, but it still struggles with the
• 1:47
  nuanced, situational insights that define good design. The
• 1:50
  definition of human advantage is fluid, and we must move beyond
• 1:54
  simple interface creation to grasp the room. Other reads
• 1:57
  today from UX Design.cc on setting limits for professional
• 2:00
  users and on storytelling for design and ADHD.
• 2:10
  Today's discussions center on the gap between what
• 2:12
  practitioners can build and what they need to validate, all while
• 2:16
  questioning whether our traditional metrics still hold
• 2:18
  weight in an age of rapid AI adoption. Over on r/hci, a
• 2:21
  master's student launched a free app to help university peers
• 2:25
  share schedules and locations, aiming to fix the fragmentation
• 2:28
  of campus social life. The core tension here is whether a tool
• 2:31
  that removes friction actually helps, or if it just speeds up
• 2:34
  the process of connecting with people you might not want to
• 2:37
  connect with. It's a reminder that solving a logistical
• 2:40
  problem isn't the same as solving a social one. In r/hci,
• 2:43
  a prospective PhD student is asking how to secure a position
• 2:47
  without stellar grades or publications, fearing that the
• 2:49
  influx of AI-focused roles has made the bar impossibly high.
• 2:53
  This question reveals a real anxiety about differentiation.
• 2:56
  If we're trading necessary friction for speed in industry,
• 2:59
  how do we prove depth in academia? The answer likely lies
• 3:02
  in defending your specific decision-making process, not
• 3:05
  just your output. Over on r/UXResearch, a mid-senior
• 3:07
  researcher is struggling to find portfolio examples, noting a
• 3:11
  significant scarcity of resources compared to design
• 3:13
  portfolios. They're asking what actually distinguishes a
• 3:16
  research portfolio from a design one, beyond just text volume.
• 3:20
  This highlights a structural gap in our field. We often judge
• 3:23
  research by its conclusions, but the value is in the method. If
• 3:26
  you can't show the work, you can't prove the insight.
• 3:29
  Finally, in r/UXResearch, a hiring manager is asking what
• 3:32
  their resume tells them that they aren't seeing, specifically
• 3:35
  regarding business value. This is the most critical question of
• 3:38
  the day. If we're rushing to merge roles, the ability to
• 3:41
  articulate impact becomes the only differentiator. Your skills
• 3:45
  are table stakes; your narrative is the asset. We're building
• 3:48
  faster, but we're forgetting to ask if we should be building at
• 3:51
  all.
• 3:59
  The Feed and The Thread is brought to you by Chicago Camps.
• 4:02
  For a weekly and monthly exploration of the patterns and
• 4:04
  signals across UX, you can also check out Patterns and Signals
• 4:07
  at the website patterns and signals dot com. Chicago Camps
• 4:10
  will have more events in 2027. You can submit to be a speaker
• 4:13
  at a future event at Chicago Camps dot org.
• 4:23
  We need to talk about the "sparkle button." It's that
• 4:25
  generic chat panel that shows up in every product, and nobody
• 4:28
  actually asked for it. Jon Sabutis called it out today, and
• 4:31
  it's a perfect example of how we're shipping features based on
• 4:34
  vendor demos rather than user needs. That's the thing that
• 4:36
  really stuck with me. It's not just about a bad UI pattern.
• 4:39
  It's about the fact that we're treating the model as the
• 4:42
  product. We're just bolting a text box onto the interface
• 4:44
  because it's easy, and then we're surprised when users
• 4:47
  ignore it. Exactly. And this connects directly to what Jeff
• 4:50
  Gothelf is arguing about the builder role. When you remove
• 4:52
  the bureaucratic friction, you also remove the quality filter.
• 4:55
  AI tools like Claude can generate a viable proposal in
• 4:58
  seconds, but they don't have the discipline to ask if the feature
• 5:01
  is even necessary. Speed becomes a trap when you skip the "why."
• 5:04
  I see that, but I think we're framing it too negatively. The
• 5:07
  friction was pure slowness. The core problem is that we haven't
• 5:10
  built new skills to replace that old friction. We need to get
• 5:12
  better at the "before" phase. We need to be able to articulate
• 5:15
  the problem so clearly that the solution doesn't need to be a
• 5:18
  generic chat box. I'd push back on that. I don't think it's a
• 5:21
  skill gap. I think it's a structural one. If the incentive
• 5:24
  is to ship fast, and the tool makes shipping fast, the
• 5:26
  "before" phase gets squeezed out. You can't just ask people
• 5:29
  to be more thoughtful when the system rewards them for being
• 5:32
  quick. But that's where the community is already moving.
• 5:34
  Look at the research portfolios on r/UXResearch. People are
• 5:37
  struggling to show their work because the value lies in the
• 5:40
  method and the conclusion. If we start valuing the "how" and the
• 5:43
  "why" as much as the final output, the sparkle button
• 5:45
  disappears. We ship the insight instead of the tool. So the
• 5:48
  shift is about making the thinking visible. If the insight
• 5:51
  is strong enough, it doesn't need a generic interface to hide
• 5:54
  behind. Exactly. The feature should be the answer to a
• 5:56
  specific question, not just a button that exists because the
• 5:59
  model can do it.
• 6:02
  That's The Feed and The Thread for today. We'll catch you next
• 6:04
  time!