Goodself Design System

Optimizing the Goodself colour system for white-labelling and efficient design handoff.

My role

UX/UI designer

Team

Lead UX/UI designer, product manager, lead developer

Timeframe

2 months

Context

Goodself is a health and wellness platform that provides patients with expert-led resources and health-focused groups.

Working with the team on this project, I evaluated the existing design system, proposed the direction, and led the implementation of colour updates.

The CHallenge

I was consulted about the feasibility of turning Goodself into a white-label platform.

I evaluated the existing screens, the colour system, and how the designers are implementing the brand guidelines.

An evaluation of the platform revealed three main underlying issues with the colour system.

Colour usage is overwhelming and makes information unclear.

Colour is used to differentiate items, but with many different colours used inconsistently, hierarchy of information becomes unclear.

The colour system makes branding unclear.

As colours keep being added, it is difficult to understand the Goodself's visual identity.

The lack of colour guidelines causes inconsistency.

Unorganized colour naming convention makes designers unsure which colours to use in different scenarios.

Goal and Approach

These significant issues needed to be addressed before we could consider white-labelling.

Discussing these issues with the product manager and lead UX/UI designer, I proposed a plan to update the colour system.

With a small team and limited time, we needed to balance effective changes with contraints.

Fully revising the entire colour system would not be possible, but leaving the system as is could result in compounding design issues in the future.

The system must be adoptable by designers and developers in a quick turnaround time.

- Product manager

The system should account for what designers and developers are already familiar with.

- Lead UX/UI designer and lead developer

Based on feedback from the team and constraints, this approach best fit our immediate needs.

Due to constraints, colour changes were limited to absolutely necessary changes and testing was limited to the main colour applications.

Implementation

Determining brand colours and scaling down colour system from 37 colours to 24.

Once I confirmed the brand colours with the product manager, I removed colours that can be replaced with existing ones.

Using mental models when assigning colour usage guidelines.

Colours were being used to indicate specific actions or statuses, but inconsistent colour usage can make it difficult for users to predict what they mean. Mental models were used to address this confusion.

Creating a understandable naming convention that accounts for updates and usage.

I created a new naming convention that allows designers to understand what the colour is used for and accounts for new colours added in.

Ensuring accessibility with WCAG standards.

Testing text colours on background colours, I made changes to colours that did not pass AA WCAG standards.

Setting up colour usage guidelines on a designated file.

I set up an excel sheet to keep track of colours and document colour updates, as both designers and developers preferred this format. This enabled designers to refer to the sheet for colour selection and direct developers to the sheet for any colour changes.

Implementing changes to the existing screens.

Passing on the sheet to the rest of the design team, I reviewed the colour changes on the Figma file to ensure they followed guidelines and explained the changes to the developers.

Result 1

Design handoff made more efficient by 30%.

Calculated based on average number of colour related revisions to ticket or design after handoff.

Result 2

100% of designers thought the changes positively impacted their workflow.

After the changes were implemented, I consulted the UX/UI team again for feedback.

Final Deliverables

A revised colour system that enables white-labelling and improves design effectiveness and handoff efficiency.

With a updated naming convention, understandable guidelines, and scalable system, the colour changes are currently in development and is the first step towards preparing the platform for white-labelling.

Reflection and Takeaways

Learning when to make changes to a large design system.

Through this experience, I learned the importance of having a solid and effective design system. Without a strong foundation, the underlying issues will still remain. This experience highlighted an example of needing to step back and make the necessary changes for product longevity.

Working with the limitations and advantages of a small team.

Working at a startup with a small team meant limited time and people to implement changes. I had to adapt and account for these factors, making sure that the changes would be both impactful and realistic. At the same time, this gave me the opportunity to be hands-on for most of the process.