do you still need a ui/ux designer if ai can build the screens?
for something new, yes. for a feature you can build with components you already have, mostly no. if the design system is good, anyone can build the feature and what comes out is good. the designer's real job moves to the system.
the roles are collapsing
some roles are expanding and some others are being crushed. so the question is, why can't a product manager just get it done on their own? they don't need to go through figma anymore.
the feeling i get is that ui/ux on its own is useless. you need a system. once you build on top of a top notch system, things kind of fall in place on their own.
when you need a designer
when you start from scratch. no design system, no clear identity. you need someone with judgment, on the graphic side and on ui/ux, to build it for you.
and when you build something completely new. new components, new ways of showing the data. then yes, you need a new piece of the design system.
when you don't
you implement a new feature with three components you already have, they work really well together. why do i need you? maybe just to confirm, hey, do you like it? the review can be done by the product manager.
one of our designers put it well. we're all builders now and we're all reviewers. we just review with the background we have.
the pushback i got
not everyone on the team agrees with me, which is good.
one take: in a market saturated with ai products, design is what makes you different. without it you get a twin of something that already exists. component libraries let you move faster on the small features, so designers can spend their time on the big things that start from zero.
another: the biggest value is strategy. defining the problem, what we focus on, and how it ties to the bigger context. and after execution, having the criteria to tell when a design is good or feels generic.
i agree with both. it still points to the same place.
the design system is the job
a top notch design system means engineering of the design system. the front end components need to be thought out with an engineering mindset, then the design side. engineering and design together give you the foundations. after that everyone can contribute.
and if ui generated on the fly becomes more and more common, like a ui an mcp returns for the exact query the user sent, the design system matters more. maintaining it matters more. enforcing it through the whole development process matters more.
if you maintain the design system well, your goal should be to make yourself irrelevant