Latest / The Feed & The Thread / The Feed & The Thread - June 9, 2026

Transcript

The Feed & The Thread - June 9, 2026 · The Feed & The Thread

0:00
AI design isn't ugly. It's fluent. And that's the problem.
0:03
So it looks good but feels wrong? Exactly. The tools are so
0:06
smooth they hide the lack of intent. We need to talk about
0:10
that illusion.
0:15
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:28
available online at feed and thread dot com to submit your
0:31
feeds, or download our app for all the feeds and threads
0:34
delivered right to your pocket.
0:42
We're trading friction for speed, but we're losing the
0:45
intent that makes design hold together. Takuma Kakehi at UX
0:49
Design.cc argues in "AI design isn’t ugly. It’s fluent — and
0:52
that’s the problem." that AI outputs aren't ugly, they're
0:56
just too fluent. That fluency strips away the intentional
0:59
rough edges that give interfaces character. It's like brutalist
1:03
efficiency ignoring human needs. We end up with homogenized
1:06
screens that feel empty. Jeff Gothelf writes about this at his
1:10
blog in "The Amazon AI-tokens problem isn’t an Amazon
1:13
problem.". He says measuring AI token usage is a vanity metric
1:17
trap. Companies are chasing activity instead of value.
1:20
Employees game the system with dummy prompts. It's
1:23
tokenmaxxing, not productivity. Pavel Samsonov at Product Picnic
1:27
explains in "Product teams struggled to create intent. AI
1:30
let them think they could skip it." that AI lets teams skip
1:34
intent. They think they can bypass strategic reasoning. The
1:37
result is a synthetic workflow without oversight. Code ships,
1:41
but the why is missing. That's a dangerous illusion. Other reads
1:44
today from Brad Frost on Tiny Awards and UX Design.cc on AI as
1:48
the third wheel.
1:56
There's a quiet anxiety running through the community today.
2:00
We're moving faster, but we're losing the intent that holds
2:03
design together. Over on r/UXDesign, people are asking if
2:06
we should mine Reddit for social proof. The idea is that raw,
2:10
honest reviews beat polished marketing. But there's a tension
2:13
here. If we use AI to curate that honesty, do we lose the
2:16
authenticity we claimed to value? It matters because trust
2:20
is hard to build and easy to break. We need to ask if
2:23
convenience is worth the cost of genuine connection. In the same
2:26
subreddit, a hot take suggests most portfolios impress
2:29
recruiters rather than show real thinking. The question is what
2:33
we should remove from a standard case study. This reveals a gap
2:36
between hiring metrics and actual competency. We're
2:39
optimizing for the interview, not the job. Practitioners
2:42
should care because this disconnect stalls career growth.
2:46
Real work requires depth, not just a pretty slide deck. A
2:49
lead designer with nine years of experience is struggling with
2:52
their title. They feel UX and UI are too narrow, but product
2:56
design feels inauthentic. This is a common identity crisis. The
2:59
market shifts, but our core skills remain. The so-what's
3:02
clear. Titles are labels, but impact is what matters. We
3:05
should focus on the problems we solve, not the box we check.
3:09
Apple recently added a slider to adjust its new Liquid Glass
3:12
interface. Many see this as an admission that the default
3:15
design was too heavy. It forces users to customize the
3:18
experience. This shows that even giants struggle with balance. We
3:22
prioritize aesthetics, but we often forget usability.
3:25
Designers should watch how companies correct their mistakes
3:28
in public. Finally, r/UI_Design moderators are asking how to
3:32
handle AI-generated submissions. There's a surge in low-effort
3:35
posts that degrade feedback quality. The community worries
3:39
this undermines learning. The tension is real. Speed is easy,
3:42
but craft is hard. We must protect the space for human
3:45
critique. Without it, we lose the ability to grow. We're
3:48
trading friction for speed, but we're losing the intent that
3:52
makes design hold together.
4:00
Chicago Camps is hosting Leadership By Design on Thursday
4:03
& Friday, September 17 & 18. It's an online event, so you can
4:06
join from anywhere in the world! Tickets are free, thanks to the
4:09
generosity of the community! If it's within your budget, you can
4:12
purchase a general admission ticket for only twenty six
4:15
dollars - with limited early bird tickets at only fifteen
4:18
dollars. Get tickets now at Chicago Camps dot org.
4:27
We keep measuring token usage as if activity equals value. That's
4:31
the vanity metric trap. Companies are chasing speed
4:33
while ignoring the strategic reasoning that actually holds a
4:36
product together. It's not just about the metrics. It's that the
4:40
output is too fluent. That smoothness hides the lack of
4:42
intent. We're getting homogenized screens that feel
4:45
empty because the rough edges that showed real thought are
4:48
gone. Exactly. The fluency creates an illusion of
4:51
competence. Teams think they can skip the hard work of defining
4:54
the why. Code ships, but the purpose is missing. That's a
4:57
dangerous disconnect between execution and strategy. And now
5:00
communities are fighting to protect the space for real
5:02
critique. If we can't distinguish between a polished
5:05
AI prompt and a designer's actual judgment, we lose the
5:08
ability to learn. Speed is easy. Craft is hard. So we stop
5:11
optimizing for the interview. We start optimizing for the job.
5:14
Right. Because a pretty slide deck doesn't solve the problem.
5:17
Only the reasoning behind it does.
5:21
That's The Feed and The Thread for today. We'll catch you next
5:24
time!