Design Systems

Design Systems

Design Systems

Design Systems

Design Systems

Design systems work across fintech, web3, gaming, and enterprise platforms. Each project is different: different team size, different maturity, different constraints. What stays consistent is the approach: start with what exists, understand how it fails, and build something the team will actually use.

Over the past few years, I’ve worked on design systems across fintech, web3, and platform products. Each project taught me that systems are more than shared components. They’re living frameworks that align teams, scale creativity, and keep products consistent as they grow.

Over the past few years, I’ve worked on design systems across fintech, web3, and platform products. Each project taught me that systems are more than shared components. They’re living frameworks that align teams, scale creativity, and keep products consistent as they grow.

Over the past few years, I’ve worked on design systems across fintech, web3, and platform products. Each project taught me that systems are more than shared components. They’re living frameworks that align teams, scale creativity, and keep products consistent as they grow.

Over the past few years, I’ve worked on design systems across fintech, web3, and platform products. Each project taught me that systems are more than shared components. They’re living frameworks that align teams, scale creativity, and keep products consistent as they grow.

 Gaming & Creator Tools | Web, Mobile, Desktop | 2024–2026

 Gaming & Creator Tools | Web, Mobile, Desktop | 2024–2026

Gaming & Creator Tools | Web, Mobile, Desktop | 2024–2026

Gaming & Creator Tools | Web, Mobile, Desktop | 2024–2026

Gaming & Creator Tools | Web, Mobile, Desktop | 2024–2026

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.

Fintech | Mobile & Responsive Web | 2023

Fintech | Mobile & Responsive Web | 2023

Fintech | Mobile & Responsive Web | 2023

Fintech | Mobile & Responsive Web | 2023

Fintech | Mobile & Responsive Web | 2023

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.

Fintech | Mobile & Responsive Web | 2022

Fintech | Mobile & Responsive Web | 2022

Fintech | Mobile & Responsive Web | 2022

Fintech | Mobile & Responsive Web | 2022

Fintech | Mobile & Responsive Web | 2022

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.

EigenLayer

EigenLayer

EigenLayer

EigenLayer

EigenLayer

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.

The most valuable work usually isn't the problem I was assigned. It's the one nobody had named yet. I focus not only on building components but on the strategic alignment of design, engineering, and business objectives: token architecture, governance models, and cross-functional workflows that connect design, code, and business outcomes.

Every system I build is validated through real use, not just theoretical patterns. The best systems are those people want to use because they make their work better, easier, and more effective.

The most valuable work usually isn't the problem I was assigned. It's the one nobody had named yet. I focus not only on building components but on the strategic alignment of design, engineering, and business objectives: token architecture, governance models, and cross-functional workflows that connect design, code, and business outcomes.

Every system I build is validated through real use, not just theoretical patterns. The best systems are those people want to use because they make their work better, easier, and more effective.

The most valuable work usually isn't the problem I was assigned. It's the one nobody had named yet. I focus not only on building components but on the strategic alignment of design, engineering, and business objectives: token architecture, governance models, and cross-functional workflows that connect design, code, and business outcomes.

Every system I build is validated through real use, not just theoretical patterns. The best systems are those people want to use because they make their work better, easier, and more effective.

The most valuable work usually isn't the problem I was assigned. It's the one nobody had named yet. I focus not only on building components but on the strategic alignment of design, engineering, and business objectives: token architecture, governance models, and cross-functional workflows that connect design, code, and business outcomes.

Every system I build is validated through real use, not just theoretical patterns. The best systems are those people want to use because they make their work better, easier, and more effective.

The most valuable work usually isn't the problem I was assigned. It's the one nobody had named yet. I focus not only on building components but on the strategic alignment of design, engineering, and business objectives: token architecture, governance models, and cross-functional workflows that connect design, code, and business outcomes.

Every system I build is validated through real use, not just theoretical patterns. The best systems are those people want to use because they make their work better, easier, and more effective.

Every project begins with understanding what already exists before proposing what comes next. This phase uncovers real problems, builds alignment, and earns stakeholder trust, often surfacing issues nobody had flagged yet.

Component Audit. I review Figma organisation, component usage, and assets to identify redundancies and gaps. In one engagement, this surfaced that the same interaction pattern had been independently rebuilt across separate libraries by different teams, with no shared logic between them. I consolidated both into one structure, not just merging what existed, but rebuilding it so the fragmentation couldn't reappear at the team level.

Handoff Friction. I run collaborative sessions with design, engineering, and product teams to surface workflow bottlenecks and ensure smooth implementation.

Visual Consistency. I analyse current brand identity, identify inconsistencies, and translate evolving brand goals into a clear, scalable token structure.

