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

Transcript

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

• 0:00
  The boardroom doesn't care about delightful experiences anymore.
• 0:03
  So what actually gets the budget approved? You have to prove the
• 0:06
  return on investment with hard numbers, which means leaving the
• 0:09
  vague promises behind for good.
• 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:20
  Friday, September 17 and 18 and tickets are available now! And
• 0:23
  while you're at it, get caught up on UX fundamentals with five
• 0:26
  minute UX at five em UX dot com. The Feed & The Thread is
• 0:29
  available online at feed and thread dot com to submit your
• 0:32
  feeds, or download our app for all the feeds and threads
• 0:35
  delivered right to your pocket.
• 0:43
  We build faster now, but we test later. That gap is closing, yet
• 0:47
  the stakes for trust and value remain higher than ever. Megan
• 0:51
  Chan at Nielsen Norman Group argues in "Test Complex
• 0:54
  Interactions Earlier with AI Prototyping" that AI lets teams
• 0:57
  test complex interactions much earlier. We used to skip testing
• 1:01
  filters or dashboards because building them by hand took too
• 1:04
  long. Now, designers can generate high-fidelity
• 1:07
  prototypes with dynamic data in a single day. This shifts
• 1:10
  testing from simple happy paths to messy, real-world usage
• 1:13
  before development starts. Alex Williams at Smashing Magazine
• 1:17
  makes the case in "Building A UX ROI Case That Survives The
• 1:20
  Boardroom" that UX needs provable ROI, not just
• 1:23
  delightful experiences. He uses a fictional B2B SaaS company to
• 1:27
  show how to turn vague goals into specific OKRs. The key is
• 1:30
  interviewing stakeholders to find hidden problems like high
• 1:34
  churn or support bottlenecks. You must define clear objectives
• 1:37
  to secure budget and boardroom approval. Pedro A. Brêtas at UX
• 1:41
  Design.cc explores the tension in "Your first draft now has a
• 1:44
  log" regarding AI tools and employee privacy. These tools
• 1:47
  act as confidential confidants for users, but HR sees the data
• 1:51
  as a resource for monitoring retention risk. Traditional
• 1:54
  alignment mechanisms fail here because employees can't
• 1:57
  uninstall mandatory enterprise software. Designers must
• 2:00
  navigate this conflict between user trust and corporate
• 2:04
  oversight. Other reads today from Silicon Valley Product
• 2:07
  Group on holding opinions loosely, Jeffrey Zeldman on
• 2:10
  professional identity, and Codrops on nostalgic digital
• 2:13
  experiences.
• 2:21
  Designers are arguing less about which tools to use and more
• 2:24
  about who gets to decide what good design actually looks like
• 2:28
  today. Over on r/UI_Design, the community is identifying a
• 2:31
  distinct accent in AI-generated websites. The argument is that
• 2:34
  while these tools build fast, they rely on predictable tropes
• 2:37
  like purple gradients and vague buzzwords. It creates a
• 2:40
  recognizable sameness that lacks authentic brand identity. We
• 2:43
  build faster now, but that speed often comes at the cost of
• 2:47
  nuance. The stake here's trust. If a site feels generic, users
• 2:50
  don't just lose interest, they lose confidence in the product
• 2:53
  behind it. Authenticity is becoming the new scarcity. In
• 2:56
  r/hci, a graduate student is questioning whether a course in
• 2:59
  systems thinking is worth the effort for a UX professional.
• 3:02
  They want to stand out but fear it might just be unnecessary
• 3:06
  overhead. This anxiety is common among junior designers trying to
• 3:09
  define their unique value. The question reveals a shift in the
• 3:12
  field. Standard UX skills are becoming table stakes.
• 3:15
  Understanding how design fits into larger technical and
• 3:18
  organizational systems is what separates competent execution
• 3:21
  from strategic impact. It's not just about the interface
• 3:24
  anymore. It's about the infrastructure that supports it.
• 3:27
  Over on r/UI_Design, someone is analyzing Apple's design
• 3:30
  guidelines for the upcoming iPhone Duo. The strategy
• 3:33
  prioritizes adaptive, resizable interfaces over creating unique
• 3:36
  layouts for every fold state. Apple encourages relying on
• 3:39
  existing principles like size classes rather than building
• 3:42
  multiple versions of every screen. This is a pragmatic
• 3:45
  approach to complexity. It suggests that robust design
• 3:48
  systems are more valuable than bespoke solutions for every
• 3:51
  hardware variation. It also reinforces the idea that testing
• 3:54
  later is risky. If the foundation isn't flexible, the
• 3:57
  whole structure fails when the device changes. In
• 4:00
  r/ProductDesign, a designer is asking how companies structure
• 4:03
  their teams in relation to engineering departments. They're
• 4:06
  looking for data on lead structures and headcounts. This
• 4:09
  inquiry highlights a persistent industry curiosity about optimal
• 4:13
  team composition. The structure of a design team directly
• 4:16
  influences how quickly and effectively products are built.
• 4:19
  If design is siloed, the gap between building and testing
• 4:22
  widens. If it's integrated, feedback loops tighten. The way
• 4:25
  we organize ourselves is just as important as the tools we use.
• 4:28
  Today's discussions point to a clear trend. We're moving away
• 4:31
  from isolated UI decisions toward integrated, systemic
• 4:34
  thinking that values long-term trust over short-term speed.
• 4:45
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:47
  & Friday, September 17 & 18. It's an online event, so you can
• 4:50
  join from anywhere in the world! Tickets are free, thanks to the
• 4:54
  generosity of the community! If it's within your budget, you can
• 4:57
  purchase a general admission ticket for only twenty six
• 4:59
  dollars - with limited early bird tickets at only fifteen
• 5:02
  dollars. Get tickets now at Chicago Camps dot org.
• 5:12
  The tension in Pedro Brêtas' piece about AI logs is
• 5:14
  structural. We have tools acting as confidential confidants while
• 5:18
  HR treats that same data as a retention risk metric. The
• 5:20
  problem isn't the technology. It's that traditional alignment
• 5:23
  mechanisms fail when employees can't uninstall mandatory
• 5:26
  enterprise software. That's the trap. We're asking designers to
• 5:29
  navigate a conflict where the user has no exit strategy. If
• 5:32
  the tool logs your draft, you aren't trusting it. You're
• 5:35
  complying with it. And compliance doesn't build the
• 5:37
  kind of loyalty that actually reduces churn. It just builds
• 5:40
  resentment that shows up in support tickets later. Exactly.
• 5:43
  Which circles back to the ROI argument from Smashing Magazine.
• 5:46
  If you can't prove the value of a delightful experience, you
• 5:49
  lose budget. But if you prove the value by monitoring that
• 5:52
  experience, you lose trust. The boardroom wants the metric. The
• 5:55
  user wants the privacy. We're designing for the middle, where
• 5:58
  neither side gets what they actually want. So we stop
• 6:01
  treating the log as a neutral record. We treat it as a design
• 6:04
  decision. If we're going to capture that data, we need to
• 6:06
  make the trade-off explicit to the user, not hidden in the
• 6:09
  terms of service. Transparency becomes the feature. Hiding the
• 6:12
  surveillance is the bug. Transparency is expensive. It
• 6:15
  slows down the workflow the company is paying for. And
• 6:18
  that's the point. If the cost of trust is higher than the cost of
• 6:21
  speed, the product is broken. We have to value the relationship
• 6:24
  more than the render time.
• 6:27
  That's The Feed and The Thread for today. We'll catch you next
• 6:30
  time!