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

Transcript

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

• 0:00
  Wearables are reducing complex human stress into a single
• 0:02
  score. That feels like a dangerous oversimplification. It
• 0:05
  is, and the data suggests we're trusting the label over the
• 0:08
  feeling.
• 0:13
  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:21
  our app for all the feeds and threads delivered right to your
• 0:24
  pocket.
• 0:31
  Designers often assume the craft is the hardest part, but today's
• 0:35
  stories suggest the real friction lies elsewhere. It's
• 0:38
  about who pays, what we measure, and how we hide costs. Scott
• 0:41
  Berkun at On Scott Berkun's blog makes the case in "The 5 big
• 0:45
  lessons designers must learn" that professional success
• 0:48
  depends less on pure style and more on understanding business
• 0:51
  realities. He argues that designers must convince
• 0:54
  stakeholders to invest in quality, noting that someone has
• 0:57
  to pay for the work. This shifts the role from decision-maker to
• 1:00
  adviser, where influence and trust are the primary tools. The
• 1:04
  uncomfortable truth is that if you can't navigate power
• 1:07
  structures, your craft doesn't matter. Catherine Chu at UX
• 1:10
  Design.cc examines the limits of quantification in "Can stress be
• 1:14
  quantified?", asking if stress can truly be measured by
• 1:17
  wearables. Devices like Oura and Garmin reduce complex human
• 1:20
  states into simple scores, tracking physiological signals
• 1:23
  like heart rate variability. But these metrics often fail to
• 1:26
  capture psychological context, misclassifying excitement or
• 1:30
  exercise as distress. The gap between physiological data and
• 1:33
  perceived experience remains a critical blind spot in our
• 1:36
  health tech. Malin Liljeblad at Baymard Institute reveals a core
• 1:40
  friction in "New Event Ticketing UX Research: 3 Key Takeaways",
• 1:43
  based on four hundred sixty- three usability test sessions.
• 1:47
  Users struggle significantly with opaque pricing and late-
• 1:50
  stage surcharges, which drives high abandonment rates for live
• 1:53
  events. Unlike standard e-commerce, tickets can't be
• 1:56
  returned, so design must build confidence through early
• 1:59
  transparency. The study highlights that hiding costs is
• 2:02
  a direct cause of user hesitation and lost sales.
• 2:05
  Other reads are available from UX Design.cc on regulating AI
• 2:08
  and Rosenfeld Media on designing your own path.
• 2:18
  A volunteer is trying to count petition signatures, and the
• 2:21
  interface is the bottleneck. Over on r/UI_Design, a developer
• 2:24
  is building open-source petition software and asking whether
• 2:28
  radio buttons or checkboxes better serve the data entry
• 2:31
  process. The tension is between minimizing training for
• 2:34
  volunteers and ensuring legal integrity in the count. It's a
• 2:37
  reminder that the right control isn't just about aesthetics, but
• 2:40
  about reducing the cognitive load on the people doing the
• 2:43
  heavy lifting. In r/UI_Design, a creator of an app called
• 2:47
  Daymark is asking how to move past a "good looking" UI into
• 2:50
  actual interaction design mastery. They can see the
• 2:52
  surface is polished, but they can't identify the specific
• 2:56
  friction points in the animation or flow. This highlights a
• 2:59
  common gap where subjective feelings of quality don't
• 3:02
  translate into actionable critiques, leaving designers
• 3:04
  stuck in a loop of surface-level tweaks. Over on r/Design,
• 3:08
  someone is asking why accessible packaging isn't discussed more,
• 3:11
  citing a relative who struggles to open standard products. The
• 3:14
  industry often prioritizes shelf appeal over grip strength and
• 3:18
  dexterity, assuming perfect physical capability. It's a
• 3:21
  clear signal that accessibility is often an afterthought, rather
• 3:24
  than a foundational constraint that shapes the design from the
• 3:28
  very start. In r/Design, a practitioner is asking how to
• 3:31
  handle scope creep, specifically whether to check contracts, push
• 3:34
  back, or renegotiate. This is a universal pain point for
• 3:37
  freelancers and agency staff who are trying to maintain
• 3:40
  professional boundaries without burning out. The question
• 3:43
  reveals that the hardest part of design is often not the craft
• 3:46
  itself, but the negotiation of effort and compensation. The
• 3:50
  contractor request that sat with zero engagement shows that
• 3:53
  clarity is the first currency of professional respect.
• 4:03
  The Feed and The Thread is brought to you by Chicago Camps.
• 4:06
  For a weekly and monthly exploration of the patterns and
• 4:09
  signals across UX, you can also check out Patterns and Signals
• 4:12
  at the website patterns and signals dot com. Chicago Camps
• 4:15
  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:27
  There's a striking disconnect in today's feed between the promise
• 4:30
  of precision and the reality of perception. Catherine Chu's
• 4:33
  piece on quantifying stress highlights how devices like Oura
• 4:36
  and Garmin reduce complex human states into simple scores, yet
• 4:39
  they often misclassify excitement or exercise as
• 4:41
  distress. The gap between physiological data and perceived
• 4:44
  experience remains a critical blind spot, meaning we're
• 4:46
  measuring the body's response without understanding the mind's
• 4:49
  context. That misclassification is exactly the friction we see
• 4:52
  in the community. In r/UI_Design, a creator named
• 4:54
  Daymark describes hitting a wall where the interface looks
• 4:57
  polished, but they can't identify the specific friction
• 4:59
  points in the flow. It's the same problem as the wearable
• 5:02
  trying to read a heart rate spike. You have a signal, but
• 5:05
  without the context of what the user is actually feeling or
• 5:07
  trying to do, that signal is just noise. You can't debug a
• 5:10
  feeling with a score. But I think we're underestimating the
• 5:13
  value of the score itself, even if it's imperfect. Scott Berkun
• 5:16
  argues that professional success depends less on pure style and
• 5:19
  more on understanding business constraints. If we discard
• 5:21
  quantitative data because it lacks nuance, we lose the
• 5:24
  leverage needed to defend design decisions. The metric is the
• 5:27
  currency. Without it, the "friction" you described becomes
• 5:29
  just an opinion, and opinions don't carry weight in a budget
• 5:32
  meeting. That's where I push back. Currency is only useful if
• 5:35
  the exchange rate is fair. The Baymard Institute study on
• 5:38
  ticketing shows that hiding costs drives abandonment because
• 5:40
  users don't trust the opacity. If we treat design metrics the
• 5:43
  same way - hiding the context behind a clean number - we're
• 5:46
  doing the same thing. We're asking people to trust the
• 5:48
  output without seeing the input. The community is ready to move
• 5:51
  past "good looking" UIs and into interaction mastery, but that
• 5:54
  requires showing the work and the result. So the goal is to
• 5:57
  demand the context alongside the data. A metric without a
• 6:00
  narrative is just a number, and a narrative without a metric is
• 6:03
  just a story. Exactly. The field needs to stop treating
• 6:05
  empathy and analytics as separate departments. They're
• 6:08
  the same problem viewed from different angles, and until we
• 6:10
  integrate them, we're just guessing.
• 6:14
  That's The Feed and The Thread for today. We'll catch you next
• 6:17
  time!