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

Transcript

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

0:00
Designers are losing the power to specify. So what's left for
0:03
us to do? Just critique. And honestly, that shifts the entire
0:06
skill set we've been teaching for decades.
0:13
Welcome to The Feed and The Thread, brought to you by
0:15
Chicago Camps. Leadership By Design is on Thursday and
0:18
Friday, September 17 and 18 and tickets are available now! And
0:21
while you're at it, get caught up on UX fundamentals with five
0:23
minute UX at five em UX dot com. The Feed & The Thread is
0:26
available online at feed and thread dot com to submit your
0:29
feeds, or download our app for all the feeds and threads
0:31
delivered right to your pocket.
0:40
The machine doesn't think. It calculates. That distinction is
0:43
the new battleground for design relevance. Lai-Jing Chu at UX
0:47
Design.cc makes this case in "“What computers can’t do” — and
0:50
what designers should". Computers excel at execution,
0:53
but they lack the capacity for creative struggle. Designers
0:57
must not shy away from difficult, non-linear ideation.
1:00
True innovation lives in that discomfort. Chu also recommends
1:03
improving code literacy to understand agentic AI
1:06
constraints. This technical fluency becomes a protective
1:09
moat against replacement. Adam Elman argues in "The Core Skill
1:13
of Design in the AI Era: Critique" that critique is the
1:16
core design skill now. We're shifting from deterministic
1:19
specs to probabilistic outcomes. Generative AI makes autonomous
1:23
decisions we can't fully specify. Designers must define
1:26
evaluation criteria instead. This changes how we guide user
1:29
experiences. It's less about drawing pixels and more about
1:32
setting boundaries. Carrie Webster writes in "The Impact Of
1:36
Humanoid Robots On Humanity" about humanoid robots moving
1:39
into industry. Advanced AI brains let them learn by
1:42
observation. They can fold laundry or sort parts without
1:45
millions of lines of code. Physical hurdles like battery
1:48
life remain. The concern is where this trajectory leads for
1:51
human labor. Other articles today from CSS-Tricks on
1:54
navigation labels, UX Design.cc on digital complexity, and
1:58
Nielsen Norman Group on context architecture.
2:08
There's a quiet anxiety in the community today. It's not about
2:11
new tools or trends. It's about the fundamental value of human
2:14
judgment in a world that calculates everything else.
2:17
Over on r/UXDesign, a senior designer is opening up about the
2:20
heavy cost of imposter syndrome. They've spent years shipping
2:23
fast in low-maturity companies, skipping research to meet
2:26
deadlines. Now, with a promotion but no formal process artifacts,
2:29
they feel the weight of that gap. It's a stark reminder that
2:33
speed often comes at the expense of depth. And when the machine
2:36
can generate layouts instantly, that depth becomes our only real
2:39
leverage. We aren't competing on speed anymore. We're competing
2:42
on the why behind the design. In the same subreddit, another
2:46
designer is asking how to build a personal brand that feels
2:49
authentic. They note it's harder than branding a company because
2:52
you have to integrate personality with professional
2:55
work. This struggle reveals a deeper tension. If the machine
2:58
doesn't think, it can't have a persona. Your unique voice, your
3:01
specific way of seeing the world, is the thing that can't
3:04
be automated. Branding yourself isn't just marketing. It's
3:07
defining the human perspective you bring to the table. Also in
3:10
r/UXDesign, a junior designer is struggling to showcase case
3:13
studies. They admit to using AI to generate content and copying
3:17
structures from Behance because they lack confidence in their
3:20
own narrative. This is dangerous. Copying templates
3:22
might look good, but it strips away the messy, human reasoning
3:26
that makes design valuable. The machine can mimic the structure.
3:29
It can't mimic the struggle, the failure, and the insight that
3:32
comes from real problem solving. Your story is your proof of
3:35
thought. There's also a discussion about a family chore
3:38
app called WeOrbit. The designer is worried that gamification
3:41
elements like points and animations add unnecessary
3:44
noise. They're asking if the interface is too complex. This
3:47
highlights the balance between engagement and clarity. When we
3:50
add game mechanics, we risk obscuring the core utility. The
3:53
machine can calculate the optimal reward loop. But only a
3:56
human designer can judge whether that loop actually serves the
4:00
user's life, or just distracts them from it. Finally, a
4:02
product designer at top tech companies is stuck on portfolio
4:06
storytelling. They can articulate the process but lack
4:08
a compelling narrative arc. They're getting interviews but
4:11
stalling in later rounds. This suggests that technical
4:14
competence is no longer enough. Hiring managers are looking for
4:17
the ability to frame problems, not just solve them. The machine
4:21
provides the solution. You must provide the context. Without
4:24
that narrative, you're just another pair of hands. With it,
4:27
you're a strategic partner. The pattern here's clear. We're
4:30
moving from proving we can build things to proving we can think
4:33
about them. The distinction is everything.
4:43
Chicago Camps is hosting Leadership By Design on Thursday
4:46
& Friday, September 17 & 18. It's an online event, so you can
4:49
join from anywhere in the world! Tickets are free, thanks to the
4:52
generosity of the community! If it's within your budget, you can
4:55
purchase a general admission ticket for only twenty six
4:58
dollars - with limited early bird tickets at only fifteen
5:01
dollars. Get tickets now at Chicago Camps dot org.
5:11
Adam Elman's point about critique being the core skill
5:14
hits hard when you look at Lai- Jing Chu's argument about
5:17
creative struggle. We're shifting from deterministic
5:19
specs to probabilistic outcomes. The machine calculates the
5:22
optimal path. It doesn't struggle. That lack of friction
5:25
is exactly what we need to preserve in our process. I see
5:28
it differently. The struggle isn't the value. The judgment
5:30
is. Chu says code literacy is a moat against replacement. I
5:33
think that's defensive. The real moat is knowing when the
5:36
calculated path is wrong for the human on the other end. It's not
5:39
about protecting the job. It's about protecting the intent.
5:42
But if you can't read the constraints of the agentic AI,
5:45
how do you know the intent is being met? You're flying blind.
5:48
Technical fluency allows you to set boundaries. Without that,
5:51
your critique is just opinion. Opinion doesn't scale. Code
5:54
does. And yet the community thread on personal branding
5:56
suggests the opposite. Authenticity is the thing that
5:59
can't be automated. If you reduce design to boundary-
6:01
setting and code literacy, you lose the persona. You lose the
6:04
specific way a human sees the world. That voice is what makes
6:07
the critique matter in the first place. Voice without structure
6:11
is noise. You can have the most authentic critique in the world.
6:14
If you don't understand the technical constraints, the
6:16
engineer will ignore it. The battleground isn't creativity
6:19
versus calculation. It's relevance versus irrelevance.
6:22
Maybe. But relevance without humanity is just efficiency. And
6:25
we've plenty of that. The designers who survive won't be
6:27
the ones who just speak code. They'll be the ones who can
6:30
translate human friction into technical constraints that
6:33
actually solve the problem. So the new standard isn't just
6:36
technical literacy. It's translation. Exactly. The gap
6:39
between human friction and machine logic is the only place
6:41
left to build.
6:44
That's The Feed and The Thread for today. We'll catch you next
6:47
time!