Every project begins with understanding what already exists before proposing what comes next. This phase uncovers real problems, builds alignment, and earns stakeholder trust, often surfacing issues nobody had flagged yet.

Component Audit. I review Figma organisation, component usage, and assets to identify redundancies and gaps. In one engagement, this surfaced that the same interaction pattern had been independently rebuilt across separate libraries by different teams, with no shared logic between them. I consolidated both into one structure, not just merging what existed, but rebuilding it so the fragmentation couldn't reappear at the team level.

Handoff Friction. I run collaborative sessions with design, engineering, and product teams to surface workflow bottlenecks and ensure smooth implementation.

Visual Consistency. I analyse current brand identity, identify inconsistencies, and translate evolving brand goals into a clear, scalable token structure.

Every project begins with understanding what already exists before proposing what comes next. This phase uncovers real problems, builds alignment, and earns stakeholder trust, often surfacing issues nobody had flagged yet.

Component Audit. I review Figma organisation, component usage, and assets to identify redundancies and gaps. In one engagement, this surfaced that the same interaction pattern had been independently rebuilt across separate libraries by different teams, with no shared logic between them. I consolidated both into one structure, not just merging what existed, but rebuilding it so the fragmentation couldn't reappear at the team level.

Handoff Friction. I run collaborative sessions with design, engineering, and product teams to surface workflow bottlenecks and ensure smooth implementation.

Visual Consistency. I analyse current brand identity, identify inconsistencies, and translate evolving brand goals into a clear, scalable token structure.

Every project begins with understanding what already exists before proposing what comes next. This phase uncovers real problems, builds alignment, and earns stakeholder trust, often surfacing issues nobody had flagged yet.

Component Audit. I review Figma organisation, component usage, and assets to identify redundancies and gaps. In one engagement, this surfaced that the same interaction pattern had been independently rebuilt across separate libraries by different teams, with no shared logic between them. I consolidated both into one structure, not just merging what existed, but rebuilding it so the fragmentation couldn't reappear at the team level.

Handoff Friction. I run collaborative sessions with design, engineering, and product teams to surface workflow bottlenecks and ensure smooth implementation.

Visual Consistency. I analyse current brand identity, identify inconsistencies, and translate evolving brand goals into a clear, scalable token structure.

Every project begins with understanding what already exists before proposing what comes next. This phase uncovers real problems, builds alignment, and earns stakeholder trust, often surfacing issues nobody had flagged yet.

Component Audit. I review Figma organisation, component usage, and assets to identify redundancies and gaps. In one engagement, this surfaced that the same interaction pattern had been independently rebuilt across separate libraries by different teams, with no shared logic between them. I consolidated both into one structure, not just merging what existed, but rebuilding it so the fragmentation couldn't reappear at the team level.

Handoff Friction. I run collaborative sessions with design, engineering, and product teams to surface workflow bottlenecks and ensure smooth implementation.

Visual Consistency. I analyse current brand identity, identify inconsistencies, and translate evolving brand goals into a clear, scalable token structure.

Architecture and Strategy

Architecture and Strategy

Architecture and Strategy

Architecture and Strategy

Architecture and Strategy

I design systems that balance technical alignment, usability, and long-term maintainability, using an atomic approach, foundational elements like buttons, icons, and typography, scaled into complex patterns like cards, modals, and navigation.

Key principle: nest deliberately, not by default. Deep nesting can introduce real instability. I've been burned by it before, so I test structures thoroughly before committing to them. When a nested architecture is validated and warranted, it can radically reduce long-term complexity; when it's not, it becomes its own maintenance burden. The judgment is knowing which case you're in before you build.

I design systems that balance technical alignment, usability, and long-term maintainability, using an atomic approach, foundational elements like buttons, icons, and typography, scaled into complex patterns like cards, modals, and navigation.

Key principle: nest deliberately, not by default. Deep nesting can introduce real instability. I've been burned by it before, so I test structures thoroughly before committing to them. When a nested architecture is validated and warranted, it can radically reduce long-term complexity; when it's not, it becomes its own maintenance burden. The judgment is knowing which case you're in before you build.

I design systems that balance technical alignment, usability, and long-term maintainability, using an atomic approach, foundational elements like buttons, icons, and typography, scaled into complex patterns like cards, modals, and navigation.

Key principle: nest deliberately, not by default. Deep nesting can introduce real instability. I've been burned by it before, so I test structures thoroughly before committing to them. When a nested architecture is validated and warranted, it can radically reduce long-term complexity; when it's not, it becomes its own maintenance burden. The judgment is knowing which case you're in before you build.

I design systems that balance technical alignment, usability, and long-term maintainability, using an atomic approach, foundational elements like buttons, icons, and typography, scaled into complex patterns like cards, modals, and navigation.

