
Taming AI Design Slop: A Practical Playbook for UX Teams Under Pressure
A UX designer lays out how PMs and developers vibe coding can erode quality, and what designers can do to regain control.
How Do UX Teams Survive AI Design Slop?
Veteran UX designer Nick Babich's counterpart here, the author of this uxdesign.cc essay, argues that AI-generated interfaces are now arriving from product managers and developers who never open Figma. The piece walks through three scenarios: a PM turning backlog ideas into working prototypes, a developer shipping AI-assisted front ends that look plausible but fail on focus states, and a designer who must fight back by vibe coding their own, better-structured output. Its practical fixes are concrete: define a skeleton UI, set a minimum quality bar that includes WCAG rules, and run rapid QA checks.
For brand builders and design leads, this is a useful reality check on how quickly unreviewed AI output can reach leadership and production. The advice on shared guardrails, componentised design systems and accessibility standards applies whether you run a small product team or a large brand site. Designers, design managers and product leaders who are negotiating new AI workflows should read it. It is candid, a little humorous, and more useful for process than for tool recommendations.
Source: uxdesign.cc · Originally published




