Systems
My happy place is architecting sustainable, legible design systems, co-owned by design and engineering. As products scale, I'm often humbled when user and contributor needs illuminate the difference between my assumptions and reality.
Systems
My happy place is architecting sustainable, legible design systems, co-owned by design and engineering. As products scale, I'm often humbled when user and contributor needs illuminate the difference between my assumptions and reality.
Systems
My happy place is architecting sustainable, legible design systems, co-owned by design and engineering. As products scale, I'm often humbled when user and contributor needs illuminate the difference between my assumptions and reality.
Library architecture
Figma file, token architecture, naming conventions, theming strategy
Early and ongoing partnership with engineering allowed me to create a design library architecture which mapped to mental model used to create the code architecture. Shared language and mutual understanding of constraints had us focus on a foundational token architecture, on top of which we built our components and pattern libraries. Our approach prevented bottlenecks by segmenting the library into layers, allowing feature teams to move quickly and system team members to operate more intentionally.
Library architecture
Figma file, token architecture, naming conventions, theming strategy
Early and ongoing partnership with engineering allowed me to create a design library architecture which mapped to mental model used to create the code architecture. Shared language and mutual understanding of constraints had us focus on a foundational token architecture, on top of which we built our components and pattern libraries. Our approach prevented bottlenecks by segmenting the library into layers, allowing feature teams to move quickly and system team members to operate more intentionally.
Library architecture
Figma file, token architecture, naming conventions, theming strategy
Early and ongoing partnership with engineering allowed me to create a design library architecture which mapped to mental model used to create the code architecture. Shared language and mutual understanding of constraints had us focus on a foundational token architecture, on top of which we built our components and pattern libraries. Our approach prevented bottlenecks by segmenting the library into layers, allowing feature teams to move quickly and system team members to operate more intentionally.
Team collaboration
Design operations, product governance, internal workshops
As our product scaled, regularly revisiting our collaboration methods and providing clarity on design decisions became essential. I coordinated research with our engineering team partners, ensuring an empathy-based approach. We established goals that led to ongoing improvements in communication and collaboration. As a result, the team simplified communication channels, streamlined weekly meetings, encouraged 1:1 pairing, and committed to documenting design decisions in real-time, fostering shared stewardship and maintaining contributor flow.
Team collaboration
Design operations, product governance, internal workshops
As our product scaled, regularly revisiting our collaboration methods and providing clarity on design decisions became essential. I coordinated research with our engineering team partners, ensuring an empathy-based approach. We established goals that led to ongoing improvements in communication and collaboration. As a result, the team simplified communication channels, streamlined weekly meetings, encouraged 1:1 pairing, and committed to documenting design decisions in real-time, fostering shared stewardship and maintaining contributor flow.
Team collaboration
Design operations, product governance, internal workshops
As our product scaled, regularly revisiting our collaboration methods and providing clarity on design decisions became essential. I coordinated research with our engineering team partners, ensuring an empathy-based approach. We established goals that led to ongoing improvements in communication and collaboration. As a result, the team simplified communication channels, streamlined weekly meetings, encouraged 1:1 pairing, and committed to documenting design decisions in real-time, fostering shared stewardship and maintaining contributor flow.
Clear documentation
Writing guidelines, accessibility documentation, developer collaboration
The principle by-product of all of our systems work is our documentation. The quality of that documentation is measured by its discoverability, legibility and usefulness. I led the effort to centralize all documentation within a single hub, which connects to multiple layers serving designers, engineers, and product managers. The documentation is written in plain English for legibility, details variants with states, and highlights accessibility requirements. Alongside technical component documentation, I've also detailed usability guidelines for specific use cases.
Clear documentation
Writing guidelines, accessibility documentation, developer collaboration
The principle by-product of all of our systems work is our documentation. The quality of that documentation is measured by its discoverability, legibility and usefulness. I led the effort to centralize all documentation within a single hub, which connects to multiple layers serving designers, engineers, and product managers. The documentation is written in plain English for legibility, details variants with states, and highlights accessibility requirements. Alongside technical component documentation, I've also detailed usability guidelines for specific use cases.
Clear documentation
Writing guidelines, accessibility documentation, developer collaboration
The principle by-product of all of our systems work is our documentation. The quality of that documentation is measured by its discoverability, legibility and usefulness. I led the effort to centralize all documentation within a single hub, which connects to multiple layers serving designers, engineers, and product managers. The documentation is written in plain English for legibility, details variants with states, and highlights accessibility requirements. Alongside technical component documentation, I've also detailed usability guidelines for specific use cases.