If you work as a UX designer, product designer or design researcher, AI is no longer a topic "for the data team". It is already in your Figma, your copy workflow, the analytics dashboard you check every day. The question is not whether you will encounter it, but whether you can recognise where it influences the decisions you make.
In the creative process, generative AI is used for wireframes, moodboards, layout variants, microcopy and naming. Tools like Figma AI, Galileo, Uizard or Midjourney plugins speed up exploration. But speed does not mean neutrality: every output carries aesthetic bias, visual homogenisation and copyright questions about training data.
In research, automatic interview synthesis, sentiment analysis, feedback clustering and LLM-generated "synthetic users" appear. They can help explore hypotheses, but do not replace the voices of real people — and presenting them as authentic research is ethically problematic.
In production, the designer creates interfaces for recommendations, chatbots, virtual assistants, personalised onboarding and "smart" filters. Here AI is not a designer tool: it is the product itself. Every UI choice — what to show, what to hide, how to explain a result — shapes the relationship between user and algorithm.
There is also the organisational dimension: management pressure to add "AI features", "Powered by AI" badges for fundraising or marketing, sprints to integrate models without time to assess risks. The designer is often the first to see how these decisions translate into concrete experiences — and therefore has a say.
Mapping where AI enters your work is the first step to acting responsibly. You do not need to become a data scientist: you need to know which decisions are yours, which belong to the product team, and which require involvement from legal, policy or affected communities.