AI in the design process.
A one-day in-house programme for design teams already using AI, on where judgement still lives, how critique changes, and what your team agrees to.
For teams where the tools arrived before the rules.
This assumes your team is already using AI daily. The question is no longer whether, it is what you let it decide.
The tools arrived before the rules
Your team already uses them. Nobody agreed how.
More output, same decisions
Volume went up. The quality of the calls did not.
Juniors who skip the first draft
The path that built craft ran straight through it.
Stakeholders who now arrive with a design
Anyone can produce something plausible. Someone has to judge it.
Six questions your team is already arguing about.
Run against your own work and your own tools, not a demo.
What actually changed, and what only looks like it did
Separate the parts of the job the tools genuinely do from the parts where they produce something plausible and wrong.
→ an honest capability line for your own stackGenerating options versus making the call
Ten directions in an afternoon is not ten times the thinking. Where the judgement still has to live.
→ a decision record for one real choiceCritique when the work is cheap to produce
Review was built for work that cost something. Rebuild it for work that does not.
→ a critique protocol your team agrees toResearch and synthesis without fooling yourself
Where a model helps with research data, and how it manufactures agreement that was never in the transcripts.
→ rules for what a model may touchHow juniors build craft when the first draft is free
The traditional path ran through doing the boring part. Decide what replaces it before your juniors do.
→ a development plan for one juniorA position your team can hold
What you use, what you will not, and what you tell a client or a regulator when they ask.
→ a one-page team position on AIA position, not a pile of opinions.
A team position on AI
One page: what you use, what you do not, what you disclose.
A critique protocol
For reviewing work that took minutes to make.
A delegate-or-not list
The tasks worth handing over, and the ones that are the job.
Language for the conversation
So the team argues about the work, not about the tools.
A decade of teaching teams on their own work.
We have run in-house UX training for product, design and technology teams at the BBC, Google, GroupM, Wataniya Insurance, Deloitte and Lidl, and our own courses have been AI-first since 2026. Every day runs against your product, your tools and your constraints, not a case study.
If the question in front of you is the other one, where an agent belongs in your customers' journey and when it hands back to a person, see our agentic AI programme.
Before you enquire.
Is this a tools course?
No. It is not a tutorial in any particular product, and it does not go out of date when one of them ships a new feature. It is about the decisions around the tools: what you let them do, how you review what comes back, and how a team agrees a position it can defend. Bring whichever tools you already use and we work against those.
Who have you taught this way before?
We have delivered in-house UX training to product, design and technology teams for over a decade, including the BBC, Google, GroupM, Wataniya Insurance, Deloitte and Lidl, and our own courses have been AI-first since 2026. This curriculum applies that to the question every design team is working out at the same time. Ask us to walk your team through it before you commit.
How is this different from the agentic AI day?
Will this tell my team to use AI more, or less?
Neither. We have no position to sell you on that, and a day that arrived with the answer already decided would be worth nothing. The output is your team's position, argued out against your own work, which in places will be that a tool is not worth using.
Can this be combined with other in-house training?
Yes. It is often scoped alongside the UX research day, since research synthesis is where teams most often let a model do more than it should. Tell us on the form below and we will scope the days together.
Enquire about this programme.
Tell us about your team, the tools they already use, and your preferred timing. We'll get back to you within 2 business days.
*Advertised price assumes 10 or more participants. Prices vary depending on the number of participants.