Description

Today we're looking at a growing disconnect: companies want senior talent but keep automating the work where juniors learn. In The Feed, we dig into the talent pipeline collapse, the case for better postmortems, and why genuine understanding takes more humility than we like to admit. Then in The Thread, the community is fired up about execs flattening design roles with AI and what it actually means to use these tools with intention. Buckle up, there's lots to cover for a Sunday!

In This Episode

• Today's Feed tackles a harsh reality: our industry is breaking the very pipeline that creates future leaders
• Companies demand senior expertise while automating the foundational work where juniors actually learn their craft
• Postmortems are a powerful tool for learning, yet most UX teams either skip them entirely or run them so poorly they offer no value
• Genuine understanding requires time and humility, not the immediate and complete comprehension we often promise in design
• Also worth your time today: Theresa-Marie Rhyne on dancing in the clouds with Copilot and Claude, Darren Yeo exploring the wisdom curve, and Marcos Rezende on the AI adoption theatre
• The community has some strong opinions today, and honestly, it’s tough to argue with most of them

Articles Mentioned

• Today's Feed tackles a harsh reality: our industry is breaking the very pipeline that creates future leaders.
• Companies demand senior expertise while automating the foundational work where juniors actually learn their craft. That's Hoang Nguyen's argument in a piece called "Everyone wants to hire seniors, Nobody wants to make them," at UX Design.cc, and it exposes a dangerous talent collapse. If we eliminate the messy early work, we're essentially starving the next generation of leaders. Hoang argues we must shift our investment toward mentorship despite the efficiency gains from automation.
• Postmortems are a powerful tool for learning, yet most UX teams either skip them entirely or run them so poorly they offer no value. Laura Klein makes this case in her article titled "Project Postmortems for UX Teams: Learning from Success and Failure," at Nielsen Norman Group. She notes that borrowing this engineering practice requires adapting it thoughtfully to create a systematic learning loop. The goal is to examine what happened and why, then identify the specific systemic changes needed.
• Genuine understanding requires time and humility, not the immediate and complete comprehension we often promise in design. Nate Sowder explores this in a piece called "Dear diary, you're the last good listener," at UX Design.cc, contrasting modern empathy with Adam Smith's perspective. He suggests we need disciplined approximation over concrete understanding, emphasizing the importance of recognizing our limits. This challenges the assumption that we can instantly know what another person feels.
• Also worth your time today: Theresa-Marie Rhyne on dancing in the clouds with Copilot and Claude, Darren Yeo exploring the wisdom curve, and Marcos Rezende on the AI adoption theatre. Lots to dig into over the weekend.

Community Discussions

• The community has some strong opinions today, and honestly, it’s tough to argue with most of them.
• Over in r/UXDesign, a thread called "Execs say everyone is a designer, everyone is an engineer now. I am spent," is drawing a crowd. The frustration is real: leadership is using AI as an excuse to flatten roles, and designers are watching engineers ship native apps without them. The results? Inconsistent spacing, WCAG failures, what one commenter called amateur hour UI. The community is clear on this one: prototyping with AI is not the same as designing with intent.
• Also on r/UXDesign, someone posted "Using AI as a red-team tool instead of an assistant," and the framing is sharp. Instead of asking AI to generate designs, this practitioner uses it to break their own work, the logic being if AI cannot poke holes in your reasoning, you have not stress-tested it enough. It is a genuine flip in how designers are thinking about these tools.
• Over on r/UXResearch, the thread "How many studies do you do every year?" turned into a reality check. The answers vary wildly, but the real insight is that organizational maturity drives output more than individual effort. Mature teams focus on strategic impact; newer ones just tick boxes. If you are feeling pressured by arbitrary study counts, you are not alone.
• The common thread today: stop flattening what we do. Whether it is execs, AI hype, or metrics, practitioners are pushing back on oversimplification.

Announcement

Chicago Camps is hosting UX Camp Summer on Saturday, May 30th. There's an open call for speakers so submit your idea today! 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 thirteen dollars and fifty cents.

Get tickets now at Chicago Camps dot org.