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

Transcript

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

• 0:00
  The median user experience salary is now one hundred forty-
• 0:02
  two thousand dollars. That's a serious jump for a role that's
• 0:05
  still often misunderstood. But the real shock is how much that
• 0:08
  number shifts if you change your location.
• 0:14
  Welcome to The Feed and The Thread, brought to you by
• 0:16
  Chicago Camps. The Feed & The Thread is available online at
• 0:19
  feed and thread dot com to submit your feeds, or download
• 0:22
  our app for all the feeds and threads delivered right to your
• 0:24
  pocket.
• 0:32
  Your compensation looks good on paper, but your buying power is
• 0:36
  quietly shrinking. Meanwhile, the tools we use to build and
• 0:39
  test interfaces are shifting underneath us. A raise doesn't
• 0:42
  buy the life it used to this year. Jeff Sauro, Jim Lewis, and
• 0:46
  Will Schiavone at MeasuringU lay it out in "User Experience
• 0:49
  Salaries & Calculator (2026)": the median U.S. salary hit one
• 0:53
  hundred forty-two thousand dollars, yet inflation ate two
• 0:56
  percent of that value between twenty-two and twenty-four.
• 0:59
  Location explains half of the pay gap, with Northern
• 1:02
  California leading at one hundred ninety-eight thousand.
• 1:05
  Your job title matters less than your zip code. We've been
• 1:08
  building design systems backwards for years. Sepeda
• 1:11
  Rafael argues in "Entering Atomic Design from the screen"
• 1:15
  that we should start with the user's screen actions, not the
• 1:18
  smallest atom. A sort button affects the entire dataset.
• 1:21
  Proximity-based inventories miss these structural connections.
• 1:25
  Define the scope of the interaction first, then the
• 1:28
  components. Accessibility compliance just got stricter by
• 1:31
  default. Wilco Fiers at Deque announces in "Find Label in Name
• 1:34
  issues in every scan with Axe- core 4.14.0" that Axe-core now
• 1:38
  enforces the Label in Name rule. Most voice control software
• 1:41
  responds to the accessible name. Apple's ecosystem still requires
• 1:45
  an exact match, creating a significant gap for developers.
• 1:48
  If your labels don't match your names, your users can't control
• 1:52
  your interface. Other reads available today from UX Planet
• 1:55
  on testing AI code skills and UX Design.cc on post-war French
• 1:59
  design history.
• 2:07
  Today's conversations circle the shifting landscape of our
• 2:10
  professional leverage, even as the tools we rely on to build
• 2:13
  and test interfaces keep shifting underneath us. Over on
• 2:16
  r/hci, a researcher is surveying programmers to map out what they
• 2:19
  actually enjoy about their work, specifically looking at how AI
• 2:22
  tools are altering those feelings of satisfaction. The
• 2:25
  core question is whether deep focus and debugging still bring
• 2:28
  the same reward, or if automation has flattened that
• 2:31
  curve. This matters because if the intrinsic joy of the craft
• 2:34
  is eroding, we need to understand if that's a temporary
• 2:37
  adjustment or a permanent shift in how we value our own
• 2:39
  expertise. In r/uxwriting, someone is sharing the anxiety
• 2:42
  of a performance review, noting that their strategic output has
• 2:46
  declined after covering a vacant role for eighteen months. They
• 2:49
  describe a spiral of self-doubt, feeling that their work lacks
• 2:52
  the depth and leadership their manager expects. This is a real
• 2:55
  tension, where the pressure to cover multiple bases often comes
• 2:58
  at the cost of the strategic thinking that's supposed to
• 3:01
  define seniority. It highlights how easily we can lose our
• 3:04
  footing when we're stretched too thin, and how hard it is to
• 3:07
  reclaim that authority when you're already behind. Over on
• 3:10
  r/DesignSystems, a developer is introducing an open-source
• 3:13
  alternative to Figma and Paper, aiming to create a unified place
• 3:16
  for storing design systems and developing product pages. The
• 3:19
  post is framed as a tentative offer, acknowledging uncertainty
• 3:23
  about whether the community actually needs another tool in
• 3:26
  this crowded space. The question here's simple: do we want a new
• 3:29
  option, or are we tired of the churn? This is less about the
• 3:32
  tool itself and more about our collective appetite for adopting
• 3:35
  new infrastructure, and whether we're ready to invest in another
• 3:38
  platform that promises to simplify our workflows. In
