LO
Product / UX designer — tasks, one by one
The unit of analysis is the task, not the job title. Each one below carries its direction, whether the judgement rests on evidence or on platform inference, the reasoning, and what it does not establish.
Every task on this page#
Producing screens and components
Automating✓ Evidence-backedTurning a decided flow into high-fidelity mockups, states, variants and hand-off specs.
Design tools now generate screens from a prompt and a design system, and code-generation tools skip the mockup entirely by producing a working interface. The pixel-production hours that filled a junior designer's week are the clearest casualty on a product team.
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 right problem
Still human-led≈ Platform inferenceWorking out what users are actually trying to do, where the current product fails them, and what is worth fixing first.
This rests on observing real people using real software and on organisational judgement about what the business can and will change. It is the input to everything downstream, and generating polished screens for the wrong problem is now cheaper and therefore more common — which raises the value of getting the problem right.
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 and usability testing
Being augmented≈ Platform inferenceWatching users struggle, running interviews, reading the analytics, and turning what you saw into a decision.
Transcription, synthesis of interview notes and analysis of session recordings are much faster with assistance, and synthetic 'users' are being marketed as a substitute. The substitute is weak where it matters: it cannot reproduce the surprise of a real person doing something no one anticipated, which is the finding research exists to produce.
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.
Getting the team to agree
Still human-led✓ Evidence-backedPersuading engineering that the extra state is worth building and product that the shortcut will cost users, in the same week.
Design decisions in software are negotiated, not decreed. The designer's leverage comes from evidence and from credibility built over previous decisions, both of which are personal. Tools produce more options to argue about; they do not settle the argument.
Alignment work grows with team size and disappears with the team. It protects the designer who is already trusted, not the role's headcount.
Designing for non-deterministic products
New task≈ Platform inferenceShaping products whose output varies — conversational interfaces, agents, generated content — where the old screen-by-screen craft does not apply.
A large share of new software has a model in the loop, and designing how it fails, how it explains itself and how the user stays in control is an unsolved craft. Teams are hiring designers specifically for it, and the skill is scarce because almost no one has done it for long.
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.