The Feed & The Thread - June 6, 2026

AI coding agents are creating a new psychological trap. Design fixation? That sounds expensive. It costs your creativity, so we're breaking down the four distinct AI design jobs to fix it.

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.

We built tools to remove friction from our workflow, but that very absence of resistance is now trapping us in bad ideas. When building becomes effortless, we lose the pause that lets us question whether we're solving the right problem. Meg Kurdziolek at UX Design.cc makes this case in "The psychological cost of moving too fast". She argues that AI coding agents have slashed financial costs but introduced a heavy psychological toll through design fixation. When teams move too fast from idea to functional prototype, they harden those ideas prematurely. This speed creates confirmation bias and makes designers defensive about their work, even when the sunk cost is low. We stop pivoting because we've already built it. The danger isn't the cost; it's the loss of curiosity. Sarah Gibbons at Nielsen Norman Group clarifies this in "The Four Design Jobs AI Created (So Far)". She argues that the term AI design is too broad and misleading because it masks four distinct types of work. These roles range from generating component variations to defining behavioral parameters for large language models. Recognizing these differences matters because each requires a fundamentally different skill set. Treating them as one discipline dilutes the expertise needed for each. Diogo Andrea details this shift in "The Making of the New Lesse Studio Website: Clarity, Performance, and Intentionality" at Codrops. He shows how rebuilding the Lesse Studio website with self- hosting and deliberate tool selection improved performance and clarity. Moving away from bloated third-party dependencies reduces technical debt and gives designers greater control over the user experience. Intentional choices in infrastructure directly impact the perceived quality of the interface. Control comes from stripping back, not adding on. Other articles today from Nielsen Norman Group on behavioral economics and UX Design.cc on workplace loyalty.

The ease of modern tools is stripping away the necessary friction that forces us to pause and question whether we're solving the right problem. Over on r/UI_Design, a developer admits their word puzzle game menu feels boring because they relied on React Bootstrap to mask limited design skills. This reveals a dangerous comfort zone where technical convenience overrides intentional craft. When building becomes effortless, we lose the resistance that usually signals we're taking shortcuts. In r/UXDesign, a design leader shares a plugin that automates the entire design system lifecycle, cutting setup time from weeks to hours. While speed is tempting, removing the manual labor of token setup and code deployment might also remove the deep understanding of how those systems actually function. We risk deploying solutions we no longer truly comprehend. A cognitive science student in r/UXResearch asks how to transition into design, seeking clarity on daily workflows and portfolio building. Their psychology background is valuable, but the shift from academic inquiry to practical application requires a different kind of rigor. The question matters because it highlights the gap between theoretical knowledge and the messy reality of user engagement. Over on r/UI_Design, a beginner struggles to create distinct icons for locked and unblocked doors in a retro sci-fi game without using generic symbols. This specific challenge underscores the tension between thematic style and universal usability. Good design must communicate clearly even when it tries to look unique. A solo developer in r/UI_Design shares their first app, a study tracker, noting that while users praise the aesthetics, retention is dropping significantly. Positive UI feedback doesn't guarantee long-term engagement if the core problem isn't being solved. This disconnect proves that visual polish can't mask a lack of functional value. We're seeing a pattern where removing friction from the workflow removes the critical thinking required to validate the work itself.

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.

That piece on the psychological cost of speed is the real headline here. We removed friction from our workflows, but we accidentally removed the resistance that forces us to question our assumptions. Exactly. When building is effortless, we lose the pause. I keep thinking about that solo developer in the threads whose app looks great but retains no one. Visual polish can't mask a lack of functional value. And that connects to the confirmation bias Meg Kurdziolek mentioned. We harden ideas prematurely because the prototype exists. The sunk cost is low, but the emotional attachment is high. So the problem isn't the speed. It's that we're treating the first draft as the final answer. We need to reintroduce friction intentionally. Not to slow down, but to force a review of whether we're solving the right problem. I see it differently. I think the issue is that we haven't defined what that pause actually looks like in a new workflow. If we just add steps, we create bottlenecks. We need new rituals, not just more meetings. Agreed. But until we have those rituals, the default is momentum. And momentum favors the wrong ideas. We have to stop confusing velocity with progress. It's a shift in how we measure success. Right. If your process doesn't include a mechanism for killing your favorite idea, you aren't designing. You're just decorating. That's The Feed and The Thread for today. We'll catch you next time!