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

Transcript

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

• 0:00
  Teams are using AI to work faster, but business outcomes
• 0:02
  aren't moving. So we're just spinning our wheels? Exactly.
• 0:05
  We're trading speed for substance, and that paradox is
• 0:08
  killing product quality.
• 0:14
  Welcome to The Feed and The Thread, brought to you by
• 0:16
  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:27
  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
  We're building faster, but are we building better? That's the
• 0:45
  quiet crisis in design today, where speed is easy, but trust
• 0:49
  and value are hard to earn. Patrick Neeman at UX Design.cc
• 0:52
  makes the case in "Four questions every tool should
• 0:55
  answer (even Figma) about AI training model usage" that trust
• 0:58
  isn't a feeling, it's an auditable set of defaults. He
• 1:01
  points out that companies like Zoom and Slack quietly changed
• 1:04
  their terms to include user data in AI training, often without
• 1:08
  clear consent. That rewrites the assumption that legal compliance
• 1:12
  equals ethical design. Neeman proposes a four-question test
• 1:15
  for designers to evaluate whether their tools truly
• 1:18
  respect user agency. If you can't answer those questions,
• 1:21
  you don't have a product, you have a liability. Scott Berkun
• 1:24
  challenges the myth of rapid adoption in "What is the speed
• 1:28
  of your ideas?", published on his blog Why Design Is Hard. He
• 1:31
  argues that idea velocity is dictated by culture, not merit,
• 1:34
  and that most people resist change because they crave
• 1:37
  stability. So even brilliant ideas stall in risk-averse
• 1:40
  environments like conservative banks. Designers need to stop
• 1:44
  expecting high velocity by default and start measuring how
• 1:47
  fast ideas actually move through their specific organization.
• 1:50
  Speed is a cultural output, not an input. Marty Cagan addresses
• 1:54
  the AI Productivity Paradox in "The AI Productivity Paradox"
• 1:57
  from Silicon Valley Product Group. Teams are using AI to
• 2:00
  work faster, yet business outcomes often remain stagnant
• 2:04
  or decline. This disconnect suggests that velocity without
• 2:07
  value is just expensive noise. Cagan notes that simply adopting
• 2:10
  AI tools for speed is insufficient; teams must ensure
• 2:13
  AI usage aligns with actual user needs. You can't automate your
• 2:17
  way to relevance if you're solving the wrong problems.
• 2:20
  Other reads today from UX Planet on Figma workflows, Phil Morton
• 2:23
  on upskilling, and Codrops on tangible infrastructure.
• 2:34
  Designers are trading polished interfaces for functional
• 2:37
  reality today, and the friction is showing up in unexpected
• 2:40
  places. Over on r/UI_Design, one designer is calling out the
• 2:43
  hidden complexity of email marketing tools, describing them
• 2:46
  as cluttered cockpits that feel decades behind modern design
• 2:49
  standards. It's a stark reminder that speed in development often
• 2:53
  comes at the cost of usability, leaving users to navigate
• 2:56
  archaic systems while the rest of the industry moves forward.
• 2:59
  We build faster, but we often forget to build better, and that
• 3:02
  gap is where trust erodes. In r/UXResearch, a practitioner is
• 3:05
  asking how to bridge the gap between qualitative interviews
• 3:08
  and rigorous quantitative segmentation using surveys. This
• 3:11
  isn't just about filling a skill gap, it's about recognizing that
• 3:15
  intuition alone doesn't build scalable products. When we rely
• 3:18
  solely on stories without the weight of data, we risk building
• 3:21
  for the loudest voices rather than the widest audience, and
• 3:24
  that's a hard lesson to learn in hindsight. Over on r/UI_Design,
• 3:28
  an eighteen-year-old is asking what a normal Tuesday actually
• 3:31
  looks like for a seasoned designer, stripping away the
• 3:34
  glamour of the portfolio. The question reveals a hunger for
