LO
Get told when a verified record lands on this occupation → · Mark which of these tasks are yours (VOLO Pro, free) → · For a team or a graduating class →
Product / UX designer
Decides how a piece of software behaves for the person using it — screen by screen, state by state — and proves the decision with evidence.
Take your best recent piece of work and rewrite the case study to lead with the problem and the evidence, with the screens last. If there is nothing to write before the screens, that is the gap.
This is not a probability of losing your job. It combines how much of the role's task load is exposed to automation with how far adoption has actually gone — useful for comparing occupations on one consistent basis, and for nothing else.
Written for product, UX and UI designers on software teams. Design research as a separate role, brand and marketing design, and game design differ.
What is actually changing#
The unit of analysis is the task, not the job title. A role is not replaced — its task mix shifts.
Each tile is one task. Its size is how much of the job it is; its colour is where the task is heading. Click a tile to see what the judgement does not establish.
Pixel production was the paid apprenticeship. Removing it does not just remove junior jobs; it removes how anyone becomes the senior designer the same team still needs.
Defining the problem is usually shared with product management, and on small teams it is not the designer who wins that argument. Being valuable is not the same as being the one who decides.
Research is the first budget cut in most downturns, regardless of whether synthetic users are any good. Its exposure is commercial before it is technical.
Alignment work grows with team size and disappears with the team. It protects the designer who is already trusted, not the role's headcount.
Scarcity here is temporary by construction — almost no one has done it for long because it is new, and that gap closes as everyone gets the same few years of practice.
Is this your job? Say so and this page narrows to your share of it.
A job title is a bundle of tasks bought together, and no two people hold the same bundle. Nothing is sent anywhere — it stays in this browser.
Read all 5 tasks in full — direction, reasoning and limits →
Recent changes#
One vendor's quarter, reported by the vendor. Paid customers are not designers: a count of separately billed customer accounts rising 54% while AI tools spread is at least as consistent with design work moving to people who were never design hires as it is with more designers being employed. Figma also put AI credit limits on all seats from 18 March 2026 and sells AI credit add-ons, so part of the revenue figure may reflect AI monetisation rather than more users.
Failure, rollback, regulation or cost is suppressing adoption. Can lower an assessment or widen its uncertainty.
The UK government's digital service describing its own product. Over 18 months it ran two public pilots of GOV.UK Chat in which more than 10,000 users asked 26,000 questions; it introduced clarifying questions where users' questions were ambiguous, raising the answer rate for in-scope questions to 88%; answer streaming tested well with users but requires redesigning some safety guardrails; and the research used methods including 99 remote usability tests and a diary study with 30 hours of video interviews. It is a pilot reported by the team that built it; the assistant runs on a model from Anthropic, the maker of the model that wrote this record.
Small-scale trial in a real setting. Tells us the deployment conditions are being tested, not that they hold — so one pilot is never enough on its own; two independent ones are.
The filing establishes metering, not its effect. Figma states that it introduced AI credits across all Figma seats in 2025 and began enforcing the limits in March 2026, with monthly add-ons or pay-as-you-go usage beyond them; it names the month, not a day. It describes Figma Make as going from a prompt to a working prototype, lists it among the features subject to AI credit pricing, and warns that customers may curtail their use of those features. It reports no usage figure and no measurement of whether any team generated less once the limits bit. Figma sells these seats and has an interest in how a pricing change is presented, but the fact recorded here is stated in a filing where overstating carries liability. It says nothing about other vendors' tools.
Failure, rollback, regulation or cost is suppressing adoption. Can lower an assessment or widen its uncertainty.
The Government of Canada's design system guidance for AI help applications on its main website. It says AI help applications must be clearly labelled as AI; all in-scope answers must include at least one authoritative citation link, pointing to a Government of Canada page wherever possible; teams must not give the application a human name or call it a chat or chatbot; warning users that AI makes mistakes is not a replacement for measuring accuracy; and UX researchers should be involved early to test design prototypes with potential end users, followed by iterative usability testing. It binds one government's website, and the testing guidance is 'should'.
Failure, rollback, regulation or cost is suppressing adoption. Can lower an assessment or widen its uncertainty.
A peer-reviewed study of language models used as replacements for human participants in computational social science, user testing and annotation. Through human studies with 3,200 participants across 16 demographic identities and four models, the authors show the models misportray and flatten demographic groups, and that their own inference-time techniques reduce but do not remove these harms. It is not specific to UX work and tests models current at the time; the authors declare no competing interests.
Failure, rollback, regulation or cost is suppressing adoption. Can lower an assessment or widen its uncertainty.
Guidance for UK government departments on using AI. It says identifying use cases for AI must be led by business and user needs, pain points and inefficiencies, not what the technology can do, with challenges and opportunities identified through user research; and, under its second principle, that when defining and deploying AI systems teams must understand people's needs and priorities by conducting user research and engaging with the public as appropriate. It binds UK government teams and is guidance rather than statute.
Failure, rollback, regulation or cost is suppressing adoption. Can lower an assessment or widen its uncertainty.
One design-tool vendor's generative feature (GPT-4o and Amazon Titan on hand-built component design systems), limited beta. A vendor rollback, not a customer deployment; the feature returned within three months as First Draft.
Failure, rollback, regulation or cost is suppressing adoption. Can lower an assessment or widen its uncertainty.
What this means for you#
A portfolio of polished screens is worth much less than it was, because polished screens are now cheap. What gets you hired is evidence of decisions: a problem you defined, the research you did, what you chose and why, and what happened. Build that with one real product — a side project with real users counts — and learn the non-deterministic interface problems early, because the field is short of people who have.
If your value was production quality and speed, expect that to be compressed; if it was problem definition, research and alignment, it is holding and the generative-product problems are new demand in your favour. The uncomfortable shift is that fewer production designers means each senior designer covers more ground with tools, so fluency with them becomes a baseline rather than a differentiator.
Your options#
Four directions, each with its real constraints and one thing you can test this week. Continuing as you are is a legitimate choice — it just has to be a chosen one.
Lead with research and decisions, not screens
The scarce work is knowing what to build. Designers who can show the evidence trail behind a decision are the ones teams keep when production gets cheap.
Requires access to users and to the roadmap conversation, which junior roles often lack.
Take your best recent piece of work and rewrite the case study to lead with the problem and the evidence, with the screens last. If there is nothing to write before the screens, that is the gap.
Specialise in model-in-the-loop products
Its design problems are still open: GOV.UK's own pilot found streaming answers meant redesigning safety guardrails. Scarcity favours anyone who has shipped one.
You need a team building such a product, and tolerance for designing things whose behaviour you cannot fully specify.
Pick one conversational or agentic product you use and document three ways it fails the user and what you would change. That document is a portfolio piece nobody else has.
Product management
Designers who already own problem definition and alignment are doing much of the product manager's job. The move formalises it and usually pays better.
You inherit prioritisation, metrics and stakeholder management, and you lose most of the craft.
Sit in on one roadmap prioritisation meeting. If you found yourself with opinions on the trade-offs rather than the interface, take the path seriously.
Common questions#
You need to be fluent enough to direct and correct what the tools produce, which is less than a production specialist needed and more than nothing. The skill that has appreciated is everything upstream of the tool: knowing what problem to solve, what evidence supports a choice, and how to get a team to build it. Learn the tools quickly, then spend your effort on the judgement — that order is the reverse of how design education usually runs.
Watch who produces the screens on your team. When engineers generate a working interface from a prompt and a design system, the mockup step disappears entirely — and that is a workflow change inside your own team, visible before it appears in any hiring plan.
Producing screens and components — the task marked automating, and the hours that filled a junior designer's week. Problem definition and research are not, but problem definition is usually shared with product management, and on small teams the designer is not the one who wins that argument.
You need them to be credible in the argument, not to produce the artefact. The leverage in this role comes from evidence and from credibility built over previous decisions — both personal, neither generated. Learn the tool well enough to not be dismissed, and spend the rest of the time on research.
Studying towards this?
These majors lead here. Their pages break down which of their competencies transfer and what graduates typically lack.
What these judgements rest on#
5 of 5 task judgements on this page are backed by a verified event and 0 are platform inference, each labelled where it appears. Behind them sit 1 technology dimensions, a reconstructed trajectory since language models reached the public, and 7 verified events.
See which technologies, how it got here, and the method →
Where it sits in the official classification: skills, knowledge, related jobs →
Other roles in the same function#
A company divides its work into functions before it divides it into jobs. These sit in Product & design alongside this one — a fact about org charts, not a judgement that they are similar or that they are changing in the same direction.