Latest / The Feed & The Thread / The Feed & The Thread - July 18, 2026

Transcript

The Feed & The Thread - July 18, 2026 · The Feed & The Thread

• 0:00
  Dropdown lists are actually hiding your options from users.
• 0:03
  That sounds counterintuitive, doesn't it. They create friction
• 0:06
  by forcing clicks, so we're breaking down when to ditch
• 0:09
  them.
• 0:13
  Welcome to The Feed and The Thread, brought to you by
• 0:16
  Chicago Camps. Leadership By Design is on Thursday and
• 0:19
  Friday, September 17 and 18 and tickets are available now! And
• 0:22
  while you're at it, get caught up on UX fundamentals with five
• 0:25
  minute UX at five em UX dot com. The Feed & The Thread is
• 0:28
  available online at feed and thread dot com to submit your
• 0:31
  feeds, or download our app for all the feeds and threads
• 0:33
  delivered right to your pocket.
• 0:42
  We keep asking our tools to do the heavy lifting, but the real
• 0:46
  work happens in the agreements between those tools. Huei-Hsin
• 0:49
  Wang at Nielsen Norman Group challenges us in "Does Your Form
• 0:52
  Really Need a Dropdown List?". She argues that dropdown lists
• 0:56
  hide options behind a click, which slows down decision-making
• 0:59
  and increases cognitive load. This convenience for designers
• 1:02
  comes at a significant cost to user experience. We should only
• 1:06
  use dropdowns in narrow, specific scenarios where the
• 1:08
  friction is justified. Christine Vallaure addresses
• 1:11
  design system drift in "Design system contracts: the component
• 1:15
  lives in neither Figma nor code". She proposes a contract
• 1:18
  approach where a neutral JSON file serves as the single source
• 1:21
  of truth. Both Figma components and code are automatically
• 1:24
  generated from this contract, ensuring they stay synchronized
• 1:27
  without manual intervention. This removes the maintenance
• 1:31
  errors that come from picking one tool as the authority. Nick
• 1:34
  Babich highlights a major update to Google Stitch in "Google
• 1:37
  Stitch Just Got a Major Update". The tool now leverages AI to
• 1:40
  craft interfaces, moving beyond traditional manual design
• 1:44
  processes. This reinforces the trend of AI acting as a co-pilot
• 1:47
  in the design workflow. It allows designers to generate
• 1:50
  high-fidelity UI components more efficiently, shifting the focus
• 1:53
  from creation to curation. Other reads available from
• 1:56
  Codrops on interactive narrative engineering, Nielsen Norman
• 2:00
  Group on human-led research, and UX Design.cc on design
• 2:03
  metaphors.
• 2:10
  Designers are looking past the interface to see where the real
• 2:14
  work actually lives. Over on r/UserExperienceDesign, a poster
• 2:17
  asked if feedback boards overwhelm users. It's a valid
• 2:20
  worry. We collect data to reduce uncertainty, but the method can
• 2:24
  create it. The board becomes a wall of noise rather than a
• 2:27
  clear signal. The hard work is in the agreement between what we
• 2:30
  ask for and what users can give without burning out. Another
• 2:34
  designer in r/UI_Design shared the struggle of building a
• 2:37
  browser board game where the interface is the game board.
• 2:40
  They faced five specific hurdles, from color flow to
• 2:43
  rendering bridges. This is where the theme lands. The tools
• 2:46
  rendered the graphics, but the heavy lifting was negotiating
• 2:49
  the rules of space and perception. The UI had to agree
• 2:52
  with the logic, or the game broke. In r/UI_Design, there's
• 2:55
  concern that AI tools are bringing back scrolljacking.
• 2:58
  It's a pattern that overrides native scrolling for visual
• 3:02
  flair. We see the trend on Dribbble, but the cost falls on
• 3:05
  accessibility. The tension here's between aesthetic
• 3:08
  ambition and functional respect. When we ask tools to create
• 3:11
  spectacle, we often lose the agreement with the user's need
• 3:14
  for control. Finally, in r/UserExperienceDesign, someone
• 3:17
  questioned if AI makes design easier or just moves the hard
• 3:20
  part. The consensus is shifting. AI handles the wireframes, but
• 3:24
  it struggles with empathy. The difficulty hasn't disappeared.
• 3:27
  It's migrated to the space between the generated output and
• 3:31
  the human context. That's where the design happens now. We're
• 3:34
  not just using tools anymore. We're negotiating the terms of
• 3:37
  their use.
• 3:45
  Chicago Camps is hosting Leadership By Design on Thursday
• 3:48
  & Friday, September 17 & 18. It's an online event, so you can
• 3:51
  join from anywhere in the world! Tickets are free, thanks to the
• 3:54
  generosity of the community! If it's within your budget, you can
• 3:57
  purchase a general admission ticket for only twenty six
• 4:00
  dollars - with limited early bird tickets at only fifteen
• 4:03
  dollars. Get tickets now at Chicago Camps dot org.
• 4:12
  The JSON contract idea from Christine Vallaure changes the
• 4:15
  game because it stops us from treating Figma or code as the
• 4:18
  source of truth. It treats the logic itself as the authority.
• 4:21
  That's the structural fix, but the r/UserExperienceDesign
• 4:24
  thread points out the human cost. We're automating the sync,
• 4:27
  but are we automating the empathy? The difficulty hasn't
• 4:30
  vanished. It just moved to the gap between the generated output
• 4:33
  and the user's actual context. So the tool handles the heavy
• 4:36
  lifting of consistency, which frees up the designer to focus
• 4:39
  on that context. But only if the organization trusts the
• 4:42
  contract. If they don't, we're just building a faster way to be
• 4:45
  wrong together. Exactly. The risk isn't the tool. It's the
• 4:48
  assumption that a neutral file removes the need for judgment.
• 4:51
  We're not just using tools anymore. We're negotiating the
• 4:54
  terms of their use. The contract is the floor, not the ceiling.
• 4:57
  And that negotiation is where the real work lives. It's no
• 5:00
  longer about drawing the box. It's about defining what the box
• 5:04
  is allowed to contain. Right. The skill shifts from creation
• 5:07
  to curation. And that requires a new kind of rigor. We used to
• 5:10
  measure success by how fast we could produce assets. Now we
• 5:13
  have to measure it by how well we can define constraints. And
• 5:16
  until we do, the contract is just a really expensive to-do
• 5:19
  list.
• 5:21
  That's The Feed and The Thread for today. We'll catch you next
• 5:24
  time!