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

Transcript

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

• 0:00
  Designers are refusing to be watched while they edit in
• 0:02
  Photoshop. That's a serious breach of professional trust.
• 0:05
  The discomfort is so real it's becoming a retention risk for
• 0:08
  studios.
• 0:12
  Welcome to The Feed and The Thread, brought to you by
• 0:15
  Chicago Camps. The Feed & The Thread is available online at
• 0:18
  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
  The line between a tool and a direct answer is blurring. We
• 0:34
  used to build interfaces for browsing, but now the goal is
• 0:37
  just the result. That shift forces a hard look at trust,
• 0:40
  disclosure, and where the actual value lives in our designs.
• 0:43
  Taylor Dykes at Nielsen Norman Group lays out the PACED
• 0:46
  framework in "When Should You Disclose AI Use? The PACED
• 0:49
  Framework", arguing that user trust depends heavily on context
• 0:52
  rather than a universal rule. The EU AI Act will make
• 0:55
  transparency mandatory by August twenty twenty six, shifting
• 0:58
  disclosure from a voluntary choice to a legal requirement.
• 1:01
  You have to weigh how the AI's involvement alters the
• 1:04
  perception of authenticity. That regulatory deadline changes the
• 1:07
  calculus for every team shipping generated content. Stefanie
• 1:11
  Hutka at Rosenfeld Media reframes the whole question in
• 1:14
  "What should your machines do?", arguing we keep asking "could we
• 1:17
  automate this" when the real test is "should we." Her
• 1:20
  Autonomy Decision Matrix weighs value, risk, and consequence
• 1:23
  instead of raw capability, and her case for humanist automation
• 1:26
  keeps people holding the judgment and empathy while the
• 1:29
  machine takes the repetitive load. The point that lands:
• 1:32
  faster output was never the goal if it erodes trust or piles on
• 1:36
  pressure, so you start from the human outcome you want, not the
• 1:39
  technology you could ship. Hiroshi Sato at UX Design.cc
• 1:42
  explores lateral thinking in "Is this the line for burgers?",
• 1:45
  using the metaphor of a line for burgers to show how solutions
• 1:49
  emerge from unrelated contexts. Designers often miss the best
• 1:52
  fixes because they look only inside their own immediate
• 1:55
  scope. Borrowing insights from other industries helps address
• 1:58
  user needs more effectively. The most effective human centered
• 2:01
  design often comes from looking outside the box. Other reads
• 2:05
  available from Silicon Valley Product Group on expert
• 2:07
  dynamics, UX Planet on testing AI effort levels, and Jeffrey
• 2:11
  Zeldman on the unsung hero of design.
• 2:20
  A sign shop developer built a time tracker that runs offline,
• 2:23
  and a designer is asking if Helvetica is still the right
• 2:26
  choice for clean work. These are small, specific questions about
• 2:29
  where our tools and our boundaries actually sit. Over
• 2:32
  on r/Design, a designer is struggling with a manager who
• 2:34
  wants to watch live Photoshop edits. The core tension is the
• 2:37
  clash between the creative flow that requires privacy and a
• 2:40
  management style that treats observation as oversight. It's a
• 2:44
  professional boundary issue that gets missed because it's framed
• 2:47
  as a technical collaboration. We need to be comfortable saying
• 2:50
  that the process isn't the product. In r/ProductDesign,
• 2:53
  someone is dealing with a physical product that gets high
• 2:56
  traffic but low sales. The issue is that the value is
• 2:58
  experiential, which breaks the standard problem-solution
• 3:01
  marketing narrative. This highlights a gap in how we
• 3:04
  communicate value when the result is a feeling rather than
• 3:07
  a feature. If we can't articulate the "why" behind the
• 3:09
  experience, the conversion will always lag behind the curiosity.
• 3:13
  Back in r/Design, there's a question about whether Helvetica
• 3:16
  is still the gold standard for clean design. With AI-generated
• 3:19
  maximalism everywhere, the neutral choice feels like a
• 3:21
  statement in itself. It's not just about legibility anymore;
• 3:24
  it's about resisting the noise. Choosing a standard typeface is
• 3:28
  now a deliberate act of restraint in a field that's
• 3:30
  increasingly saturated with visual clutter. And over on
• 3:33
  r/Design, that sign shop developer shared a free, offline
• 3:36
  time tracker for design work. It's a simple tool for
• 3:39
  categorizing time between initial designs and revisions to
• 3:41
  help with quoting. It's a reminder that the most valuable
• 3:44
  tools are often the simplest ones that respect our privacy
• 3:47
  and speed, rather than the most complex ones that demand our
• 3:50
  data. The common thread here is that value is moving from the
• 3:53
  interface to the intent, whether that's a font choice, a tool, or
• 3:57
  a boundary.
• 4:05
  The Feed and The Thread is brought to you by Chicago Camps.
• 4:07
  For a weekly and monthly exploration of the patterns and
• 4:10
  signals across UX, you can also check out Patterns and Signals
• 4:13
  at the website patterns and signals dot com. Chicago Camps
• 4:16
  will have more events in 2027. You can submit to be a speaker
• 4:18
  at a future event at Chicago Camps dot org.
• 4:28
  The most concrete story today is Taylor Dykes' PACED framework,
• 4:31
  because the EU AI Act turns AI disclosure into law by August.
• 4:34
  "When do you tell users the AI was involved" stops being a
• 4:37
  style choice and becomes a compliance line every team has
• 4:39
  to draw. But Stefanie Hutka pushes that question upstream,
• 4:42
  and that's where the real work is. Before you disclose that a
• 4:45
  machine acted, you decide whether it should have acted at
• 4:48
  all. Her "should we automate this" test comes before Dykes'
• 4:51
  "when do we disclose it." Right, because you can disclose
• 4:54
  perfectly and still have automated something you never
• 4:56
  should have. Hutka's Autonomy Decision Matrix weighs value,
• 4:59
  risk, and consequence before capability, and her humanist
• 5:02
  automation keeps the person holding judgment while the
• 5:05
  machine takes the repetitive load. So the two frameworks
• 5:08
  work opposite ends of the same trust problem. Teams keep
• 5:10
  bolting trust on at the end as a disclosure label. It actually
• 5:13
  starts as a decision at the very beginning, and faster output
• 5:16
  that erodes trust was never a win. Put together, they're a
• 5:19
  sequence: decide whether the machine should act, then be
• 5:22
  honest that it did. Trust gets built at that first decision.
• 5:25
  Disclosure just keeps it honest downstream.
• 5:29
  That's The Feed and The Thread for today. We'll catch you next
• 5:32
  time!