The Feed & The Thread - June 8, 2026

AI handles the pixels now. So what's left for designers? Strategy, because emotional intelligence is the one competitive advantage machines simply can't replicate.

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've spent years treating speed as the ultimate metric for design success. But as automation handles the mechanical work, that metric is becoming a trap. The real value isn't in how fast you can push pixels, but in how deeply you can understand the human context behind them. Daleen Rabe at UX Design.cc makes this case in "Let the AI have the pixels", arguing that designers must stop competing with machines on precision. The shift is from pixel-pushing to practical wisdom, which means making sound judgments in ambiguous situations. AI can generate layouts, but it can't replicate the nuanced understanding of ethics or business goals. Your competitive advantage is no longer speed, but strategic judgment. Roman Pichler at his own blog expands this idea in "Emotional Intelligence for Product Managers: The Competitive Advantage AI Can’t Replicate", focusing on the emotional intelligence that product managers need. He contrasts IQ with EQ, noting that high intellectual capability often fails without the ability to manage emotions. Successful leadership requires understanding human dynamics, which data analysis simply can't replicate. It's about relationship management, not just requirement gathering. San Rita shares their design philosophy in "No Two Paths Alike: Inside San Rita’s Approach to Digital Experiences", published on Codrops, rejecting standard templates in favor of bespoke discovery. They treat every brief as a unique path, advocating for adaptive strategies that evolve during the project. This challenges the industry's push for standardized systems by highlighting the value of non-linear processes. Flexibility matters more than consistency when uncovering specific user needs. Other articles today from UX Design.cc on file archiving, the habit of logging off, and why flaws can be features.

There's a quiet tension running through the community today. We're seeing a shift away from speed as the primary metric. The focus is turning toward depth. Designers are asking what matters when the mechanical work disappears. Over on r/UXDesign, someone asked a deceptively simple question. Is skincare marketing actually a better teacher than design school? The post suggests these brands visualize complex data with surprising clarity. It challenges us to look outside our industry. We often ignore how other fields handle information architecture. This matters because clarity is universal. It isn't bound by tools or trends. If a lotion bottle can explain ingredients simply, we can explain user flows. In r/UserExperience, a student asked if an undergrad psychology paper helps land a research role. They want the iterative nature of design, not rigid academia. This highlights a real friction point. Credentials signal rigor, but practice signals empathy. The industry needs both. Yet we often treat them as separate tracks. The question reveals our anxiety about legitimacy. Are we researchers or designers? The answer is usually both. Depth of understanding trumps the format of the degree. Back on r/UXDesign, the community is questioning our output. Are we designing products or just designing screenshots? The concern is valid. Perfect visuals often ignore error states. They ignore accessibility and technical limits. This is the trap of speed. We optimize for the portfolio, not the user. The real value lies in the messy middle. That's where context lives. Screenshots are static. Products are dynamic. We must design for the latter. Another thread in r/UXDesign seeks a Figma alternative without AI. The request is specific. They want open source software that excludes generative features. This is a reaction to the noise. Some designers feel overwhelmed by prompt-based suggestions. They miss the tactile control of the tool. It shows a desire for intentionality. When tools decide for us, we lose agency. The pushback isn't anti- technology. It's pro-craft. We need tools that serve the vision, not dictate it. Finally, a new graduate in r/UXDesign asked how to launch a project. They have the design skills but lack the coding knowledge. This is a common gap. School teaches the prototype, not the product. The question exposes our siloed training. We design in vacuums. But real products require maintenance. Understanding deployment changes how we design. It grounds us in reality. The path forward is collaboration. Or it's learning the basics. Either way, we must bridge the gap. The thread today suggests a maturation of the field. We're moving past the hype. We're returning to the human context. That's where the real work begins.

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.

The shift from pixel perfection to strategic judgment feels like the most significant structural change in our field right now. It's less about judgment and more about survival. If AI handles the layout, we have to handle the ethics. That's a heavier burden than moving pixels. Exactly. Roman Pichler calls it emotional intelligence. It's the one thing data analysis can't replicate. You can't algorithm your way through human dynamics. But I worry we're romanticizing that. New grads are asking how to launch projects without coding knowledge. They're learning design in a vacuum. That gap is real. But it's not a coding gap. It's a context gap. They need to understand why a decision matters, not just how to build it. So we stop teaching tools and start teaching consequences. The skill isn't making the screen look good. It's knowing why that screen shouldn't exist. We're moving from execution to interpretation. And interpretation requires a voice that machines simply don't have. That's The Feed and The Thread for today. We'll catch you next time!