AI Design Transformation.
From “we tried AI” to an AI-native design team in 90 days. One day of bootcamp plus 12 weeks of anchoring so your designers operate a design + code + AI workflow daily, not just attend a training and forget by Monday.
Move your design team from “we tried AI” to an AI-native workflow.
A YouTube playlist or a 500 CHF Maven course produces 20 to 30% real adoption. By Monday, the team is back in Figma. What lifts adoption past 70% is anchoring inside your real projects for three months. That’s what this program does.
- 01
Each designer ships a working code + AI prototype in your industry on day one. The first win lands before they go back to their desk.
- 02
A weekly cadence that survives Monday morning: 2 group sessions a month, 1:1s every quarter, and a Slack channel that answers under 24h.
- 03
Features validated in front of users before the engineering build, not after. The cost of a wrong feature stops being a quarter of work.
- 04
An adoption report at 90 days you can hand to your CPO and L&D — prototypes per month, time-to-validation, team satisfaction.
What your team will operate.
A 3-month transformation that takes your design team from “we tried AI” to a code + AI workflow operated daily on real projects. The program covers code-first prototyping, design systems inside the IDE, and validation before the engineering build. Goal: an AI-native team you can stand behind in front of your CPO, board, and L&D.
01
Code-first prototyping with AI
Set up VS Code, Claude Code, and the prompt patterns that actually ship
Prototype a landing or feature in hours instead of weeks
Switch fluently between code and Figma without losing the design intent
02
Design systems inside the IDE
Anchor your tokens and components so AI output stays on-brand
Reuse the team's prompt library across projects
Hand work to engineering with patterns they can actually pick up
03
Validation before the build
Frame the feature as a testable prototype before any sprint commitment
Run a stakeholder review on a working artefact, not a static frame
Close the loop with research signal that earns the engineering budget
Program agenda.
One day of bootcamp plus 12 weeks of weekly anchoring. Every phase builds on the last.
D-14 to D-1
Pre-bootcamp
Prep videos (IDE setup, Claude Code basics, first prompts). A level questionnaire pre-qualifies each designer. The practice case is shared in advance so day one starts at full speed.
Day 0 — Morning
Pedagogy (3h)
AI use cases in the design workflow. Going from approximate output to structured output. Prototyping in code. Switching between code and Figma. The foundations of a design system inside the IDE.
Day 0 — Afternoon
Practice case (3h)
A case in your industry (banking, insurance, retail, telco, public services). Around 2h of guided autonomous work, then a collective debrief. Every designer leaves with a functional prototype.
D+14
Group follow-up (1h)
A live session to unblock the friction that always shows up the first week back. The exact moment most trainings lose their team.
Months 1–3
Anchoring
2 group sessions per month (1h30, remote). 1 quarterly 1:1 per designer (45 min). A private Slack channel with a 24h response time. A mid-program audit on 2–3 real projects.
Run by
Lucas Rappart
Senior Product Designer · Independent since 2022
Senior Product Designer shipping for enterprise teams: Hafnova (security app rebuild), Le Temps (vision sprint plus Chronos AI assistant), Dentsply Sirona (NASDAQ: XRAY, embedded product squad), Foodhack, Romande Energie. I prototype in code with AI every day for live client work.
On the coaching side, 500+ designers accompanied 1:1 over the last few years. This program is the bridge between those two practices: hands-on senior delivery, packaged so a design team can adopt the workflow without a hire.
Email me a questionWho this program is for.
You lead a design team of 4 to 15 designers inside a mid-to-large enterprise.
Your CPO or board is asking for an AI strategy in design and you only have a deck.
Your designers have tried Claude Code once and went straight back to Figma.
You have a real L&D and product budget — the cost of a wrong feature is six figures.
What’s included.
Inside the program
Packaged pre-training
4 to 5 prep videos plus the level questionnaire and technical setup check. Heterogeneous skill levels arrive on day one ready to work.
One-day bootcamp (remote, 6 designers max)
Morning pedagogy then an afternoon practice case in your industry. Live coaching throughout, small enough for individual attention.
3 months of weekly anchoring
2 group sessions a month, 1:1 quarterly per designer, private Slack/Discord channel for 3 months. The piece that turns ~25% adoption into ~75%.
Mid-program audit (month 2)
A live review of 2 to 3 real projects from your team. Course-corrects before the program ends.
Project template + prompt library
A working design system, file structure, and the prompts that actually ship. Stays with the team after the 3 months.
Board-ready adoption report at day 90
Prototypes per month, time-to-validation, team satisfaction. Packaged with a slide narrative your CPO can present to the board.
Two commitments
Tangible Bootcamp Guarantee
By end of day zero, every designer has produced a functional code + AI prototype in your industry. If not, I rerun the day with your team at no charge — or the bootcamp isn't billed.
90-Day Adoption Guarantee
If at the month-2 audit fewer than 4 out of 6 designers are prototyping in code + AI at least weekly on real projects, I extend the anchoring by 30 days at no cost.
Frequently asked questions.
Why a bundle instead of just a one-day training?
Standalone training reliably produces 20 to 30% real adoption. By the Monday after the bootcamp, the team is back in Figma. The 3 months of weekly anchoring (group sessions, 1:1s, Slack, mid-program audit) is the piece that takes adoption to 70 to 80%. It's the program, not the day.
My designers have very different technical levels — will this work?
Yes. The pre-bootcamp phase (prep videos plus a level questionnaire 14 days out) brings everyone to the same starting line. Designers who aren't ready are rescheduled rather than dropped into a day that won't serve them.
Our data is sensitive — we can't expose our product.
The practice case is built in your industry, not on your product. No proprietary code or data leaves your environment. Data and AI policies are checked at the scoping stage, before signature.
How is this different from a Maven course or a YouTube playlist?
Two ways. First, it's hands-on synchronous with a senior practitioner, not async content. Second, it includes 90 days of anchoring inside your real projects — courses can't do that. The price reflects the transformation, not the content.
Why remote and not on-site?
Remote keeps the cohort at 6 designers max with live coaching for each. It records cleanly so absentees catch up, and it works for distributed teams. An on-site variant is available on request with a separate quote.
What happens after the 3 months?
The template, the prompt library, and the adoption report stay with your team. Most teams roll into a lighter cadence quarterly check-in, or onto a Design Partner Retainer if senior design continuity is what they need next.