Latest / The Feed & The Thread / The Feed & The Thread - November 7, 2026

Transcript

The Feed & The Thread - November 7, 2026 · The Feed & The Thread

• 0:00
  A design team bypassed Figma entirely. They're generating
• 0:03
  code prototypes directly in GitHub branches. So the canvas
• 0:06
  is gone, and the workflow is shifting to live repositories.
• 0:13
  Welcome to The Feed and The Thread, brought to you by
• 0:16
  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:32
  Usability is often treated as a fixed property of a product, yet
• 0:35
  today's coverage suggests it's actually a relative measure of
• 0:38
  human context. Meanwhile, the industry is grappling with the
• 0:42
  economic reality of the AI boom, and the isolating nature of in-
• 0:45
  house design work. These three threads challenge how we define
• 0:49
  success, value, and community in our field. Raluca Budiu at
• 0:52
  Nielsen Norman Group breaks down usability in "Usability 101:
• 0:55
  Introduction to Usability", clarifying that it's a relative
• 0:59
  measure of ease. The article distinguishes usability from
• 1:02
  utility, arguing that a product must be both useful and easy to
• 1:05
  use to have real value. This reframes our evaluation metrics,
• 1:09
  reminding us that a tool's worth depends entirely on the specific
• 1:12
  user, task, and context involved. Oliver Meredith Cox
• 1:15
  at UX Design.cc calls the current AI hype a speculative
• 1:18
  bubble in "After the AI bubble: a manifesto", asserting that
• 1:22
  generative AI hasn't delivered the promised business returns.
• 1:25
  The manifesto argues that we're shifting computers from tools
• 1:28
  for human freedom to instruments for manipulation, drawing
• 1:31
  parallels to the dot-com era. This is a warning that the
• 1:35
  current economic cycle is regressive, and that we risk
• 1:38
  social conflict if we ignore the financial losses hiding behind
• 1:41
  the headlines. Paul Boag at Smashing Magazine addresses the
• 1:44
  isolation of in-house designers in "A New Community For In-House
• 1:48
  UX People", noting that the hardest part of the job is often
• 1:51
  organizational dynamics. Boag highlights a significant gap
• 1:54
  where professionals work in silos without access to outside
• 1:58
  perspectives or shared best practices. This piece offers a
• 2:01
  path forward by creating a dedicated space for these non-
• 2:04
  design challenges, ensuring that in-house teams are no longer
• 2:07
  left to navigate stakeholder conflicts alone. Other articles
• 2:11
  today from UX Planet on UI design trends, CSS-Tricks on the
• 2:14
  redesign preview, and Nielsen Norman Group on agent
• 2:17
  definitions.
• 2:25
  Today's discussions center on how usability shifts with
• 2:28
  context, the changing role of design tools in the AI era, and
• 2:31
  the need for consistent systems in fragmented products. It's a
• 2:34
  day about defining what success actually looks like in practice.
• 2:38
  Over on r/UI_Design, a practitioner is asking how to
• 2:40
  show unsaved changes in a dense settings screen without creating
• 2:44
  visual clutter. They're questioning if the standard
• 2:47
  pattern of a disabled save button is too easy to miss, and
• 2:50
  seeking alternatives to repetitive section-level save
• 2:52
  buttons. The core tension here is between clear user feedback
• 2:56
  and maintaining a clean interface. This matters because
• 2:59
  dense screens are where users feel the most friction, and
• 3:02
  getting the feedback right is crucial for trust. In
• 3:04
  r/ProductDesign, a HubSpot designer shares a workflow where
• 3:08
  their team bypassed Figma entirely, using AI to brainstorm
• 3:11
  and generate code prototypes directly in GitHub branches.
• 3:14
  They argue that AI has replicated the multiplayer
• 3:16
  advantage of design tools, allowing designers to work
• 3:19
  directly in code repositories with live links. This suggests a
• 3:22
  shift where the design tool becomes less central to the
• 3:25
  collaboration process. It's a significant move toward
• 3:28
  integrating design and development, which could change
• 3:31
  how we define our daily workflows. Over on r/UI_Design,
• 3:34
  a UX designer at a mid-sized B2B e-commerce company is seeking
• 3:37
  advice on establishing a UI style from zero, citing
• 3:40
  inconsistent components and cognitive overload as primary
• 3:43
  pain points. They have stakeholder buy-in but feel
• 3:46
  overwhelmed by the scope, asking for a checklist to unify the
• 3:49
  interface. This is a common challenge for teams moving from
• 3:52
  ad-hoc design to a systematic approach. The so-what's clear:
• 3:55
  without a unified style, user experience suffers, and
• 3:58
  developer efficiency drops. In r/UI_Design, a designer proposes
