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

Transcript

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

• 0:00
  Ninety-five percent of AI pilots deliver zero measurable impact.
• 0:03
  That's a staggering failure rate. The problem isn't the
• 0:06
  technology, it's the human systems we built around it.
• 0:13
  Welcome to The Feed and The Thread, brought to you by
• 0:15
  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:26
  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 AI in UX research is speed, but the reality is
• 0:44
  often a shift in where the bottleneck lives. We're trading
• 0:47
  technical execution for human ambiguity, and the data suggests
• 0:50
  we haven't actually saved as much time as we thought. Lucas
• 0:53
  Plabst, Jeff Sauro, and Jim Lewis at MeasuringU review the
• 0:56
  literature on "Effectiveness of AI Moderators: A Literature
• 1:00
  Review" to test if AI can truly replace human moderators. The
• 1:03
  findings are mixed, showing that participants often speak less to
• 1:06
  AI and provide shallower insights than they do to humans.
• 1:09
  AI might handle straightforward questions, but it misses the
• 1:12
  nuanced elaboration that comes from human connection. That
• 1:15
  rewrites the assumption that automation equals better data
• 1:19
  quality. Patrick Neeman at UX Design.cc makes the case in
• 1:22
  "Most AI problems are really human problems" that most AI
• 1:25
  failures are organizational, not technical. He points out that
• 1:28
  ninety-five percent of generative AI pilots deliver no
• 1:31
  measurable impact because we start with technology instead of
• 1:34
  user needs. This creates a Jevons Paradox where faster code
• 1:37
  generation just shifts the bottleneck to decision-making
• 1:40
  and shared understanding. The problem isn't the tool, it's the
• 1:43
  lack of oversight. Luke Wroblewski critiques the
• 1:46
  standard chat pattern in "Always Asking People to Ask", arguing
• 1:49
  that forcing users to ask questions assumes they know what
• 1:52
  the tool can do. He found that replacing the prompt with a pre-
• 1:56
  generated answer, like a daily summary, solved the issue of
• 1:59
  capability awareness. This answer-first approach shows
• 2:02
  users the value immediately without requiring active input.
• 2:05
  It removes the friction of figuring out how to start.
• 2:08
  Other articles today from Dan Saffer on researching widgets
• 2:11
  and the Baymard Institute on self-service UX updates.
• 2:21
  Designers are trading technical execution for human ambiguity
• 2:24
  today. We're finding that the bottleneck hasn't disappeared,
• 2:27
  it's just moved to places we didn't expect. Over on
• 2:30
  r/UXDesign, someone is asking what happens to websites if AI
• 2:33
  answers user questions before they ever arrive. The premise is
• 2:36
  sharp. If discovery happens in the chat window, the website
• 2:39
  becomes a validation interface. Users arrive with high intent
• 2:42
  and specific questions about fit. This shifts our job from
• 2:45
  designing for exploration to designing for confirmation. It's
• 2:48
  a narrower scope, but it demands higher precision in how we
• 2:51
  present evidence. There's also a serious warning circulating
• 2:54
  about a new phishing scam targeting Dribbble and LinkedIn.
• 2:57
  Fraudsters pose as clients or peers, sending links to
• 3:00
  repositories, then asking for video calls where they request
• 3:03
  access to your terminal. The goal is stealing crypto wallets
• 3:06
  and browser passwords. It's sophisticated social engineering
• 3:09
  that exploits our natural desire to help peers. The takeaway is
• 3:12
  simple. Never open your terminal for a stranger, even if they
• 3:16
  look like a designer. In the same subreddit, a master's
• 3:18
  student is asking for budget- friendly desktop recommendations
• 3:22
  because their five-year-old laptop is struggling. This
• 3:24
  highlights the financial pressure on students entering
• 3:27
  the field. Reliable hardware is a prerequisite for the job, yet
• 3:30
  it's often the first thing to break under budget constraints.
• 3:34
  It's a reminder that our tools are expensive, and that cost
• 3:37
  barrier is real for many newcomers. Another designer is
• 3:39
  sharing success with organic networking, noting that casual
• 3:42
  moments led to tangible work. They're looking for structured
• 3:46
  advice to replicate this luck. Networking feels high value but
• 3:49
  lacks a clear roadmap. The tension is between the desire
• 3:52
  for structure and the reality that connection is often messy
• 3:55
  and unscripted. Finally, someone bound by an NDA is
• 3:57
  asking how to share case studies with recruiters safely. They're
• 4:01
  weighing expensive Figma plans against free Google Drive
• 4:04
  options. It's a practical dilemma between confidentiality
• 4:06
  and visibility. The field is still figuring out how to prove
• 4:10
  competence without breaking legal agreements. Today's
• 4:12
  discussions reveal that we're optimizing for speed in
• 4:15
  research, but slowing down in security, hiring, and trust. The
• 4:18
  tools change, but the human variables remain stubbornly
• 4:21
  complex.
• 4:29
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:31
  & Friday, September 17 & 18. It's an online event, so you can
• 4:34
  join from anywhere in the world! Tickets are free, thanks to the
• 4:37
  generosity of the community! If it's within your budget, you can
• 4:40
  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
  The MeasuringU literature review on AI moderators shows
• 4:57
  participants speak less and provide shallower insights when
• 5:00
  talking to machines. This suggests automation doesn't
• 5:03
  equal better data quality, because human connection drives
• 5:06
  the nuanced elaboration we actually need. That aligns with
• 5:09
  Patrick Neeman's point that most AI failures are organizational,
• 5:12
  not technical. We start with the tool instead of the user need,
• 5:15
  which creates a bottleneck in decision making. The problem is
• 5:18
  lack of oversight, not the code itself. But Luke Wroblewski
• 5:21
  flips the script by arguing we should stop asking users to ask
• 5:24
  questions. If we replace the prompt with a pre-generated
• 5:27
  answer, we show value immediately. This answer-first
• 5:30
  approach solves the capability awareness issue without
• 5:32
  requiring active input. That's a sharper design move than
• 5:35
  trying to fix the moderation quality. If the website becomes
• 5:38
  a validation interface rather than an exploration space, we
• 5:41
  shift from designing for discovery to designing for
• 5:44
  confirmation. That's a fundamental change in intent.
• 5:46
  It forces us to decide if we want users to confirm what they
• 5:49
  already know or help them find what they don't. The AI
• 5:52
  moderator data shows we lose depth when we remove the human
• 5:55
  element, so the answer-first model risks becoming a shallow
• 5:58
  echo chamber. Or it becomes a highly efficient filter. We
• 6:01
  don't need every user to elaborate on every topic. We
• 6:03
  need the right people to engage deeply, and the rest to get
• 6:06
  quick answers. The goal isn't to replace human connection but to
• 6:09
  reserve it for high-value interactions. So the metric
• 6:12
  shifts from total engagement to engagement quality. Exactly. We
• 6:15
  stop measuring how many questions were asked and start
• 6:18
  measuring how many decisions were made.
• 6:22
  That's The Feed and The Thread for today. We'll catch you next
• 6:25
  time!