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

Transcript

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

0:00
Your CEO bypassed you to ask an AI for designs. That's not just
0:03
rude. It's dangerous. Because the tool doesn't understand your
0:07
users, only your prompt. We're breaking down why that matters.
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: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: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:33
delivered right to your pocket.
0:42
We're treating AI like a tool to master, but the real shift is
0:46
deeper. It's about how we bend these tools to fit our thinking,
0:49
not the other way around. That tension between control and
0:52
adaptation is reshaping how we work. Amber Bouabdallah at UX
0:56
Design.cc explores this in "Designing how designers master
0:59
AI". She argues that mastery isn't about correct usage, but
1:02
about personalizing the tool. At Salesforce, designers moved away
1:06
from training decks to shared exploration. A senior researcher
1:09
admitted she wasn't an expert, which normalized the anxiety
1:12
many feel. This shifted the team from seeking rules to seeking
1:16
understanding. Pavel Samsonov at Product Picnic challenges the
1:19
hype in "AI is not the future of software development, but the
1:23
last dying gasp of the past". He argues AI isn't the future of
1:26
software, but the end of the past. He sees Google's move to
1:29
interactive experiences as prioritizing engagement over
1:32
utility. This favors ad revenue over solving user problems with
1:36
minimal effort. It turns AI into a tool for keeping us stuck, not
1:39
moving forward. Michael Buckley at UX Design.cc raises the
1:42
stakes in "The case for catholic philosophy in ethical interface
1:46
design". He contends that current ethical frameworks lack
1:49
moral grounding. Without a shared conception of the good,
1:52
design becomes a negotiation of preferences. He points to
1:55
Catholic philosophy as a source for universal truth. This
1:58
suggests we need deeper anchors than just user satisfaction.
2:02
Other reads today from UX Planet on model comparisons and Brad
2:05
Frost on design system updates.
2:14
It's a busy day in the community, so let's dive
2:17
straight in. Over on r/UXDesign, there's a sharp
2:19
reminder that we often fall in love with solutions before we
2:22
truly understand the problem. It's a classic trap. The
2:25
excitement of a new idea shifts the focus from what problem
2:28
we're solving to how we make that specific idea work. This
2:32
leads to ignored edge cases and selective research. The tension
2:35
here's between the speed of innovation and the rigor of
2:38
validation. We need to resist the urge to prototype too early.
2:41
Slowing down to define the problem actually speeds up the
2:44
right solution later. In r/UXDesign, a designer shares a
2:47
frustrating story where their CEO bypassed them. The leader
2:50
asked a developer to just see what Claude would come up with
2:53
for a design. The community response is empathetic but
2:56
strategic. One user, Scared- Push3893, points out that
2:59
leadership often mistakes AI- generated screens for actual UX
3:02
work. The AI might look convincing fast, but it doesn't
3:05
understand flows or product logic. Another commenter
3:08
suggests using the same AI tools to demonstrate the gap between a
3:12
quick generation and a polished, system-aware design. It's about
3:15
showing the value of professional oversight, not just
3:18
rejecting the tool. Over on r/uxwriting, a writer asks how
3:21
to handle microcopy in dynamic interfaces. When layouts shift
3:24
based on user data, tooltips and error messages can lose their
3:27
context. The challenge is keeping copy spatially logical
3:30
when components stack or collapse. This reveals a deeper
3:33
issue in adaptive design. We're building flexible systems, but
3:37
our language often remains rigid. The solution isn't just
3:40
strict character limits. It's designing copy that survives
3:43
structural change. It requires thinking about language as a
3:46
flexible component, not just static text. In r/UXDesign, a
3:49
designer feels like a spare part in a fast-moving team. They
3:52
describe a painful cycle where their work gets discarded
3:55
because it doesn't match the team's intuitive process. This
3:58
highlights the tension between speed and alignment. When a team
4:02
moves too fast, clarity often gets left behind. The designer
4:05
admits to being a slower worker, which creates a disconnect.
4:08
Rebuilding alignment requires slowing down the process, not
4:11
speeding up the designer. It's about creating space for
4:14
deliberate thought in a culture that prioritizes velocity. Or,
4:17
sometimes, it’s about individuals and teams
4:20
recognizing that there is not a great fit, and identifying a
4:23
path beyond that. Over on r/UXDesign, a solo product
4:26
designer asks if the job is supposed to be this exhausting.
4:29
They spend most of their time explaining rationale to
4:32
stakeholders. A fellow solo designer, sickfee49, validates
4:35
this experience. They note that everyone is driving to build a
4:38
good product. Designers decide how it works, so they owe
4:41
stakeholders a clear rationale. It's not just about making
4:44
things look good. It's about justifying the decisions behind
4:47
the interface. The exhaustion comes from the constant need to
4:50
educate and align. The common thread today is the tension
4:54
between speed and depth. Whether it's AI generation or fast-
4:57
moving teams, we're rushing to outputs. But the real work
5:00
happens in the slow, deliberate thinking that those tools and
5:03
speeds often skip.
5:11
Chicago Camps is hosting Leadership By Design on Thursday
5:14
& Friday, September 17 & 18. It's an online event, so you can
5:17
join from anywhere in the world! Tickets are free, thanks to the
5:20
generosity of the community! If it's within your budget, you can
5:24
purchase a general admission ticket for only twenty six
5:26
dollars - with limited early bird tickets at only fifteen
5:29
dollars. Get tickets now at Chicago Camps dot org.
5:39
Amber Bouabdallah makes a sharp point about designers moving
5:42
from training decks to shared exploration. It normalizes the
5:45
anxiety of not being an expert. This shifts the team from
5:48
seeking rules to seeking understanding. That shift
5:51
matters because we're building flexible systems with rigid
5:54
language. Look at the r/uxwriting discussion on
5:57
dynamic interfaces. Tooltips lose context when layouts shift
6:00
based on user data. We need language that survives
6:02
structural change, not just static text. And that connects
6:05
to the ethical void Michael Buckley highlights. Without a
6:08
shared conception of the good, design becomes a negotiation of
6:12
preferences. If our copy can't adapt, we're just optimizing for
6:15
engagement, not utility. Exactly. Stakeholders want
6:18
rationale, not just pretty screens. The solo designer on
6:21
r/UXDesign noted that everyone is driving to build a good
6:24
product. We owe them a clear reason why the copy works in
6:27
chaos. It's about justifying the decision. So we're treating AI
6:30
like a tool to master, but the real shift is deeper. It's about
6:33
bending these tools to fit our thinking. We need anchors deeper
6:37
than user satisfaction. Right. The gap between rigid copy and
6:40
adaptive design is where the real value lives. We have to
6:43
treat language as a flexible component. Uncomfortable
6:46
territory. But uncomfortable and obsolete have never been the
6:49
same thing. No. And right now the gap between those two words
6:52
is where all the interesting work lives.
6:56
That's The Feed and The Thread for today. We'll catch you next
6:59
time!