• 3:37
  truth over inspiration, and it's a vital check for anyone
• 3:40
  entering the field. We need to be honest about the grind,
• 3:43
  because the reality of daily problem solving is what sustains
• 3:46
  a career, not the highlight reel of shipped features. In
• 3:49
  r/UI_Design, a designer showcases a new enterprise site
• 3:52
  that balances minimal aesthetics with the heavy trust
• 3:55
  requirements of government clients. It proves that modern
• 3:58
  doesn't always mean flashy, and that clarity is often the most
• 4:01
  radical choice in high-stakes industries. When you strip away
• 4:04
  the noise, you're left with whether the design actually
• 4:07
  earns the user's confidence, which is harder than it looks.
• 4:10
  Over on r/UserExperience, a senior designer is venting about
• 4:13
  the degradation of high-fidelity designs during development
• 4:16
  handoff, specifically regarding responsive layouts. This is the
• 4:20
  quiet crisis we keep bumping into, where the vision dies in
• 4:23
  translation because we lack tools that bridge the gap
• 4:25
  between static frames and living code. We need systems that
• 4:28
  preserve intent, not just pixels, if we want to maintain
• 4:31
  the quality we promise. The common thread today isn't just
• 4:35
  about tools or techniques, it's about the integrity of the
• 4:38
  handoff, whether it's to code, to data, or to reality.
• 4:48
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:50
  & Friday, September 17 & 18. It's an online event, so you can
• 4:53
  join from anywhere in the world! Tickets are free, thanks to the
• 4:57
  generosity of the community! If it's within your budget, you can
• 5:00
  purchase a general admission ticket for only twenty six
• 5:02
  dollars - with limited early bird tickets at only fifteen
• 5:05
  dollars. Get tickets now at Chicago Camps dot org.
• 5:15
  Cagan's point about the AI productivity paradox hits hard
• 5:18
  because we're mistaking velocity for value. We're generating
• 5:21
  outputs faster than ever, yet the business outcomes aren't
• 5:23
  moving. It suggests that speed without alignment is just
• 5:26
  expensive noise. That noise is exactly what the community is
• 5:29
  fighting against right now. When designers in r/UI_Design strip
• 5:32
  away the flashy minimalism to focus on trust for government
• 5:35
  clients, they're prioritizing clarity over speed. They know
• 5:38
  that in high-stakes environments, earning confidence
• 5:41
  takes time, and you can't automate that relationship. And
• 5:43
  that connects directly to Berkun's argument that idea
• 5:46
  velocity is a cultural output, not an input. If your culture
• 5:49
  craves stability, adding AI tools won't make ideas move
• 5:52
  faster. It'll just make the resistance to change more
• 5:54
  expensive. We need to measure how fast ideas actually move
• 5:57
  through our specific organization, not how fast the
• 5:59
  tool generates them. But I think we're missing the
• 6:02
  structural piece here. Neeman argues that trust isn't a
• 6:05
  feeling, it's an auditable set of defaults. If we don't have
• 6:08
  transparency around how AI models use our data, no amount
• 6:10
  of cultural alignment will save us. We can't build trust on a
• 6:13
  foundation of hidden terms of service. So the bottleneck
• 6:16
  isn't the tool, or even the culture. It's the integrity of
• 6:19
  the handoff. Whether we're handing off to code, to data, or
• 6:22
  to reality, the gap between qualitative intuition and
• 6:24
  rigorous quantitative validation is where the value gets lost.
• 6:27
  We're building faster, but we're failing to verify if we're
• 6:30
  building the right thing. The metric that matters isn't how
• 6:33
  fast we ship, but how well we explain why we shipped it.
• 6:36
  Exactly. And until transparency becomes a default feature of our
• 6:39
  workflows, speed is just a liability in disguise.
• 6:43
  That's The Feed and The Thread for today. We'll catch you next
• 6:46
  time!