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

Transcript

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

• 0:00
  Staff designers are getting paid sixty nine dollars an hour.
• 0:03
  That's actually below entry level in some hubs. And the
• 0:05
  market shift behind that number is reshaping how we value senior
• 0:08
  expertise.
• 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:18
  Friday, September 17 and 18 and tickets are available now! And
• 0:21
  while you're at it, get caught up on UX fundamentals with five
• 0:24
  minute UX at five em UX dot com. The Feed & The Thread is
• 0:27
  available online at feed and thread dot com to submit your
• 0:29
  feeds, or download our app for all the feeds and threads
• 0:32
  delivered right to your pocket.
• 0:41
  The promise of speed is hollow if we can't trust the output.
• 0:44
  We're building systems that move fast, but we're losing the
• 0:47
  thread on accuracy, follow- through, and team health. Russ
• 0:51
  Unger at russunger.com introduces a new verification
• 0:53
  layer in "Executive Orders. In Plain Language.". He argues that
• 0:57
  AI summaries are now table stakes, so the real value lies
• 1:00
  in proving faithfulness to the source. The tool generates a
• 1:03
  receipt for every claim, linking it back to the exact original
• 1:06
  sentence using deterministic string matching. This shifts the
• 1:10
  burden from blind trust to instant verifiability. It forces
• 1:13
  us to ask if we can prove our AI didn't hallucinate, not just if
• 1:16
  it answered quickly. Dan Maccarone at UX Design.cc makes
• 1:19
  a sharp distinction in "The revolution was the easy part".
• 1:23
  He says the loud AI announcements are easy, but the
• 1:25
  slow, unglamorous evolution is where the actual product value
• 1:29
  lives. He compares the current industry hype to a constitution
• 1:32
  patching a flawed declaration, noting that demos aren't shipped
• 1:35
  products. Real progress happens when teams stop celebrating the
• 1:39
  launch and start fixing the edge cases. The revolution was the
• 1:42
  easy part, and the hard work is just beginning. Scott Berkun at
• 1:46
  On Scott Berkun offers a playbook for interpersonal
• 1:48
  friction in "How to fix your team". He advises leaders to act
• 1:52
  as investigators rather than judges, diagnosing root causes
• 1:55
  like lack of trust instead of treating surface symptoms. A
• 1:58
  critical step is accepting that your own habits might be the
• 2:01
  source of the team's friction. You must identify allies for
• 2:05
  change while respectfully engaging those who resist.
• 2:07
  Fixing a team starts with looking in the mirror before
• 2:10
  pointing a finger. Other articles today from Dan Saffer
• 2:13
  on favorite books, UX Planet on AI replacing designers, and
• 2:17
  Jeffrey Zeldman on web accessibility memory.
• 2:26
  Designers are trading speed for stability today. The tension
• 2:30
  isn't about moving fast anymore. It's about trusting what ships.
• 2:33
  Over on r/uxwriting, writers are asking what actually eats their
• 2:37
  time. The answer isn't writing. It's chasing context from
• 2:41
  product managers. It's syncing copy docs with Figma files. It's
• 2:44
  explaining terminology to stakeholders who don't read the
• 2:48
  docs. This reveals a broken handoff. We build fast systems
• 2:51
  that ignore human friction. If the output isn't trusted, the
• 2:55
  speed is hollow. In r/UXDesign, a staff-level offer for sixty-
• 2:58
  nine dollars an hour sparked alarm. It's a contract role with
• 3:02
  no benefits. It feels like a race to the bottom. Senior
• 3:05
  talent is being priced like junior labor. This erodes team
• 3:08
  health. When you devalue experience, you lose the people
• 3:12
  who ensure quality. Speed without respect for craft is
• 3:15
  just burnout in disguise. Also in r/uxwriting, the disconnect
• 3:18
  between Figma and live products is causing chaos. Designers see
• 3:22
  one thing. Users see another. Localization teams are left
• 3:26
  guessing. There's no single source of truth. This lack of
• 3:29
  follow-through breaks trust. If the interface doesn't match the
• 3:33
  design, users doubt the product. Accuracy matters more than
• 3:36
  velocity here. Over on r/UXDesign, new designers are
• 3:39
  asking if the career is still worth it. They worry about AI
• 3:43
  and saturation. The anxiety is real. But the question shifts
• 3:46
  from replacement to adaptation. AI is a tool, not a replacement
• 3:50
  for judgment. Learning resources matter less than learning how to
• 3:54
  think. The field needs critical thinkers, not just pixel
• 3:57
  pushers. Still in r/UXDesign, someone argues AI anxiety comes
• 4:01
  from loving craft too much. They say users care about efficiency,
• 4:04
  not delight. This is a false dichotomy. Good design is both
• 4:08
  efficient and trustworthy. Ignoring craft risks building
• 4:11
  systems that work but feel wrong. We need balance, not
• 4:14
  abandonment. We're building faster systems, but we're losing
• 4:18
  the thread on trust.
• 4:26
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:29
  & Friday, September 17 & 18. It's an online event, so you can
• 4:32
  join from anywhere in the world! Tickets are free, thanks to the
• 4:36
  generosity of the community! If it's within your budget, you can
• 4:39
  purchase a general admission ticket for only twenty six
• 4:42
  dollars - with limited early bird tickets at only fifteen
• 4:45
  dollars. Get tickets now at Chicago Camps dot org.
• 4:55
  Dan Maccarone calls the revolution the easy part. He
• 4:57
  argues that demos aren't shipped products. The real value lives
• 5:01
  in fixing edge cases. That connects directly to Russ
• 5:03
  Unger's point about receipts. We need deterministic proof, not
• 5:06
  just speed. Exactly. The speed is hollow without trust. Writers
• 5:10
  on r/uxwriting are drowning in context chasing. They aren't
• 5:13
  writing copy. They're proving their work to stakeholders who
• 5:16
  don't read the docs. If the output isn't trusted, the
• 5:19
  handoff breaks. So the friction isn't technical. It's
• 5:21
  structural. We built systems that move fast but ignore human
• 5:24
  verification. Unger's string matching shifts the burden from
• 5:28
  blind trust to instant verifiability. But does that
• 5:30
  solve the team health issue? It solves the ambiguity. When you
• 5:33
  can prove the AI didn't hallucinate, you stop defending
• 5:36
  your craft. You start validating the result. The anxiety comes
• 5:39
  from loving craft too much while ignoring efficiency. Good design
• 5:43
  must be both. I see it as a standardization problem. We need
• 5:46
  to treat verification as a deliverable, not an
• 5:48
  afterthought. If we don't, we lose the thread on accuracy. The
• 5:51
  hard work is just beginning because we haven't defined what
• 5:54
  faithful output looks like at scale. But defining it isn't
• 5:58
  enough. We have to value the judgment call. Knowing which
• 6:00
  proof to trust is the new senior skill. It's not about doing the
• 6:04
  work faster. It's about deciding what work actually matters. So
• 6:07
  the metric shifts from velocity to verifiability. We stop
• 6:10
  measuring how fast we ship. We start measuring how easily we
• 6:13
  can prove we shipped the right thing. Right. Trust is no
• 6:16
  longer a feeling. It's a feature.
• 6:20
  That's The Feed and The Thread for today. We'll catch you next
• 6:22
  time!