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

Transcript

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

• 0:00
  A new prototype is designed to know when to stay silent. So
• 0:03
  it's waiting for you to ask? No, it actively decides when your
• 0:06
  input would actually help.
• 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:23
  pocket.
• 0:30
  AI is everywhere, yet the gap between the tool and the user is
• 0:34
  widening. We're seeing a pattern today: the need to bridge the
• 0:37
  distance between machine output and human intent, whether
• 0:40
  through color, code, or communication. Theresa-Marie
• 0:43
  Rhyne at UX Design.cc outlines a five-step workflow in "Five-step
• 0:47
  color balancing with GenAI", using Gemini to balance color
• 0:50
  schemes. She argues that we must feed qualitative data and
• 0:53
  specific constraints into the AI, not just generic prompts.
• 0:56
  This turns the tool into a collaborative partner for
• 0:59
  iterative design. It allows designers to test variations
• 1:02
  quickly while keeping accessibility intact. The goal
• 1:05
  is speed, but the method requires precision. Christian
• 1:08
  Crumlish at Chicago Camps shares a candid retrospective in
• 1:11
  "Hilarious Tales of Failure: What a Year of Building With AI
• 1:15
  Taught Me" about a year of building with AI. He details
• 1:18
  specific failures, including agents that hallucinated facts
• 1:21
  and silent job errors during server reboots. His core point
• 1:24
  is that the human must own the feedback loop to maintain trust.
• 1:28
  Normalizing these messy failures helps alleviate the anxiety of
• 1:31
  feeling behind. It reminds us that learning is an ongoing
• 1:34
  journey. Dane DeSutter and Stephanie Scopelitis explore
• 1:37
  gesture in "What gestures reveal about users with Dane DeSutter
• 1:41
  and Stephanie Scopelitis", arguing that hands reveal mental
• 1:44
  models that words miss. They distinguish spontaneous gestures
• 1:47
  from sign language, noting that gestures are contextual and
• 1:50
  synthetic. This approach helps researchers clarify ambiguous
• 1:54
  ideas during user studies. It moves observation beyond
• 1:57
  intuition to systematic interpretation. The body often
• 2:00
  speaks before the mouth does. Also out today: Baymard
• 2:03
  Institute on B2B UX benchmarks, UX Planet on LLM comparisons for
• 2:06
  web design, and UX Design.cc on adaptive accessibility.
• 2:16
  A CS student built a prototype for an AI that chooses when to
• 2:20
  stay silent, and the field is asking if that restraint is the
• 2:23
  missing piece. Over on r/hci, this student presents "QUIET," a
• 2:26
  system designed to sit between passive waiting and aggressive
• 2:30
  task takeover. The core idea is an interface that gauges user
• 2:33
  intent before deciding whether to offer help or simply wait.
• 2:36
  This matters because most current AI tools default to
• 2:39
  constant availability, which often creates noise rather than
• 2:42
  clarity. The tension here's defining the exact threshold
• 2:45
  where assistance becomes intrusion. If we can map that
• 2:48
  boundary, we stop forcing users to manage the tool and start
• 2:51
  letting the tool manage its own presence. In r/DesignSystems, a
• 2:54
  designer is asking whether AI compliance patterns should
• 2:57
  become part of the core design system. The argument is that
• 3:01
  teams are independently building transparency notices, human
• 3:04
  review states, and distinction markers for AI data. This
• 3:07
  creates a fragmented experience where the same regulatory
• 3:10
  requirement looks different in every product. The so-what's
• 3:13
  clear: if these are recurring interaction problems, they need
• 3:16
  shared, standardized components. Treating AI compliance as a
• 3:19
  utility rather than a one-off feature ensures consistency and
• 3:23
  reduces the cognitive load on both users and design teams. A
• 3:26
  graphic design graduate in r/hci is mapping out a path into UX,
• 3:29
  specifically seeking a European Master's program that avoids
• 3:33
  heavy coding. They're weighing options like Aalto and TU Delft,
• 3:36
  prioritizing industry connections over technical
• 3:38
  depth. This question highlights a persistent divide in the
• 3:42
  field: the push toward technical fluency versus the enduring
• 3:45
  value of strategic, human- centered thinking. For
• 3:47
  practitioners, this signals that the entry point into UX is still
• 3:51
  broad, provided you can articulate the value of non-
• 3:54
  technical skills in a technical landscape. Today's discussions
• 3:57
  all point to the same gap: the distance between machine output
• 4:00
  and human intent. Whether it's an AI choosing silence or a
• 4:03
  design system standardizing compliance, the goal is the
• 4:06
  same. We're trying to build interfaces that respect the
• 4:09
  user's agency rather than overriding it. That's the real
• 4:12
  work happening right now.
• 4:21
  The Feed and The Thread is brought to you by Chicago Camps.
• 4:24
  For a weekly and monthly exploration of the patterns and
• 4:26
  signals across UX, you can also check out Patterns and Signals
• 4:29
  at the website patterns and signals dot com. Chicago Camps
• 4:32
  will have more events in 2027. You can submit to be a speaker
• 4:35
  at a future event at Chicago Camps dot org.
• 4:45
  The QUIET prototype on r/hci is proposing a system that chooses
• 4:48
  when to stay silent, gauging user intent before offering
• 4:50
  help. It's a direct counter to the current default where AI
• 4:53
  tools are constantly available, creating noise instead of
• 4:56
  clarity. The core argument is that defining the threshold
• 4:58
  where assistance becomes intrusion is the missing piece.
• 5:01
  That threshold is the whole game. Most tools right now force
• 5:04
  the user to manage the interaction, constantly deciding
• 5:06
  when to ignore the prompt. If the system can manage its own
• 5:09
  presence, we stop treating the tool like a needy colleague and
• 5:12
  start treating it like a competent partner. That shift
• 5:14
  changes the cognitive load of the entire workflow. I'd push
• 5:17
  back on the idea that we can just map that boundary
• 5:19
  universally. Intent is context- dependent, and a system that
• 5:22
  guesses wrong is worse than one that's quiet. If QUIET decides
• 5:25
  to speak when the user is in deep flow, it breaks trust
• 5:28
  faster than a silent tool would. The risk of false positives is
• 5:31
  high, and the community needs to be careful about assuming we can
• 5:34
  solve this with a single heuristic. You're right that
• 5:36
  false positives are dangerous, but that's an implementation
• 5:39
  detail, not a fundamental flaw. The goal is to be less intrusive
• 5:42
  than the status quo. We've spent years building tools that demand
• 5:45
  attention by default. A tool that defaults to restraint is a
• 5:48
  better starting point, even if it misses the mark sometimes.
• 5:50
  The field is moving away from "always on" toward "context-
• 5:53
  aware," and that direction is correct. I agree the direction
• 5:56
  is right, but the metric for success has to change. We need
• 5:59
  to measure silence as a feature. If we keep optimizing for
• 6:01
  engagement, we'll keep building tools that talk too much. The
• 6:04
  industry has to redefine what a successful interaction looks
• 6:07
  like, and that means valuing the moments where the tool doesn't
• 6:10
  intervene. Exactly. The value is in the quality of the moments
• 6:13
  when the tool does speak. When we flip that incentive, we stop
• 6:16
  designing for attention and start designing for trust.
• 6:18
  That's the shift that actually changes how people work with
• 6:21
  these systems. The definition of a helpful tool is changing
• 6:24
  from "always available" to "right there when needed." And
• 6:27
  the tools that understand that difference are the ones that'll
• 6:29
  actually fit into the work, rather than interrupting it.
• 6:34
  That's The Feed and The Thread for today. We'll catch you next
• 6:37
  time!