AI UX/UI Designer/Researcher

AI UX/UI Designer/Researcher - - - - - - - - - - - -

Mission

Move AI uses from individual experimentation to collective practices that hold up in production.

The scope covers user research, interface design, content and the design system. The person works alongside the teams, without replacing UX Leads or imposing a single tool on everyone.

Understand and build on what already exists

Go into the hubs, observe practices and collect concrete examples. Identify what delivers real value, what remains fragile and what is duplicated.

Expected deliverables: a map of current uses, documented examples and a shortlist of topics to pool first.

Build and harden the workflow s

Work on real projects to design repeatable ways of working: inputs, steps, tools, human checks, expected outputs and limits.

A workflow must be usable by someone other than its author, at a verifiable level of quality.

Expected deliverables: tested workflows, reusable templates and explicit validation criteria.

Organise their day-to-day use

Make practices easy to find, understand and maintain. Clarify who owns them, how they evolve and when they should be retired. Align uses with the design system and with internal frameworks governing tools and data.

Expected deliverables: a maintained reference space, clear ownership and a lightweight process for flagging issues.

Work with the teams and pass it on

Support designers on their deliverables, pair with them, make trade-offs visible and help local champions become autonomous.

Training can help, but it is not the purpose of the role. Success shows in the practices that remain once the person has left the room.

Measure the real contribution

Assess the impact on working time, rework, deliverable quality and team autonomy. Tell an impressive demo apart from a lasting gain.

Expected deliverables: before/after comparisons and reasoned decisions to continue, adapt or stop a use.

What the role is not

This is not a trend-watching or evangelism role disconnected from projects, nor a job producing training courses or prompt libraries. The person is not expected to build every technical integration alone, nor to approve every team experiment.

They must be technical enough to understand, prototype and engage with IT, without losing their product design expertise.

First expected results: three-month proposal

Month one: understand the hubs' practices, identify champions and select a few use cases based on observed problems.

Month two: test two or three workflows on projects, with a baseline and quality criteria defined with the teams.

Month three: have at least one workflow adopted by another team, document the conditions for success and set up its maintenance.

he first sign of success is not the number of people trained: it is a useful practice, adopted elsewhere, with no permanent dependence on its author .