Mark Nguyen
CEOPassionate trainer focused on helping professionals realise better opportunities in work and business.
All workshops
The Claude for Design Workshop
Keep the craft. Hand over the synthesis, the specs and the documentation - and get a clickable prototype out of a sketch
Some of the companies where our students come from
What you'll gain
Research, actually synthesised
Transcripts and tickets turned into themes, with the quotes still attached so you can defend every one.
A sketch, made clickable
Photograph the whiteboard and have it running in the browser before the block ends.
Docs your engineers will read
Anatomy, states and usage, written from the component itself in the time it takes to feel guilty about it.
A critique partner that argues back
The heuristic you've broken and the contrast that fails, uncomfortable before the review instead of during it.
How it sticks
A workshop designed for lasting impact
Discover
You see the actual gap - not clever prompting, but giving Claude your context and your own material to work on.
Build
Set up around your own work, and running on it before the session is half over.
Trust
The two places Claude will mislead you, caught in seconds - so using it well and using it safely become one habit.
Compound
Three of your own jobs, packaged up to rerun next week, without starting from a blank chat.
About this session
Nobody became a designer to write component documentation
Ask most designers where the week went and you’ll get the same list back, and none of it is design. The research nobody has had a day to read properly. The spec that has to be written before engineering can start. The component documentation that’s been on the board since March. The fourth attempt at an error message.
Claude is very good at exactly that list - and most designers are using it as a slightly faster way to write a paragraph. The gap isn’t clever prompting. It’s that nobody has given it your context: your design principles, how your product speaks, the constraints you’ve already argued about and settled. Without that it’s a competent stranger with opinions. With it, it’s someone who has read every doc your team has ever written and never gets bored of the boring parts.
It’s also better at the interesting end than people expect. You’ll photograph something from a notebook and have it clickable in the browser before the block finishes, then keep changing it by saying what’s wrong - which turns out to be a much faster way to find out whether an idea works than arguing about it in a static frame.
It’s deliberately small, too. You’ll be able to say “that won’t work with our design system because-” and get a real answer, which is the whole reason to do this live instead of watching a video at 1.5×.
This is for you if…
- You design for a living - product, UX, brand, or you run the team
- You're comfortable in Figma and a shared doc
- You've got real work you'd like to get further along
- You'd rather build one thing properly than watch ten things demoed
Probably not, if…
- You want an image generator - Claude makes words and working code, not pictures
- You're looking for a comparison of AI design tools to buy
- You can't bring any of your own work on the day
- You need something engineering-focused - that's our Claude Code workshops
The workshop agenda
Every block ends with something you could hand over
You'll spend more of this afternoon typing than watching. Nothing gets demonstrated and then left behind - the prototype, the synthesis and the documentation are all built on your own work, running, and ready to use again on Monday. The running order below is UK time; the session times at the top of the page are shown in yours.
- 15:00 15 min
Welcome, and what you brought
A quick round of what everyone's working on and where the week actually goes. We use your real files for the rest of the session, so this genuinely shapes the afternoon.
- 15:15 25 min
Setting Claude up for design work
The setup nobody shows you: projects, which files are worth uploading - your design principles, your voice guide, the component library README that stops halfway - and the standing instructions that stop you re-explaining your product in every new chat.
- 15:40 30 min
Research, synthesised
Transcripts, tickets and reviews into themes you can stand behind, with the quotes kept attached. We'll also cover the two ways Claude will quietly flatten an inconvenient minority view, and how to stop it.
- 16:10 10 min
Break
Coffee, stand up, look out of a window. Back at twenty past.
- 16:20 35 min
From sketch to clickable prototype
A photo of a whiteboard in, something running in the browser out - then twenty minutes of changing it by describing what's wrong. No code from you at any point, and no waiting for a front-end developer to be free.
- 16:55 35 min
Words, specs and documentation
Microcopy in your product's voice, the handoff spec with its edge cases and acceptance criteria, and the component documentation you've been meaning to write since March.
- 17:30 20 min
Critique and accessibility
Claude playing the sceptical design director, then the accessibility audit - contrast, labels, focus order, the alt text nobody wrote. Bring a flow you've got a review booked for.
- 17:50 10 min
Packaging it up, and Monday morning
We save what you built as things you can rerun, and each pick the one job to automate first when you're back at your desk.
Details, agenda and timing subject to change.
Before you book
What happens next
-
Your ticket arrives in your inbox
It has your joining details, your receipt and a calendar invite, ready to add straight away.
-
You get a bespoke setup guide
Everything installed and ready before the day, so no session time is lost to downloads. You and your fellow students start straight on real work.
-
The workshop itself
Our instructors show you how to use Claude, drawn from their own experience in industry. Then you do the real work, and leave with workflows you can use the very next morning.
Need to move to another date, or can't make it any more? Reply to your confirmation email and we'll sort it. You can cancel up to 21 days before the workshop and we'll refund you in full.
Bringing colleagues
Booking for your team?
3+ tickets, 25% off
Book 3 seats or more for this same date and the discount is applied automatically at checkout below. No code, no separate invoice.
Want it in person, or built around your team?
Run this session privately, tailored to your stack and your own material, remote or on-site.
Explore team trainingMeet Your Instructors
Arpan Bakshi
Chief Growth Officer & Director of EducationLeads curriculum design and workshop delivery at Atlas Learn. Formerly an educator and trainer, specialising in breaking down complex technical concepts into accessible, hands-on learning paths.
Before you book
Questions people actually ask
Bring the sketch you haven't had time to build
Three hours, a small group, and your own work on the screen. Change your mind? Cancel up to 21 days before and we'll refund you in full.