Key principle: nest deliberately, not by default. Deep nesting can introduce real instability. I've been burned by it before, so I test structures thoroughly before committing to them. When a nested architecture is validated and warranted, it can radically reduce long-term complexity; when it's not, it becomes its own maintenance burden. The judgment is knowing which case you're in before you build.

I design systems that balance technical alignment, usability, and long-term maintainability, using an atomic approach, foundational elements like buttons, icons, and typography, scaled into complex patterns like cards, modals, and navigation.

Key principle: nest deliberately, not by default. Deep nesting can introduce real instability. I've been burned by it before, so I test structures thoroughly before committing to them. When a nested architecture is validated and warranted, it can radically reduce long-term complexity; when it's not, it becomes its own maintenance burden. The judgment is knowing which case you're in before you build.

I build flexible, reusable components and test them under real product conditions, from atomic elements through to complex patterns like forms, calendars, and navigation.

Each component is designed for flexibility, so teams can adapt patterns without breaking the system. I validate by applying components to real product features, ensuring they hold up under real-world pressure before wider adoption.

I build flexible, reusable components and test them under real product conditions, from atomic elements through to complex patterns like forms, calendars, and navigation.

Each component is designed for flexibility, so teams can adapt patterns without breaking the system. I validate by applying components to real product features, ensuring they hold up under real-world pressure before wider adoption.

I build flexible, reusable components and test them under real product conditions, from atomic elements through to complex patterns like forms, calendars, and navigation.

Each component is designed for flexibility, so teams can adapt patterns without breaking the system. I validate by applying components to real product features, ensuring they hold up under real-world pressure before wider adoption.

I build flexible, reusable components and test them under real product conditions, from atomic elements through to complex patterns like forms, calendars, and navigation.

Each component is designed for flexibility, so teams can adapt patterns without breaking the system. I validate by applying components to real product features, ensuring they hold up under real-world pressure before wider adoption.

I build flexible, reusable components and test them under real product conditions, from atomic elements through to complex patterns like forms, calendars, and navigation.

Each component is designed for flexibility, so teams can adapt patterns without breaking the system. I validate by applying components to real product features, ensuring they hold up under real-world pressure before wider adoption.

Even the strongest system fails without adoption. The clearest signal of trust isn't the components themselves. It's being trusted with more than what you were assigned. In one engagement, a Principal Designer's feedback to my manager was unprompted: "She's a better visual/systems designer than just about anyone on the team."
A design engineer I worked closely with, Eric, put it this way in a LinkedIn recommendation: "You could trust that if she owned something, it was thought through."

That kind of trust isn't something you shortcut, especially working remotely, where you don't get hallway conversations to build it by accident.

Even the strongest system fails without adoption. The clearest signal of trust isn't the components themselves. It's being trusted with more than what you were assigned. In one engagement, a Principal Designer's feedback to my manager was unprompted: "She's a better visual/systems designer than just about anyone on the team."
A design engineer I worked closely with, Eric, put it this way in a LinkedIn recommendation: "You could trust that if she owned something, it was thought through."

That kind of trust isn't something you shortcut, especially working remotely, where you don't get hallway conversations to build it by accident.

Even the strongest system fails without adoption. The clearest signal of trust isn't the components themselves. It's being trusted with more than what you were assigned. In one engagement, a Principal Designer's feedback to my manager was unprompted: "She's a better visual/systems designer than just about anyone on the team."
A design engineer I worked closely with, Eric, put it this way in a LinkedIn recommendation: "You could trust that if she owned something, it was thought through."

That kind of trust isn't something you shortcut, especially working remotely, where you don't get hallway conversations to build it by accident.

Even the strongest system fails without adoption. The clearest signal of trust isn't the components themselves. It's being trusted with more than what you were assigned. In one engagement, a Principal Designer's feedback to my manager was unprompted: "She's a better visual/systems designer than just about anyone on the team."
A design engineer I worked closely with, Eric, put it this way in a LinkedIn recommendation: "You could trust that if she owned something, it was thought through."

That kind of trust isn't something you shortcut, especially working remotely, where you don't get hallway conversations to build it by accident.

Even the strongest system fails without adoption. The clearest signal of trust isn't the components themselves. It's being trusted with more than what you were assigned. In one engagement, a Principal Designer's feedback to my manager was unprompted: "She's a better visual/systems designer than just about anyone on the team."
A design engineer I worked closely with, Eric, put it this way in a LinkedIn recommendation: "You could trust that if she owned something, it was thought through."

That kind of trust isn't something you shortcut, especially working remotely, where you don't get hallway conversations to build it by accident.