Latest / The Feed & The Thread / The Feed & The Thread - August 15, 2026

Transcript

The Feed & The Thread - August 15, 2026 · The Feed & The Thread

• 0:00
  One AI output is just an example, not an evaluation. So
• 0:02
  we're judging the whole system on one lucky guess? Exactly, and
• 0:06
  since the results vary every time, we need to change how we
• 0:09
  test for reliability.
• 0:14
  Welcome to The Feed and The Thread, brought to you by
• 0:17
  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:30
  feeds, or download our app for all the feeds and threads
• 0:33
  delivered right to your pocket.
• 0:42
  The blank page is gone, but the hard part hasn't. We've traded
• 0:45
  the friction of starting for the peril of trusting, and that
• 0:48
  shift exposes a dangerous gap in our workflows. Nicole Alexandra
• 0:52
  Michaelis at UX Design.cc makes this case in "Getting started is
• 0:55
  not getting it right": AI solves the startup drag, but it fails
• 0:59
  at accuracy. She shares a story where a model hallucinated
• 1:02
  budget figures and aggressively defended those errors when
• 1:05
  challenged. That behavior shifts the burden of verification
• 1:09
  entirely back to the human user. And as models get better at
• 1:12
  defending false information, the risk of slop entering
• 1:15
  professional work grows. We can't just accept the first
• 1:18
  draft because it's fast. Raluca Budiu argues at Nielsen Norman
• 1:22
  Group that one output is an example, not an evaluation, in
• 1:25
  "One AI Output Is an Example, Not an Evaluation". AI is
• 1:28
  nondeterministic, meaning it produces varying results for the
• 1:31
  same input. Unlike traditional software, a single successful
• 1:34
  response proves capability, not reliability. Teams need to use
• 1:38
  multiple inputs and confidence intervals to assess performance.
• 1:41
  We have to stop testing for what the system can do and start
• 1:45
  measuring what it consistently does. Nick Babich breaks down
• 1:48
  agentic workflows in "3 Types of Agentic Workflows in Claude
• 1:51
  Code: Safe, Risky, and Dangerous", published on UX
• 1:54
  Planet. He categorizes them into safe, risky, and dangerous tiers
• 1:58
  based on their autonomy. Safe workflows are read-only, while
• 2:01
  dangerous ones make autonomous changes to production
• 2:04
  environments. The author suggests we strictly avoid or
• 2:07
  heavily guard those dangerous autonomous actions.
• 2:10
  Understanding these boundaries is critical to preventing
• 2:13
  catastrophic errors in our systems. Other reads today from
• 2:16
  Rosenfeld Media on leadership salons and CSS-Tricks on custom
• 2:19
  highlight APIs.
• 2:28
  Designers are spending less time staring at empty canvases and
• 2:31
  more time staring at empty databases. The friction of
• 2:34
  starting is gone, but the peril of trusting what comes next has
• 2:37
  taken its place. Over on r/UXResearch, a junior
• 2:40
  researcher in healthtech is asking how to synthesize themes
• 2:43
  when coding a single interview takes an entire afternoon. They
• 2:46
  feel stuck between re-watching raw footage and shipping
• 2:49
  incomplete insights, noting that tools like Dovetail haven't
• 2:52
  reduced the mental load. This reveals a dangerous gap in our
• 2:55
  workflows. We've traded the anxiety of the blank page for
• 2:58
  the paralysis of data overload. The tool didn't fix the process,
• 3:02
  it just made the volume of noise louder. Practitioners need to
• 3:05
  remember that synthesis is a human act, not a storage
• 3:08
  problem. In r/UXResearch, another practitioner is
• 3:10
  preparing for a role interview where they must present a pre-
• 3:14
  assigned research plan. They express uncertainty about what
• 3:17
  to expect, having not interviewed for this role in a
• 3:20
  long time. This vulnerability is common. The question isn't just
• 3:23
  about the plan, it's about defending the methodology behind
• 3:26
  it. When you can't point to your own past work, you have to prove
• 3:30
  you can think through someone else's constraints. That shift
• 3:33
  from execution to justification is where the real trust gap
• 3:36
  lies. Over on r/hci, a prospective student with a CS
