I build systems that work in the real world, component libraries teams actually want to use, governance frameworks that scale, and documentation that bridges design and engineering. Five years at Forge Studio across fintech, web3, and enterprise platforms, including 14 months embedded in Roblox's core design systems team.
I build systems that work in the real world, component libraries teams actually want to use, governance frameworks that scale, and documentation that bridges design and engineering. Five years at Forge Studio across fintech, web3, and enterprise platforms, including 14 months embedded in Roblox's core design systems team.
I build systems that work in the real world, component libraries teams actually want to use, governance frameworks that scale, and documentation that bridges design and engineering. Five years at Forge Studio across fintech, web3, and enterprise platforms, including 14 months embedded in Roblox's core design systems team.
I build systems that work in the real world, component libraries teams actually want to use, governance frameworks that scale, and documentation that bridges design and engineering. Five years at Forge Studio across fintech, web3, and enterprise platforms, including 14 months embedded in Roblox's core design systems team.
I build systems that work in the real world, component libraries teams actually want to use, governance frameworks that scale, and documentation that bridges design and engineering. Five years at Forge Studio across fintech, web3, and enterprise platforms, including 14 months embedded in Roblox's core design systems team.

Scaling a design system from early-stage development to production-ready infrastructure, 61 product teams, four platforms, millions of users. Consolidated legacy libraries, built governance frameworks, and reduced component variant complexity by 78% on high-usage patterns, all while the product kept shipping.
Full case study restricted under client agreement.
Scaling a design system from early-stage development to production-ready infrastructure, 61 product teams, four platforms, millions of users. Consolidated legacy libraries, built governance frameworks, and reduced component variant complexity by 78% on high-usage patterns, all while the product kept shipping.
Full case study restricted under client agreement.
Scaling a design system from early-stage development to production-ready infrastructure, 61 product teams, four platforms, millions of users. Consolidated legacy libraries, built governance frameworks, and reduced component variant complexity by 78% on high-usage patterns, all while the product kept shipping.
Full case study restricted under client agreement.
Scaling a design system from early-stage development to production-ready infrastructure, 61 product teams, four platforms, millions of users. Consolidated legacy libraries, built governance frameworks, and reduced component variant complexity by 78% on high-usage patterns, all while the product kept shipping.
Full case study restricted under client agreement.
Scaling a design system from early-stage development to production-ready infrastructure, 61 product teams, four platforms, millions of users. Consolidated legacy libraries, built governance frameworks, and reduced component variant complexity by 78% on high-usage patterns, all while the product kept shipping.
Full case study restricted under client agreement.
A B2B SaaS property management platform, rebuilt end-to-end brand, design system, and platform-wide UX across 8 product sections. Built and validated pattern libraries from foundational components through complete workflows, resolving Figma variable architecture issues along the way.
Full case study restricted under client agreement.
A B2B SaaS property management platform, rebuilt end-to-end brand, design system, and platform-wide UX across 8 product sections. Built and validated pattern libraries from foundational components through complete workflows, resolving Figma variable architecture issues along the way.
Full case study restricted under client agreement.
A B2B SaaS property management platform, rebuilt end-to-end brand, design system, and platform-wide UX across 8 product sections. Built and validated pattern libraries from foundational components through complete workflows, resolving Figma variable architecture issues along the way.
Full case study restricted under client agreement.
A B2B SaaS property management platform, rebuilt end-to-end brand, design system, and platform-wide UX across 8 product sections. Built and validated pattern libraries from foundational components through complete workflows, resolving Figma variable architecture issues along the way.
Full case study restricted under client agreement.
A B2B SaaS property management platform, rebuilt end-to-end brand, design system, and platform-wide UX across 8 product sections. Built and validated pattern libraries from foundational components through complete workflows, resolving Figma variable architecture issues along the way.
Full case study restricted under client agreement.


Rapid growth and a major rebrand at the same time, the system had to keep up with both. Built the pattern library that unified mobile and web under a new identity while the product was still shipping.
Rapid growth and a major rebrand at the same time, the system had to keep up with both. Built the pattern library that unified mobile and web under a new identity while the product was still shipping.
Rapid growth and a major rebrand at the same time, the system had to keep up with both. Built the pattern library that unified mobile and web under a new identity while the product was still shipping.
Rapid growth and a major rebrand at the same time, the system had to keep up with both. Built the pattern library that unified mobile and web under a new identity while the product was still shipping.
Rapid growth and a major rebrand at the same time, the system had to keep up with both. Built the pattern library that unified mobile and web under a new identity while the product was still shipping.
Taking a design system global means more than translating copy. Expanding into the UK and Canada required design patterns that could handle localisation, regulatory constraints, and language support without fragmenting the product.
Taking a design system global means more than translating copy. Expanding into the UK and Canada required design patterns that could handle localisation, regulatory constraints, and language support without fragmenting the product.
Taking a design system global means more than translating copy. Expanding into the UK and Canada required design patterns that could handle localisation, regulatory constraints, and language support without fragmenting the product.
Taking a design system global means more than translating copy. Expanding into the UK and Canada required design patterns that could handle localisation, regulatory constraints, and language support without fragmenting the product.
Taking a design system global means more than translating copy. Expanding into the UK and Canada required design patterns that could handle localisation, regulatory constraints, and language support without fragmenting the product.


A bold visual identity is easy to build in isolation. Making it functional, accessible, and consistent across light and dark contexts at product scale is a different problem entirely.
A bold visual identity is easy to build in isolation. Making it functional, accessible, and consistent across light and dark contexts at product scale is a different problem entirely.
A bold visual identity is easy to build in isolation. Making it functional, accessible, and consistent across light and dark contexts at product scale is a different problem entirely.
A bold visual identity is easy to build in isolation. Making it functional, accessible, and consistent across light and dark contexts at product scale is a different problem entirely.
A bold visual identity is easy to build in isolation. Making it functional, accessible, and consistent across light and dark contexts at product scale is a different problem entirely.
Writing about design systems as they actually work.
Published every other week.
Writing about design systems as they actually work.
Published every other week.
Writing about design systems as they actually work.
Published every other week.
Writing about design systems as they actually work.
Published every other week.
Writing about design systems as they actually work. Published every other week.

It starts as small favours. By the time you recount, the split was never 50/50. The cost doesn't show up in any retrospective.

The best career conversations happen when you're not trying to get anything out of them.

If AI handles the execution layer before the next generation gets to touch it, what exactly is the thinking layer built on?