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

Transcript

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

• 0:00
  Your job title doesn't protect you from AI. Wait, so seniority
• 0:03
  is irrelevant? It's the specific task structure that matters, not
• 0:07
  your role.
• 0:12
  Welcome to The Feed and The Thread, brought to you by
• 0:14
  Chicago Camps. The Feed & The Thread is available online at
• 0:17
  feed and thread dot com to submit your feeds, or download
• 0:20
  our app for all the feeds and threads delivered right to your
• 0:22
  pocket.
• 0:30
  The tools we rely on are quietly changing shape. Some split into
• 0:33
  two, some shrink to fit a pocket, and others stop caring
• 0:37
  what we call ourselves. The question isn't whether the
• 0:39
  technology works. It's whether our mental models still match
• 0:43
  the reality of the work. Onboarding a contractor is no
• 0:46
  longer just about paperwork. It's a question of whether the
• 0:49
  platform sees you as a global citizen or a data entry task.
• 0:52
  That's the core tension in "Deel vs. Rippling for Contractor
• 0:55
  Management: Which Platform Gets the User Experience Right?", a
• 0:59
  comparative analysis by the UX Planet team. Deel prioritizes
• 1:02
  compliance and localized contracts from the start.
• 1:05
  Rippling treats it as an integration of administrative
• 1:08
  and IT steps. The takeaway is that neither approach is
• 1:11
  neutral. Your workflow will bend to whichever logic the platform
• 1:14
  chooses first. A second screen doesn't just add space. It
• 1:17
  changes the ergonomics of how we think. Oliver Reichenstein at iA
• 1:21
  Inc. describes their approach in "It Takes Two to Duo", treating
• 1:24
  the inner display as a compact, distraction-free workspace. They
• 1:28
  move toolbars to the side in landscape mode to keep thumbs
• 1:31
  within reach. It's a small shift, but it turns a dual-
• 1:34
  screen phone into a viable professional tool for writing
• 1:37
  and presenting. Your job title is a label that doesn't reflect
• 1:40
  the actual tasks you do. Patrick Neeman argues this in "AI
• 1:44
  doesn’t care about your job title" at UX Design.cc, citing
• 1:47
  research from OpenAI and the University of Pennsylvania. The
• 1:50
  risk depends on how easily a task can be specified and
• 1:53
  verified. Like ATMs, automation changes the composition of the
• 1:56
  job rather than eliminating it. The work evolves, but the title
• 2:00
  stays the same. Other reads available today from Figma on
• 2:03
  code layers, Nielsen Norman Group on practitioner sentiment
• 2:06
  toward AI, and MeasuringU on 2026 salary benchmarks.
• 2:16
  Today, the core tension isn't about which tools we use, but
• 2:19
  whether our mental models still match the reality of the work.
• 2:22
  We're seeing a shift where roles are either splitting into two,
• 2:26
  shrinking to fit a pocket, or stopping caring what we call
• 2:29
  ourselves. Over on r/UXResearch, a psychologist in
• 2:31
  Argentina is asking if it's viable to transition into UX
• 2:34
  Research. They want to know about market conditions,
• 2:37
  starting points, and salary expectations. It's a common
• 2:40
  desire for adjacent fields to leverage a background in human
• 2:43
  behavior for tech roles. The question itself reveals a gap in
• 2:46
  how we define entry points. If a trained psychologist can't find
• 2:49
  a clear path, our onboarding models are broken. In
• 2:52
  r/UXDesign, a Creative Technology student is
• 2:54
  considering switching majors to Interaction Design. They cite
• 2:58
  ADHD and a lack of stimulation in engineering-heavy subjects,
• 3:01
  highlighting a strong aptitude for communication design.
• 3:04
  They're worried about the industry's current state,
• 3:06
  though. This isn't just about career advice. It's about
• 3:09
  whether our educational paths are forcing a one-size-fits-all
• 3:12
  structure on brains that need different types of stimulation.
• 3:15
  Also in r/UXResearch, a professional is weighing a
• 3:18
  senior generalist role in the UAE against their current
• 3:21
  specialist-focused market. The job involves end-to-end
