The Feed & The Thread - June 13, 2026

Designers are losing the power to specify. So what's left for us to do? Just critique. And honestly, that shifts the entire skill set we've been teaching for decades.

Welcome to The Feed and The Thread, brought to you by Chicago Camps. Leadership By Design is on Thursday and Friday, September 17 and 18 and tickets are available now! And while you're at it, get caught up on UX fundamentals with five minute UX at five em UX dot com. The Feed & The Thread is available online at feed and thread dot com to submit your feeds, or download our app for all the feeds and threads delivered right to your pocket.

The machine doesn't think. It calculates. That distinction is the new battleground for design relevance. Lai-Jing Chu at UX Design.cc makes this case in "“What computers can’t do” — and what designers should". Computers excel at execution, but they lack the capacity for creative struggle. Designers must not shy away from difficult, non-linear ideation. True innovation lives in that discomfort. Chu also recommends improving code literacy to understand agentic AI constraints. This technical fluency becomes a protective moat against replacement. Adam Elman argues in "The Core Skill of Design in the AI Era: Critique" that critique is the core design skill now. We're shifting from deterministic specs to probabilistic outcomes. Generative AI makes autonomous decisions we can't fully specify. Designers must define evaluation criteria instead. This changes how we guide user experiences. It's less about drawing pixels and more about setting boundaries. Carrie Webster writes in "The Impact Of Humanoid Robots On Humanity" about humanoid robots moving into industry. Advanced AI brains let them learn by observation. They can fold laundry or sort parts without millions of lines of code. Physical hurdles like battery life remain. The concern is where this trajectory leads for human labor. Other articles today from CSS-Tricks on navigation labels, UX Design.cc on digital complexity, and Nielsen Norman Group on context architecture.

There's a quiet anxiety in the community today. It's not about new tools or trends. It's about the fundamental value of human judgment in a world that calculates everything else. Over on r/UXDesign, a senior designer is opening up about the heavy cost of imposter syndrome. They've spent years shipping fast in low-maturity companies, skipping research to meet deadlines. Now, with a promotion but no formal process artifacts, they feel the weight of that gap. It's a stark reminder that speed often comes at the expense of depth. And when the machine can generate layouts instantly, that depth becomes our only real leverage. We aren't competing on speed anymore. We're competing on the why behind the design. In the same subreddit, another designer is asking how to build a personal brand that feels authentic. They note it's harder than branding a company because you have to integrate personality with professional work. This struggle reveals a deeper tension. If the machine doesn't think, it can't have a persona. Your unique voice, your specific way of seeing the world, is the thing that can't be automated. Branding yourself isn't just marketing. It's defining the human perspective you bring to the table. Also in r/UXDesign, a junior designer is struggling to showcase case studies. They admit to using AI to generate content and copying structures from Behance because they lack confidence in their own narrative. This is dangerous. Copying templates might look good, but it strips away the messy, human reasoning that makes design valuable. The machine can mimic the structure. It can't mimic the struggle, the failure, and the insight that comes from real problem solving. Your story is your proof of thought. There's also a discussion about a family chore app called WeOrbit. The designer is worried that gamification elements like points and animations add unnecessary noise. They're asking if the interface is too complex. This highlights the balance between engagement and clarity. When we add game mechanics, we risk obscuring the core utility. The machine can calculate the optimal reward loop. But only a human designer can judge whether that loop actually serves the user's life, or just distracts them from it. Finally, a product designer at top tech companies is stuck on portfolio storytelling. They can articulate the process but lack a compelling narrative arc. They're getting interviews but stalling in later rounds. This suggests that technical competence is no longer enough. Hiring managers are looking for the ability to frame problems, not just solve them. The machine provides the solution. You must provide the context. Without that narrative, you're just another pair of hands. With it, you're a strategic partner. The pattern here's clear. We're moving from proving we can build things to proving we can think about them. The distinction is everything.

Chicago Camps is hosting Leadership By Design on Thursday & Friday, September 17 & 18. It's an online event, so you can join from anywhere in the world! Tickets are free, thanks to the generosity of the community! If it's within your budget, you can purchase a general admission ticket for only twenty six dollars - with limited early bird tickets at only fifteen dollars. Get tickets now at Chicago Camps dot org.

Adam Elman's point about critique being the core skill hits hard when you look at Lai- Jing Chu's argument about creative struggle. We're shifting from deterministic specs to probabilistic outcomes. The machine calculates the optimal path. It doesn't struggle. That lack of friction is exactly what we need to preserve in our process. I see it differently. The struggle isn't the value. The judgment is. Chu says code literacy is a moat against replacement. I think that's defensive. The real moat is knowing when the calculated path is wrong for the human on the other end. It's not about protecting the job. It's about protecting the intent. But if you can't read the constraints of the agentic AI, how do you know the intent is being met? You're flying blind. Technical fluency allows you to set boundaries. Without that, your critique is just opinion. Opinion doesn't scale. Code does. And yet the community thread on personal branding suggests the opposite. Authenticity is the thing that can't be automated. If you reduce design to boundary- setting and code literacy, you lose the persona. You lose the specific way a human sees the world. That voice is what makes the critique matter in the first place. Voice without structure is noise. You can have the most authentic critique in the world. If you don't understand the technical constraints, the engineer will ignore it. The battleground isn't creativity versus calculation. It's relevance versus irrelevance. Maybe. But relevance without humanity is just efficiency. And we've plenty of that. The designers who survive won't be the ones who just speak code. They'll be the ones who can translate human friction into technical constraints that actually solve the problem. So the new standard isn't just technical literacy. It's translation. Exactly. The gap between human friction and machine logic is the only place left to build. That's The Feed and The Thread for today. We'll catch you next time!