• 3:41
  r/ProductDesign, a designer is sharing a case study where
• 3:44
  forty-one prototypes were created before finding the right
• 3:47
  interaction model for a physical desk toy. The pivotal moment
• 3:50
  came from a single piece of feedback, where a non-expert
• 3:53
  user preferred a free-spinning mechanism over a complex spring
• 3:56
  detent system. This is a clear reminder that over-engineering
• 3:59
  can be a trap, and that the simplest solution is often the
• 4:02
  one that feels most natural. It's a good check on our
• 4:05
  tendency to add complexity when a straightforward approach would
• 4:08
  have worked just fine. Over on r/ProductDesign, a junior
• 4:11
  designer is asking for guidance on how to present proprietary
• 4:14
  work in their portfolio without violating NDAs or exposing
• 4:17
  sensitive branding. They're unsure whether to recreate
• 4:20
  designs with a different system, simplify flows, or use low-
• 4:23
  fidelity mockups, seeking a rule of thumb for what's acceptable.
• 4:26
  This is a common dilemma, where the desire to show our best work
• 4:29
  clashes with the legal and ethical constraints of our
• 4:32
  current roles. It's a question about balance, about how to
• 4:35
  demonstrate our capabilities without compromising the trust
• 4:38
  our employers place in us. The common thread here is a sense of
• 4:41
  adjustment, where we're trying to find our footing in a
• 4:44
  landscape that feels less stable than it did last year.
• 4:54
  The Feed and The Thread is brought to you by Chicago Camps.
• 4:57
  For a weekly and monthly exploration of the patterns and
• 5:00
  signals across UX, you can also check out Patterns and Signals
• 5:03
  at the website patterns and signals dot com. Chicago Camps
• 5:06
  will have more events in 2027. You can submit to be a speaker
• 5:09
  at a future event at Chicago Camps dot org.
• 5:18
  The label-in-name rule in Axe- core four point fourteen zero is
• 5:21
  the quietest change with the loudest consequence we've seen
• 5:24
  all year. It's not just a new warning. It's a hard stop that
• 5:26
  forces every component to declare exactly what it does,
• 5:29
  because the screen reader or voice control software can't
• 5:32
  guess anymore. I've been watching that play out in the
• 5:34
  community threads, and it's hitting a specific nerve. We
• 5:37
  have a junior designer on ProductDesign asking how to show
• 5:39
  their work without breaking an NDA, and the tension is real.
• 5:42
  They want to prove they can build systems, but they're
• 5:45
  terrified of exposing the proprietary logic. It's a
• 5:47
  perfect microcosm of the bigger issue. We're hiding the very
• 5:50
  structure that makes our work valuable. Exactly. And that's
• 5:52
  where the salary data from MeasuringU starts to look less
• 5:55
  like a pay scale and more like a map of what's hidden. The median
• 5:58
  is one hundred and forty-two thousand, sure. But the gap
• 6:01
  between that and the top earners reflects who gets to see the
• 6:03
  whole architecture. If you're stuck in the weeds of
• 6:06
  compliance, or if you're hiding your best work because of legal
• 6:09
  fears, you're trading leverage for safety. I'd push back on
• 6:11
  that framing slightly. It's not just about hiding work. It's
• 6:14
  that we're still taught to design components in isolation,
• 6:17
  like little atoms, and then we're shocked when the system
• 6:19
  breaks. Sepeda Rafael's point about starting from the screen
• 6:22
  actions is key. A sort button is a decision about data integrity.
• 6:25
  If you don't understand that structural connection, you can't
• 6:28
  explain your value in a performance review, and you
• 6:30
  definitely can't defend it in a portfolio. So the skill is
• 6:33
  articulating why that button matters to the entire user
• 6:36
  journey. That's the difference between a task and a strategy.
• 6:38
  And that's where the buying power comes from, even if the
• 6:41
  inflation numbers are eating into the raw dollars. Right.
• 6:44
  The market is going to value the people who can connect the dots
• 6:47
  between a technical constraint, like a label rule, and a
• 6:49
  business outcome, like user retention. That's the narrative
• 6:52
  you need to build. Accessibility is the foundation
• 6:54
  of our design language, not a checkbox at the end of the
• 6:57
  pipeline. That's how you prove you're building complete
• 6:59
  systems.
• 7:02
  That's The Feed and The Thread for today. We'll catch you next
• 7:05
  time!