• 4:02
  a new "thumb-first" interaction paradigm for touchscreen
• 4:05
  laptops, replacing traditional pointer-based menus with a
• 4:08
  radial dial that opens from the bottom corner. The mechanic
• 4:11
  involves pressing the corner, sliding toward a wedge to select
• 4:14
  an action, and lifting to confirm. This is an interesting
• 4:17
  exploration of how we can make touch interfaces more intuitive
• 4:20
  on larger screens. It highlights the ongoing search for better
• 4:24
  interaction models that fit the physical context of the device.
• 4:27
  Over on r/UI_Design, a designer shares an observation about
• 4:30
  Shop's use of playful Easter eggs, arguing that these small,
• 4:33
  unexpected moments are crucial for making digital experiences
• 4:37
  memorable. They highlight the shift from purely utilitarian
• 4:40
  interfaces to ones that build trust and affinity through
• 4:43
  delight. This connects to the broader theme of how human
• 4:46
  context and emotion shape our perception of usability. It's a
• 4:49
  reminder that functional design is only part of the equation.
• 4:52
  Today's threads remind us that usability isn't a fixed
• 4:55
  property, but a relative measure shaped by human context,
• 4:58
  economic realities, and the need for community in our isolated
• 5:02
  work.
• 5:09
  The Feed and The Thread is brought to you by Chicago Camps.
• 5:12
  For a weekly and monthly exploration of the patterns and
• 5:15
  signals across UX, you can also check out Patterns and Signals
• 5:18
  at the website patterns and signals dot com. Chicago Camps
• 5:21
  will have more events in 2027. You can submit to be a speaker
• 5:24
  at a future event at Chicago Camps dot org.
• 5:33
  Paul Boag's piece on the isolation of in-house designers
• 5:36
  hit me hard, because it reframes the biggest challenge in our
• 5:39
  field. It's not the pixels, and it's not the code. It's the
• 5:42
  organizational dynamics. He argues that the hardest part of
• 5:44
  the job is navigating stakeholder conflicts in a silo,
• 5:47
  where you don't have access to outside perspectives or shared
• 5:50
  best practices. I've felt that silence for years. We treat
• 5:53
  usability as a fixed property of the product, like it's a feature
• 5:56
  you toggle on. But today's coverage suggests it's actually
• 5:59
  a relative measure of human context. If we're stuck in
• 6:01
  silos, we're measuring usability against the messy reality of how
• 6:04
  people actually work. That's a dangerous gap. And that's where
• 6:07
  the AI angle gets tricky. Oliver Meredith Cox calls the current
• 6:10
  hype a speculative bubble, arguing we're shifting computers
• 6:13
  from tools for human freedom to instruments for manipulation. If
• 6:16
  we're isolating ourselves from peer feedback, we're more likely
• 6:19
  to accept AI outputs that optimize for engagement rather
• 6:22
  than genuine utility. We're trading judgment for speed, and
• 6:24
  we're doing it alone. I push back on the "bubble" framing. I
• 6:27
  see teams like the HubSpot designer in our threads,
• 6:30
  bypassing Figma to generate code prototypes directly in GitHub.
• 6:33
  They're not just chasing hype. They're using AI to replicate
• 6:36
  the multiplayer aspect that in- house teams lose. They're
• 6:38
  building a feedback loop that doesn't rely on a committee.
• 6:41
  That's a smart tactical move, but it's a risk. If the
• 6:44
  "multiplayer" element is just you and an algorithm, you lose
• 6:46
  the social calibration that catches bias. Cox's warning is
• 6:49
  that we're regressing. If we automate the design process
• 6:52
  without automating the ethical review, we're just speeding up
• 6:55
  the production of tools that manipulate rather than empower.
• 6:58
  I don't think we're regressing. I think we're evolving the
• 7:00
  definition of success. The "thumb-first" interaction idea
• 7:03
  in r/UI_Design is a perfect example. It's not about
• 7:05
  replacing the pointer. It's about fitting the interaction to
• 7:08
  the physical context of the device. That's a human-centered
• 7:11
  adjustment. Exactly. The context is the point. Usability
• 7:14
  is a relationship between the tool and the user's environment.
• 7:17
  We must treat it as a dynamic negotiation to solve the
• 7:19
  isolation problem. That removes the need for a committee to tell
• 7:22
  us if a button is in the right place. So the shift is about
• 7:25
  what you're measuring. We must ask "is this usable for this
• 7:28
  person, in this context, right now?" That's the only way to
• 7:31
  break the silo. I agree. The isolation isn't the enemy. The
• 7:34
  lack of context is. Usability is a conversation, not a
• 7:36
  verdict.
• 7:39
  That's The Feed and The Thread for today. We'll catch you next
• 7:41
  time!