Guest lectures, workshops, and mentoring on design systems and tool-agnostic workflows.
Software changes faster than anyone can teach it. What lasts is the thinking underneath: how to structure a workflow, how to build a system that survives contact with a real team, and how to keep it alive once it ships.
Teaching happens alongside client work, on request, rather than as a separate business line.
Building flexible systems so designers aren’t handcuffed to a single software platform. Instead of training students to be Figma experts or Adobe experts, this is about teaching the underlying thinking: how to structure a workflow, use design tokens, and set up systems that move with them as the industry shifts. It also opens the door to talking about code, because building tool-agnostic systems means understanding how design and development actually connect, not just handing off a file and hoping for the best.
Teaching students to build design systems that aren’t static, one-and-done deliverables, but living systems that grow and adapt as new tech emerges. Instead of treating a design system as something you finish and file away, this session shows how to use it actively: running real-time experiments to test what works, and just as importantly what doesn’t, so the system keeps evolving alongside the tools and the industry.
More topics in progress.
It made structure the whole job.
Anyone can produce an interface now. What separates work that lasts from work that gets rebuilt in two years is whether there was a system underneath it: tokens that mean something, naming that survives a handoff, and documentation that a tool can actually read.
That is the part worth teaching, and it is the part most curricula skip in favour of the software of the moment.
01
Single sessions for a class or team, built around one idea rather than a tour of a tool.
02
Hands-on and longer form, where the group builds something real and leaves with it.
03
Ongoing and one to one, usually for designers moving toward systems or development work.