• 3:39
  background is asking if the OMSCS HCI specialization is
• 3:42
  viable for UX research roles. They worry that non-studio
• 3:45
  projects won't satisfy industry portfolios or recruiters. This
• 3:48
  highlights a tension between credential and craft. Recruiters
• 3:51
  often look for proof of process, not just a degree. The real
• 3:54
  question is whether the projects force you to make hard trade-
• 3:58
  offs. If the coursework doesn't simulate the pressure of real
• 4:01
  constraints, the portfolio won't hold up. In r/UXResearch,
• 4:04
  someone is highlighting the struggle to organize historical
• 4:07
  findings. They describe disorganized Confluence pages
• 4:10
  that force teams to rely on memory to find past insights.
• 4:13
  This inefficiency creates a barrier to transparency. We have
• 4:16
  the data, but we can't access it. That means we're likely
• 4:19
  repeating old mistakes. The hard part isn't collecting the
• 4:22
  research, it's making it usable for the next person. Over on
• 4:25
  r/ProductDesign, a user posted a survey about a tool to track
• 4:29
  rapid tech updates. The pain point is staying current in a
• 4:32
  landscape that changes faster than we can read. This connects
• 4:35
  back to the trust issue. If we can't track what changed, we
• 4:38
  can't trust our decisions. The gap isn't in the tools, it's in
• 4:41
  the system for verifying what those tools tell us. The blank
• 4:45
  page is gone, but the work of verifying what we build on top
• 4:48
  of it has only gotten heavier.
• 4:57
  Chicago Camps is hosting Leadership By Design on Thursday
• 5:00
  & Friday, September 17 & 18. It's an online event, so you can
• 5:03
  join from anywhere in the world! Tickets are free, thanks to the
• 5:06
  generosity of the community! If it's within your budget, you can
• 5:09
  purchase a general admission ticket for only twenty six
• 5:12
  dollars - with limited early bird tickets at only fifteen
• 5:15
  dollars. Get tickets now at Chicago Camps dot org.
• 5:25
  The idea that we've traded the friction of starting for the
• 5:28
  peril of trusting is the most dangerous shift in our workflows
• 5:31
  right now. We used to worry about the blank page, but now
• 5:34
  we're drowning in verified noise because the tools are defending
• 5:37
  their hallucinations. And that connects directly to what I saw
• 5:40
  in the research community today. A junior researcher is stuck
• 5:43
  because synthesizing one interview takes an afternoon,
• 5:45
  and the tools aren't reducing the mental load. They're just
• 5:48
  making the volume of data louder. The tool didn't fix the
• 5:51
  process, it just amplified the noise. Exactly. The problem is
• 5:54
  we treat the output as an evaluation when it's just an
• 5:57
  example. If a model aggressively defends false budget figures, as
• 6:00
  that UX article noted, the burden of verification shifts
• 6:03
  entirely to us. We're no longer just creators, we're full-time
• 6:06
  auditors of synthetic content. But here's where I push back on
• 6:09
  the audit framing. Auditing implies the work is done, we
• 6:11
  just need to check it. Synthesis isn't a storage problem. It's a
• 6:14
  human act of finding meaning in chaos. If we rely on the tool to
• 6:18
  structure the themes, we lose the nuance that comes from
• 6:20
  sitting with the raw data. I agree that synthesis is human,
• 6:23
  but the volume is the killer. If we have to manually verify every
• 6:26
  hallucination, the cost of truth becomes prohibitive. We need a
• 6:29
  new standard for what counts as a deliverable. Maybe the draft
• 6:32
  is never the product. The product is the verified insight.
• 6:35
  That means the skill set changes from generating content to
• 6:38
  curating truth. We stop valuing speed of output and start
• 6:41
  valuing depth of verification. The teams that survive this
• 6:44
  won't be the ones who use AI to write faster. They'll be the
• 6:47
  ones who build systems that refuse to let unverified claims
• 6:50
  pass. Verification is no longer a quality control step. It's the
• 6:53
  core design work. And until we treat it that way, we're just
• 6:56
  building faster ways to be wrong.
• 6:59
  That's The Feed and The Thread for today. We'll catch you next
• 7:02
  time!