• 3:24
  responsibilities, from research to dev handoff, with a salary of
• 3:27
  four to four point five thousand dollars. They're questioning if
• 3:30
  the move is worth it given the in-office requirement and
• 3:33
  cultural adjustment. The shift from specialist to generalist is
• 3:36
  a concrete example of the tools we rely on changing shape. Over
• 3:40
  on r/UXDesign, a product designer was cut from a paid
• 3:43
  trial after just the first day. The design team gave positive
• 3:46
  feedback, but the founder expected near-final, polished
• 3:49
  work immediately. The designer followed a standard iterative
• 3:52
  process of research and concepting. This mismatch in
• 3:54
  expectations is a direct conflict with how we actually do
• 3:57
  the work. It's not about whether the technology works. It's about
• 4:01
  whether our mental models still match the reality of the work.
• 4:04
  The pattern is clear. We're not just adapting to new tools.
• 4:07
  We're redefining what the work is, who does it, and how we
• 4:10
  expect it to be delivered.
• 4:19
  The Feed and The Thread is brought to you by Chicago Camps.
• 4:22
  For a weekly and monthly exploration of the patterns and
• 4:24
  signals across UX, you can also check out Patterns and Signals
• 4:28
  at the website patterns and signals dot com. Chicago Camps
• 4:31
  will have more events in 2027. You can submit to be a speaker
• 4:34
  at a future event at Chicago Camps dot org.
• 4:43
  I keep coming back to the Deel versus Rippling comparison,
• 4:46
  specifically the point about workflow logic. The article
• 4:49
  argues that neither platform is neutral. Your process bends to
• 4:52
  whichever logic the system adopts first. It's not just a
• 4:55
  preference. It's a structural choice that dictates how your
• 4:58
  team operates. That's a heavy claim to put on a software
• 5:01
  toggle. We're treating compliance and integration as
• 5:03
  opposing philosophies, but they're both just administrative
• 5:06
  friction. We let the tool define the human relationship. We're
• 5:09
  outsourcing our judgment to a database schema. But look at
• 5:12
  the underlying data. Deel prioritizes localized contracts
• 5:15
  from the start. That's a specific, verifiable action.
• 5:18
  Rippling treats it as an IT step. That's an integration
• 5:20
  task. The difference is measurable. It's the distinction
• 5:23
  between a legal document and a data entry field. One has
• 5:26
  weight. The other is just a record. I hear you on the
• 5:29
  measurability. But a record is often more honest than a
• 5:31
  document that's been stripped of context. If we're just entering
• 5:34
  data, we lose the nuance of the person on the other side. We're
• 5:38
  reducing a global citizen to a row in a table. That's a failure
• 5:41
  of imagination. Is it though? Or is it clarity? If the system
• 5:44
  forces you to define the role precisely, you eliminate the
• 5:47
  ambiguity that causes so much friction. You're not reducing
• 5:50
  the person. You're defining the interface between the person and
• 5:53
  the organization. That's a feature. I'm not sure I buy
• 5:55
  that. Defining the interface is easy. Designing the relationship
• 5:59
  is hard. We're so focused on the task specification that we
• 6:02
  forget the human element. The risk is that the job becomes a
• 6:05
  series of inputs and outputs. We lose the ability to adapt.
• 6:08
  Adaptation requires structure. Without a clear specification,
• 6:11
  you can't verify the outcome. You're flying blind. The system
• 6:14
  isn't removing the human. It's creating a container for the
• 6:17
  human to operate within. That's a foundation. I'll grant you
• 6:20
  the foundation. But a foundation isn't a home. It's just the
• 6:23
  ground. We need to build something livable on top of it.
• 6:25
  We need to design for the person and the process. So the
• 6:28
  question is about the standard. We need to define what a good
• 6:31
  onboarding experience looks like before we let the software
• 6:34
  define it for us. And that standard has to include the
• 6:37
  human. Not just the data. Not just the contract. The person.
• 6:40
  That's the line we have to hold.
• 6:43
  That's The Feed and The Thread for today. We'll catch you next
• 6:46
  time!