Episode Details

So designers are paying a hidden tax just to get their work approved. And apparently the fix is... proving you belong by speaking someone else's language? Right... Yeah, and meanwhile, hiring managers say they're tired of polished portfolios that hide the mess. Well, that's gonna upset some people. Let's get into it.

The Tease

Feed: So designers are paying a hidden tax just to get their work approved. Thread: And apparently the fix is... proving you belong by speaking someone else's language? Right... Feed: Yeah, and meanwhile, hiring managers say they're tired of polished portfolios that hide the mess. Thread: Well, that's gonna upset some people. Let's get into it.

In This Episode

• Today's Feed tackles a structural imbalance in design, a new standard for research inclusion, and a hard truth about what hiring managers actually want from entry-level portfolios.
• Designers pay a hidden tax just to do their jobs
• True inclusion means moving past simple checklists
• Polished case studies are hiding a problem
• Also publishing recently: George Joeckel at WebAIM on a new path for digital accessibility, Kem-Laurin Lubin at UX Design.cc on designing at the edge of AI harm, and Fabricio Teixeira on agentic UX principles.
• Welcome back to the community pulse, where the real conversations are happening.

Articles Mentioned

• Today's Feed tackles a structural imbalance in design, a new standard for research inclusion, and a hard truth about what hiring managers actually want from entry-level portfolios.
• Designers pay a hidden tax just to do their jobs. Vlad Derdeicea calls it the "justification tax" in a piece unsurprisingly called "The justification tax," at UX Design.cc. While engineers refactor code on merit, designers must constantly prove their work with data and business cases. This extra burden delays approvals and fuels burnout because design is the only discipline forced to translate its value into finance and engineering languages.
• True inclusion means moving past simple checklists. Dr. Michele Williams argues this in a new book titled "Accessible UX Research," announced by Smashing Magazine. The guide challenges professionals to recruit disabled participants from the start rather than just checking compliance boxes. It offers practical strategies to confront ableism and avoid biased questioning during sessions.
• Polished case studies are hiding a problem. In "Entry-Level UX Portfolios Demand Judgment Over Wireframes," at Mitoware, the argument is clear: hiring managers are tired of seeing perfect deliverables that mask the messy reality of product work. What actually stands out is showing the decision path, the constraints you navigated, and the tradeoffs between viable alternatives. If your portfolio can't survive a whiteboard test, the tools aren't saving you.
• Also publishing recently: George Joeckel at WebAIM on a new path for digital accessibility, Kem-Laurin Lubin at UX Design.cc on designing at the edge of AI harm, and Fabricio Teixeira on agentic UX principles.

Community Discussions

• The real question isn't whether AI is fast, but whether speed kills the definition of good work. "Stop Letting Execs Turn UX Into AI Builders," over on r/UXDesign, is urging designers to speak up now or risk irrelevance. One commenter argues that code is moving faster than our ability to shape problems, calling this gap a goldmine if we know how to use it. But another voice pushes back hard, noting that UX only survives by delivering business results, not by defending an ideology. If AI outputs perform as well as a design team, companies will simply cut the cost. The divide is clear: are we the strategists who define the problem, or just the operators building the solution?
• Meanwhile, the hierarchy of product teams is getting messy again. "Anyone else seeing designers