OPTUM NOW
Evolving a Sub-Brand Design System (DS) and Handoff Process
When the Optum Store design team switched to working on Optum Now, I was tasked with updating the Optum Store DS and handoff process.
Project background
Optum Now: Everything healthcare all at once
Optum Now is an RVO Health brand created by integrating e-commerce and wellness brands from Optum with health and wellness brands from Red Ventures. Its goal is to be an all-in-one consumer health hub.
Optum Now went live in 07/2024 and absorbed Optum Store in 09/2024.
Optum is a subsidiary of UnitedHealth Group (UHG), serving over 120M consumers, with a 2024 revenue of $253B.
Optum Now: Everything healthcare all at once
Optum Now is an RVO Health brand created by integrating e-commerce and wellness brands from Optum with health and wellness brands from Red Ventures. Its goal is to be an all-in-one consumer health hub.
Optum Now went live in 07/2024 and absorbed Optum Store in 09/2024.
Optum is a subsidiary of UnitedHealth Group (UHG), serving over 120M consumers, with a 2024 revenue of $253B.
Optum Now: Everything healthcare all at once
Optum Now is an RVO Health brand created by integrating e-commerce and wellness brands from Optum with health and wellness brands from Red Ventures. Its goal is to be an all-in-one consumer health hub.
Optum Now went live in 07/2024 and absorbed Optum Store in 09/2024.
Optum is a subsidiary of UnitedHealth Group (UHG), serving over 120M consumers, with a 2024 revenue of $253B.
Optum Now: Everything healthcare all at once
Optum Now is an RVO Health brand created by integrating e-commerce and wellness brands from Optum with health and wellness brands from Red Ventures. Its goal is to be an all-in-one consumer health hub.
Optum Now went live in 07/2024 and absorbed Optum Store in 09/2024.
Optum is a subsidiary of UnitedHealth Group (UHG), serving over 120M consumers, with a 2024 revenue of $253B.
A separate DS for existing + expected divergence
The Optum Store creative team always had a separate DS from Optum, and was the team working on Optum Now.
There was always a vague directive to "push the brand" (which we couldn't do using a DS we couldn't change).
A separate DS for existing + expected divergence
The Optum Store creative team always had a separate DS from Optum, and was the team working on Optum Now.
There was always a vague directive to "push the brand" (which we couldn't do using a DS we couldn't change).
A separate DS for existing + expected divergence
The Optum Store creative team always had a separate DS from Optum, and was the team working on Optum Now.
There was always a vague directive to "push the brand" (which we couldn't do using a DS we couldn't change).
A separate DS for existing + expected divergence
The Optum Store creative team always had a separate DS from Optum, and was the team working on Optum Now.
There was always a vague directive to "push the brand" (which we couldn't do using a DS we couldn't change).
Requirements
Update DS for flexibility + speed
Follow current visual style of Optum Store, but build in flexibility
Enable quick and easy style changes (for expected shifts and white-label design)
Complete within 4 weeks (spoiler alert: this was unrealistic)
Update DS for flexibility + speed
Follow current visual style of Optum Store, but build in flexibility
Enable quick and easy style changes (for expected shifts and white-label design)
Complete within 4 weeks (spoiler alert: this was unrealistic)
Update DS for flexibility + speed
Follow current visual style of Optum Store, but build in flexibility
Enable quick and easy style changes (for expected shifts and white-label design)
Complete within 4 weeks (spoiler alert: this was unrealistic)
Update DS for flexibility + speed
Follow current visual style of Optum Store, but build in flexibility
Enable quick and easy style changes (for expected shifts and white-label design)
Complete within 4 weeks (spoiler alert: this was unrealistic)
Optimize handoff for expanded team
Recommend team file setup to accommodate a larger (more complex) product team
Recommend processes to improve design handoff (and reduce coded design discrepancies)
Teach designers how to integrate Figma + Jira
Optimize handoff for expanded team
Recommend team file setup to accommodate a larger (more complex) product team
Recommend processes to improve design handoff (and reduce coded design discrepancies)
Teach designers how to integrate Figma + Jira
Optimize handoff for expanded team
Recommend team file setup to accommodate a larger (more complex) product team
Recommend processes to improve design handoff (and reduce coded design discrepancies)
Teach designers how to integrate Figma + Jira
Optimize handoff for expanded team
Recommend team file setup to accommodate a larger (more complex) product team
Recommend processes to improve design handoff (and reduce coded design discrepancies)
Teach designers how to integrate Figma + Jira
Challenges I anticipated and planned for
Challenge
Designers never had time for mobile designs for Optum Store.
Figma didn't allow variable mode rearrangement.
Designers didn't know what info developers needed.
Designers would begin using the new DS 2 weeks after I started.
I had to split my time between the DS and research work.
Variables were very new (still in Beta).
Plan
Enable quicker design of secondary breakpoints
Get team consensus on primary breakpoint
Consult engineers for their side of the handoff story
Prioritize the components designers would need first
Communicate workload to adjust timeline expectations
Educate designers on variable use, benefits, and limitations
Challenge
Designers never had time for mobile designs for Optum Store.
Figma didn't allow variable mode rearrangement.
Designers didn't know what info developers needed.
Designers would begin using the new DS 2 weeks after I started.
I had to split my time between the DS and research work.
Variables were very new (still in Beta).
Plan
Enable quicker design of secondary breakpoints
Get team consensus on primary breakpoint
Consult engineers for their side of the handoff story
Prioritize the components designers would need first
Communicate workload to adjust timeline expectations
Educate designers on variable use, benefits, and limitations
Challenge
Designers never had time for mobile designs for Optum Store.
Figma didn't allow variable mode rearrangement.
Designers didn't know what info developers needed.
Designers would begin using the new DS 2 weeks after I started.
I had to split my time between the DS and research work.
Variables were very new (still in Beta).
Plan
Enable quicker design of secondary breakpoints
Get team consensus on primary breakpoint
Consult engineers for their side of the handoff story
Prioritize the components designers would need first
Communicate workload to adjust timeline expectations
Educate designers on variable use, benefits, and limitations
Challenge
Designers never had time for mobile designs for Optum Store.
Figma didn't allow variable mode rearrangement.
Designers didn't know what info developers needed.
Designers would begin using the new DS 2 weeks after I started.
I had to split my time between the DS and research work.
Variables were very new (still in Beta).
Plan
Enable quicker design of secondary breakpoints
Get team consensus on primary breakpoint
Consult engineers for their side of the handoff story
Prioritize the components designers would need first
Communicate workload to adjust timeline expectations
Educate designers on variable use, benefits, and limitations
Why have a researcher manage the DS?
I was hired as a UX Researcher, and there were 5 FTE designers on my team. So why did the Sr. Director and VP of UX choose me to upgrade the DS and handoff process?
Strategy + consistency
A competitive and heuristic evaluation I did for Optum Store, showed initiative, strategic thinking, and an eye for consistency.
Strategy + consistency
A competitive and heuristic evaluation I did for Optum Store, showed initiative, strategic thinking, and an eye for consistency.
Strategy + consistency
A competitive and heuristic evaluation I did for Optum Store, showed initiative, strategic thinking, and an eye for consistency.
Strategy + consistency
A competitive and heuristic evaluation I did for Optum Store, showed initiative, strategic thinking, and an eye for consistency.
Brand knowledge
I demonstrated a deeper knowledge of the Optum brand guidelines than other team members.
Brand knowledge
I demonstrated a deeper knowledge of the Optum brand guidelines than other team members.
Brand knowledge
I demonstrated a deeper knowledge of the Optum brand guidelines than other team members.
Brand knowledge
I demonstrated a deeper knowledge of the Optum brand guidelines than other team members.
Tech savvy
I was more skilled with Figma than anyone else on the team, especially with variables (and had a reputation for learning software quickly).
Tech savvy
I was more skilled with Figma than anyone else on the team, especially with variables (and had a reputation for learning software quickly).
Tech savvy
I was more skilled with Figma than anyone else on the team, especially with variables (and had a reputation for learning software quickly).
Tech savvy
I was more skilled with Figma than anyone else on the team, especially with variables (and had a reputation for learning software quickly).
Big-picture thinking
I'd shown that my decisions considered impacts beyond the next year and beyond the creative team.
Big-picture thinking
I'd shown that my decisions considered impacts beyond the next year and beyond the creative team.
Big-picture thinking
I'd shown that my decisions considered impacts beyond the next year and beyond the creative team.
Big-picture thinking
I'd shown that my decisions considered impacts beyond the next year and beyond the creative team.
Setting up smoother handoff
Although I have a lot of experience organizing, I’d never set up the file structure for a creative team, nor streamlined handoff. So I did research before forming suggestions:
How successful product teams structured their Figma teams, projects, and files
Asked engineers how file setup could make coding easier and more visually accurate
Key suggestions for Figma structure
A separate Figma project for each product team
Within that project, a file for each feature. Within files:
Sections for “In production”, “Ready for development”, “Design/Sandbox”
Color icons indicate design status
“In production” is the source of truth for that feature (DS files are source of truth for reusable components
Designers wanted to set up files their own way, so only a “Ready for development” section was consistent.
Designers felt it overwhelming for each feature to have a separate file, so each team had one official file, plus a designer sandbox file (for designer privacy while working).
Designers wanted to set up files their own way, so only a “Ready for development” section was consistent.
Designers felt it overwhelming for each feature to have a separate file, so each team had one official file, plus a designer sandbox file (for designer privacy while working).
Designers wanted to set up files their own way, so only a “Ready for development” section was consistent.
Designers felt it overwhelming for each feature to have a separate file, so each team had one official file, plus a designer sandbox file (for designer privacy while working).
Designers wanted to set up files their own way, so only a “Ready for development” section was consistent.
Designers felt it overwhelming for each feature to have a separate file, so each team had one official file, plus a designer sandbox file (for designer privacy while working).
Design formatting suggestions to aid engineers
I’d already been advocating for and training designers in using “auto layout” (instead of groups and spacers)
Variables were helpful for establishing design tokens
Layer naming clarified each layer’s purpose
Designs for the largest and smallest breakpoints, plus breakpoints in between where the layout or content changed (in orientation, size, ratio, or visibility).
It took persistence, but I got almost all designers on board with auto layout.
It took many months to convince designers to consistently design for the medium-size breakpoint.
I was surprised layer naming was one of the easier changes for designers to adopt.
It took persistence, but I got almost all designers on board with auto layout.
It took many months to convince designers to consistently design for the medium-size breakpoint.
I was surprised layer naming was one of the easier changes for designers to adopt.
It took persistence, but I got almost all designers on board with auto layout.
It took many months to convince designers to consistently design for the medium-size breakpoint.
I was surprised layer naming was one of the easier changes for designers to adopt.
It took persistence, but I got almost all designers on board with auto layout.
It took many months to convince designers to consistently design for the medium-size breakpoint.
I was surprised layer naming was one of the easier changes for designers to adopt.
Challenge 1: Design-centrism
Designers viewed Figma and the design system as design tools for designers. I viewed Figma and design systems as tools for communication across the entire product team.
This made it more difficult to convince designers to format files in a way that benefited non-designers.
This made it more difficult to convince designers to format files in a way that benefited non-designers.
This made it more difficult to convince designers to format files in a way that benefited non-designers.
This made it more difficult to convince designers to format files in a way that benefited non-designers.
What I'd do differently
Research designers on my team and their processes, to determine needs vs. wants.
Do more research on what people in other product roles need from Figma files.
Invite guests from different product roles to speak with designers about how to work with them effectively.
What I'd do differently
Research designers on my team and their processes, to determine needs vs. wants.
Do more research on what people in other product roles need from Figma files.
Invite guests from different product roles to speak with designers about how to work with them effectively.
What I'd do differently
Research designers on my team and their processes, to determine needs vs. wants.
Do more research on what people in other product roles need from Figma files.
Invite guests from different product roles to speak with designers about how to work with them effectively.
What I'd do differently
Research designers on my team and their processes, to determine needs vs. wants.
Do more research on what people in other product roles need from Figma files.
Invite guests from different product roles to speak with designers about how to work with them effectively.
Challenge 2: Untimely updates
Part of my role involved reviewing designs for DS alignment prior to handoff. I also needed to keep the design system up-to-date with any new components.
Designers often neglected to request a review before sharing designs with engineers, and didn't notify me when designs went live (ready to be added to the DS).
Designers often neglected to request a review before sharing designs with engineers, and didn't notify me when designs went live (ready to be added to the DS).
Designers often neglected to request a review before sharing designs with engineers, and didn't notify me when designs went live (ready to be added to the DS).
Designers often neglected to request a review before sharing designs with engineers, and didn't notify me when designs went live (ready to be added to the DS).
Attempted solution
I created a checklist to help designers remember to request a review, but they said a checklist felt overwhelming.
Attempted solution
I created a checklist to help designers remember to request a review, but they said a checklist felt overwhelming.
Attempted solution
I created a checklist to help designers remember to request a review, but they said a checklist felt overwhelming.
Attempted solution
I created a checklist to help designers remember to request a review, but they said a checklist felt overwhelming.
What I'd do differently
Set up two automated workflows in Slack (RVOH's main communication app):
When managers finish a design review, it posts that update to Jira, and notifies me to do a DS review.
When QA is finished, it posts the update to Jira, and notifies me and the designer.
What I'd do differently
Set up two automated workflows in Slack (RVOH's main communication app):
When managers finish a design review, it posts that update to Jira, and notifies me to do a DS review.
When QA is finished, it posts the update to Jira, and notifies me and the designer.
What I'd do differently
Set up two automated workflows in Slack (RVOH's main communication app):
When managers finish a design review, it posts that update to Jira, and notifies me to do a DS review.
When QA is finished, it posts the update to Jira, and notifies me and the designer.
What I'd do differently
Set up two automated workflows in Slack (RVOH's main communication app):
When managers finish a design review, it posts that update to Jira, and notifies me to do a DS review.
When QA is finished, it posts the update to Jira, and notifies me and the designer.
Variables for responsiveness and quick changes
Although variables made responsive design and brand realignments quicker, they were highly controversial among designers on my team.
What I did
Created and applied variables for color and size
Based size variables on existing patterns and the main DS
What I did
Created and applied variables for color and size
Based size variables on existing patterns and the main DS
What I did
Created and applied variables for color and size
Based size variables on existing patterns and the main DS
What I did
Created and applied variables for color and size
Based size variables on existing patterns and the main DS
Why
Color variables enabled easier brand changes and dark mode design.
Size variables enabled quicker responsive design and brand changes.
Variables had potential to improve consistency.
Why
Color variables enabled easier brand changes and dark mode design.
Size variables enabled quicker responsive design and brand changes.
Variables had potential to improve consistency.
Why
Color variables enabled easier brand changes and dark mode design.
Size variables enabled quicker responsive design and brand changes.
Variables had potential to improve consistency.
Why
Color variables enabled easier brand changes and dark mode design.
Size variables enabled quicker responsive design and brand changes.
Variables had potential to improve consistency.
Challenges with variable implementation
Wrong default mode
When I asked what our default breakpoint should be, the team chose mobile-first.
But for as long as I worked there, designers never started designing with the mobile breakpoint.
This made it more difficult for designers to use variables, and much more resistant to ever learning.
Wrong default mode
When I asked what our default breakpoint should be, the team chose mobile-first.
But for as long as I worked there, designers never started designing with the mobile breakpoint.
This made it more difficult for designers to use variables, and much more resistant to ever learning.
Wrong default mode
When I asked what our default breakpoint should be, the team chose mobile-first.
But for as long as I worked there, designers never started designing with the mobile breakpoint.
This made it more difficult for designers to use variables, and much more resistant to ever learning.
Wrong default mode
When I asked what our default breakpoint should be, the team chose mobile-first.
But for as long as I worked there, designers never started designing with the mobile breakpoint.
This made it more difficult for designers to use variables, and much more resistant to ever learning.
A new way of working
Over time, it became apparent that most designers on my team were opposed to learning how to use variables.
They were used to working a certain way, and did not want to change.
Variables require some effort to learn. And if you haven’t learned how to use them, it’s confusing to use components created with variables.
A new way of working
Over time, it became apparent that most designers on my team were opposed to learning how to use variables.
They were used to working a certain way, and did not want to change.
Variables require some effort to learn. And if you haven’t learned how to use them, it’s confusing to use components created with variables.
A new way of working
Over time, it became apparent that most designers on my team were opposed to learning how to use variables.
They were used to working a certain way, and did not want to change.
Variables require some effort to learn. And if you haven’t learned how to use them, it’s confusing to use components created with variables.
A new way of working
Over time, it became apparent that most designers on my team were opposed to learning how to use variables.
They were used to working a certain way, and did not want to change.
Variables require some effort to learn. And if you haven’t learned how to use them, it’s confusing to use components created with variables.
What I'd do differently
Make sure the team understood the impact of choosing a primary breakpoint.
Better convey to my manager the minimum understanding of variables every designer would need.
Observe designers working, and create trainings to show how they could incorporate variables into their current processes.
What I'd do differently
Make sure the team understood the impact of choosing a primary breakpoint.
Better convey to my manager the minimum understanding of variables every designer would need.
Observe designers working, and create trainings to show how they could incorporate variables into their current processes.
What I'd do differently
Make sure the team understood the impact of choosing a primary breakpoint.
Better convey to my manager the minimum understanding of variables every designer would need.
Observe designers working, and create trainings to show how they could incorporate variables into their current processes.
What I'd do differently
Make sure the team understood the impact of choosing a primary breakpoint.
Better convey to my manager the minimum understanding of variables every designer would need.
Observe designers working, and create trainings to show how they could incorporate variables into their current processes.
Splitting the DS into multiple files
There was a lot of back-and-forth about keeping the DS as one file or splitting it in two, but I believed splitting it would be better in the long-term, and convinced design leadership of the same.
Split for efficiency and organization
Reduced file size and simpler organization (and search)
Some files would only need blocks
Fewer components to search = faster locating
Easier for merchandisers to use
Split for efficiency and organization
Reduced file size and simpler organization (and search)
Some files would only need blocks
Fewer components to search = faster locating
Easier for merchandisers to use
Split for efficiency and organization
Reduced file size and simpler organization (and search)
Some files would only need blocks
Fewer components to search = faster locating
Easier for merchandisers to use
Split for efficiency and organization
Reduced file size and simpler organization (and search)
Some files would only need blocks
Fewer components to search = faster locating
Easier for merchandisers to use
Foundations + small components
Foundations + small components
Foundations + small components
Foundations + small components
Blocks + page templates
Blocks + page templates
Blocks + page templates
Blocks + page templates
Photography + illustration
Photography + illustration
Photography + illustration
Photography + illustration
DS sandbox (WIP + archive)
DS sandbox (WIP + archive)
DS sandbox (WIP + archive)
DS sandbox (WIP + archive)
Challenge 1: Contentful discontent
I had been updating some components directly in the design system, but this led to confusion for the CX team, because that version wasn't the same as what was available in Contentful. Since Contentful doesn't provide previews, merchandisers had no way to know what blocks would actually look like.
We also found that developers were naming things differently than the Figma designs (adding even more confusion).
Solutions
This fix was a priority, but the DS file was still a mix of live, ready for dev, and yet-to-be-updated components.
So I created a new file with a page that had sections for "In production", "In development", and "Ready for development" (with relevant instances of components and blocks in each section).
I also worked with a content designer to rename blocks and components, and we spoke with product owners and engineers to ensure future naming consistency.
Solutions
This fix was a priority, but the DS file was still a mix of live, ready for dev, and yet-to-be-updated components.
So I created a new file with a page that had sections for "In production", "In development", and "Ready for development" (with relevant instances of components and blocks in each section).
I also worked with a content designer to rename blocks and components, and we spoke with product owners and engineers to ensure future naming consistency.
Solutions
This fix was a priority, but the DS file was still a mix of live, ready for dev, and yet-to-be-updated components.
So I created a new file with a page that had sections for "In production", "In development", and "Ready for development" (with relevant instances of components and blocks in each section).
I also worked with a content designer to rename blocks and components, and we spoke with product owners and engineers to ensure future naming consistency.
Solutions
This fix was a priority, but the DS file was still a mix of live, ready for dev, and yet-to-be-updated components.
So I created a new file with a page that had sections for "In production", "In development", and "Ready for development" (with relevant instances of components and blocks in each section).
I also worked with a content designer to rename blocks and components, and we spoke with product owners and engineers to ensure future naming consistency.
What I'd do differently
Start with only "in production" components in the DS. Everything still in-the-works would be in feature or WIP files.
Establish naming conventions for blocks and components at the start, and get the whole product team on the same page.
What I'd do differently
Start with only "in production" components in the DS. Everything still in-the-works would be in feature or WIP files.
Establish naming conventions for blocks and components at the start, and get the whole product team on the same page.
What I'd do differently
Start with only "in production" components in the DS. Everything still in-the-works would be in feature or WIP files.
Establish naming conventions for blocks and components at the start, and get the whole product team on the same page.
What I'd do differently
Start with only "in production" components in the DS. Everything still in-the-works would be in feature or WIP files.
Establish naming conventions for blocks and components at the start, and get the whole product team on the same page.
Challenge 2: Multiple sources of truth
When new components went live, the team design file was still referenced as the source of truth, even though the design system was supposed to be the most current version.
I tried to get designers to move the main component to the design system, but had difficulty getting them to adhere for several reasons:
A lack of Figma knowledge (how to move components without detaching instances).
Designers unsure of which page to put the components in.
Designers didn’t want to format designs to match the rest of the design system.
I tried to get designers to move the main component to the design system, but had difficulty getting them to adhere for several reasons:
A lack of Figma knowledge (how to move components without detaching instances).
Designers unsure of which page to put the components in.
Designers didn’t want to format designs to match the rest of the design system.
I tried to get designers to move the main component to the design system, but had difficulty getting them to adhere for several reasons:
A lack of Figma knowledge (how to move components without detaching instances).
Designers unsure of which page to put the components in.
Designers didn’t want to format designs to match the rest of the design system.
I tried to get designers to move the main component to the design system, but had difficulty getting them to adhere for several reasons:
A lack of Figma knowledge (how to move components without detaching instances).
Designers unsure of which page to put the components in.
Designers didn’t want to format designs to match the rest of the design system.
Attempted solution
I offered to move components to the DS, but designers often forgot, and I was trying to reduce the amount of time I spent on the DS (since I also had research responsibilities).
Attempted solution
I offered to move components to the DS, but designers often forgot, and I was trying to reduce the amount of time I spent on the DS (since I also had research responsibilities).
Attempted solution
I offered to move components to the DS, but designers often forgot, and I was trying to reduce the amount of time I spent on the DS (since I also had research responsibilities).
Attempted solution
I offered to move components to the DS, but designers often forgot, and I was trying to reduce the amount of time I spent on the DS (since I also had research responsibilities).
What I'd do differently
Create a simple tutorial document (with video) showing how to transfer and format DS components.
Discuss component location in DS meetings.
Work with product team to clarify where to find source of truth, and the importance of updating the creative team when QA is complete.
What I'd do differently
Create a simple tutorial document (with video) showing how to transfer and format DS components.
Discuss component location in DS meetings.
Work with product team to clarify where to find source of truth, and the importance of updating the creative team when QA is complete.
What I'd do differently
Create a simple tutorial document (with video) showing how to transfer and format DS components.
Discuss component location in DS meetings.
Work with product team to clarify where to find source of truth, and the importance of updating the creative team when QA is complete.
What I'd do differently
Create a simple tutorial document (with video) showing how to transfer and format DS components.
Discuss component location in DS meetings.
Work with product team to clarify where to find source of truth, and the importance of updating the creative team when QA is complete.
Impacts of my DS work
Better communication between designers + developers
I taught designers how and why to format files for easier interpretation by developers.
Better communication between designers + developers
I taught designers how and why to format files for easier interpretation by developers.
Better communication between designers + developers
I taught designers how and why to format files for easier interpretation by developers.
Better communication between designers + developers
I taught designers how and why to format files for easier interpretation by developers.
Improved internal + brand consistency
Components, spacing, color, and photography became noticeably more consistent.
Improved internal + brand consistency
Components, spacing, color, and photography became noticeably more consistent.
Improved internal + brand consistency
Components, spacing, color, and photography became noticeably more consistent.
Improved internal + brand consistency
Components, spacing, color, and photography became noticeably more consistent.
Superior responsive design
I advocated for designing for small and medium screens, and variables made responsive design much quicker.
Superior responsive design
I advocated for designing for small and medium screens, and variables made responsive design much quicker.
Superior responsive design
I advocated for designing for small and medium screens, and variables made responsive design much quicker.
Superior responsive design
I advocated for designing for small and medium screens, and variables made responsive design much quicker.
Nimble brand updates
The way I set up the DS allowed us to quickly make changes caused by brand realignments.
Nimble brand updates
The way I set up the DS allowed us to quickly make changes caused by brand realignments.
Nimble brand updates
The way I set up the DS allowed us to quickly make changes caused by brand realignments.
Nimble brand updates
The way I set up the DS allowed us to quickly make changes caused by brand realignments.
Learnings about design systems + grids
Design system management
I learned a great deal about what works and what doesn't.
Design system management
I learned a great deal about what works and what doesn't.
Design system management
I learned a great deal about what works and what doesn't.
Design system management
I learned a great deal about what works and what doesn't.
Grid use
I haven’t had formal graphic design training, so checking designs for grid alignment vastly improved my understanding of grids.
Grid use
I haven’t had formal graphic design training, so checking designs for grid alignment vastly improved my understanding of grids.
Grid use
I haven’t had formal graphic design training, so checking designs for grid alignment vastly improved my understanding of grids.
Grid use
I haven’t had formal graphic design training, so checking designs for grid alignment vastly improved my understanding of grids.
Designing systems for multiple roles
It felt like designing an entire product on my own. And it would have gone more smoothly if I had done more user research beforehand.
Designing systems for multiple roles
It felt like designing an entire product on my own. And it would have gone more smoothly if I had done more user research beforehand.
Designing systems for multiple roles
It felt like designing an entire product on my own. And it would have gone more smoothly if I had done more user research beforehand.
Designing systems for multiple roles
It felt like designing an entire product on my own. And it would have gone more smoothly if I had done more user research beforehand.
