Deloitte Design System

Redefining te colour palette

Redefining te colour palette

Redefining te colour palette

Client

Deloitte UK

Info

Role

Product Designer

Timeline

3 weeks

Focus

Design Systems, Accessibility, Brand Alignment

Platforms

Web applications

Team

Product Owner
Project Manager

Tech Lead

Developers

(Back/Front - End, QAs)

Context

The Project

During my tenure at Deloitte Design System team, I was tasked with solving a critical design challenge that was impacting our entire product ecosystem.


Our diverse portfolio of applications suffered from inconsistent colour usage, accessibility issues, and a little disconnect from Deloitte's brand identity.


What started as a colour audit evolved into a comprehensive design system transformation that would redefine how our teams approach visual design across all platforms.

How might we create a colour system that scales with our growing product portfolio while maintaining accessibility and brand integrity?

Outcome

The redesigned colour system established a scalable, accessible foundation that reduced design decision fatigue by 70%, improved WCAG compliance across all platforms, and created a unified visual language that strengthened brand consistency while empowering teams to build faster and more cohesively.

(A)

UI Audit

This example illustrates how platforms were being shipped without proper design system foundations, resulting in interfaces that may function but fail to provide optimal user experience or brand consistency. The lack of systematic colour guidelines creates maintenance challenges and inconsistent user interactions across the platform.

(D)

Existing colour palette

The existing colour system shown here represented Deloitte's official brand palette, carefully developed by their branding team for traditional marketing and print applications. This comprehensive palette included over 40 colour variations organised into primary, secondary, and tertiary categories, each with specific hex values and naming conventions.

Primary palette
greens and blues

$deloitte-green

#86bc25

$primary-teal

#0D8390

$primary-blue

#007CB0

$primary-green-1

#43B02A

$primary-green-2

#26890D

$primary-green-3

#046A38

base & Alerts colours

$black

#000

$gray-8

#27282A

$white

#fff

$red

#DA291C

$orange

#ED8B00

$yellow

#FFCD00

secondary palette
Background & Greys

$background-gray-1

#FAFAFA

$background-gray-2

#F5F5F5

$background-gray-3

#EBEBEB

$gray-1

#D0D0CE

$gray-2

#BBBCBC

$gray-3

#A7A8AA

$gray-4

#97999B

$gray-5

#75787B

$gray-6

#63666A

$gray-7

#53565A

bright shades

$bright-green

#0df200

$bright-teal

#3efac5

$bright-blue

#33f0ff

Tertiary palette
greens, TEALS and blues

$secondary-green-1

#E3E48D

$secondary-green-2

#C4D600

$secondary-green-3

#009A44

$secondary-green-4

#2C5234

$secondary-teal-1

#DDEFE8

$secondary-teal-2

#9DD4CF

$secondary-teal-3

#6FC2B4

$secondary-teal-4

#00ABAB

$secondary-teal-5

#0097A9

$secondary-teal-6

#007680

$secondary-teal-7

#004F59

$secondary-blue-1

#A0DCFF

$primary-teal

#0D8390

$secondary-blue-2

#62B5E5

$secondary-blue-4

#0076A8

$secondary-blue-5

#005587

$secondary-blue-6

#012169

$secondary-blue-7

#041E42

Part One:

Uncovering the chaos

1.1 The Challenge Revealed

I began this project by conducting a comprehensive audit of our existing applications. What I discovered was more complex than anticipated: our teams were struggling with an overwhelming palette of colours that lacked structure, purpose, or accessibility guidelines. The existing system, originally designed for print materials, simply wasn't meeting the needs of our digital-first product environment.

1.2 Understanding Current Behaviour

How are teams currently using our colour system?


Designers were making ad-hoc colour decisions due to unclear guidance

Developers were implementing inconsistent colour values across platforms

Brand colours were being misused or ignored entirely

Accessibility requirements were often overlooked during implementation

1.3 Identifying User Pain Points

Through interviews with 10 designers and 5 developers, several critical issues emerged:

Designer Frustrations:

Developers Frustrations:

These pain points highlighted a fundamental issue: our colour system was creating barriers rather than enabling efficient, accessible design and development.


The feedback demonstrated an urgent need for a more structured, semantic approach that would serve both design creativity and development efficiency while prioritising accessibility from the ground up.

1.4 The Decision Point

While the team initially leaned toward Option 3—it felt like the safer, more manageable route—most agreed that Option 2, would be a more comprehensive approach and allows to save on deployment time in the near future.


Our research showed that surface-level fixes wouldn’t solve the underlying issues causing design inconsistencies and slowing us down. With the team's backing, we chose to invest in a more strategic solution that addressed the root causes.


It wasn’t just about accessibility compliance—it was about improving team velocity, reducing design debt, and building a scalable, future-proof system.

While the team initially leaned toward Option 3—it felt like the safer, more manageable route—most agreed that Option 2, would be a more comprehensive approach and allows to save on deployment time in the near future.

Our research showed that surface-level fixes wouldn’t solve the underlying issues causing design inconsistencies and slowing us down. With the team's backing, we chose to invest in a more strategic solution that addressed the root causes.


It wasn’t just about accessibility compliance—it was about improving team velocity, reducing design debt, and building a scalable, future-proof system.

While the team initially leaned toward Option 3—it felt like the safer, more manageable route—most agreed that Option 2, would be a more comprehensive approach and allows to save on deployment time in the near future.

Our research showed that surface-level fixes wouldn’t solve the underlying issues causing design inconsistencies and slowing us down. With the team's backing, we chose to invest in a more strategic solution that addressed the root causes.


It wasn’t just about accessibility compliance—it was about improving team velocity, reducing design debt, and building a scalable, future-proof system.

Part Two:

Building the Foundation

2.1 Collaboration Strategy

Working closely with Deloitte's Brand team became crucial early in the process. The existing colour palette was optimised for print applications and needed fundamental adaptation for digital environments. This collaboration ensured that our new system would maintain brand integrity while serving the practical needs of web applications.

2.2 Research-Driven Design Decisions


Through my research, I identified key user stories that would drive our design decisions:

Part Three:

Designing the Solution

3.1 Key Feature 1 - Semantic Colour Roles


The biggest breakthrough was establishing a rule of 100 that redefined colours with clear semantic roles. Expanding the spectrum of existing colours provided flexibility when choosing and forming colour groups, and instead of arbitrary names, each colour now served a specific purpose:


Primary Colours: Core brand colours for key actions and brand moments

Secondary Colours: Alert colours. Success, warning, error, and information states

Neutral Colours: Typography, backgrounds, and structural elements

Data Visualisation Colours: Specially curated palette for charts and graphs

Primary COLOURS

Secondary Colours

Neutral Colours

100

#FAFAFA

200

#F5F5F5

300

#EBEBEB

400

#D0D0CE

600

#A7A8AA

700

#97999B

800

#75787B

900

#63666A

1000

#53565A

1100

#27282A

100

#FAFAFA

200

#F5F5F5

300

#EBEBEB

400

#D0D0CE

500

#BBBCBC

600

#A7A8AA

700

#97999B

800

#75787B

900

#63666A

1000

#53565A

1100

#27282A

Graph and Visualisation Colours

100

#E3E48D

200

#C4D600

300

#43B02A

400

#009A44

600

#046A38

700

#2C5234

800

#75787B

900

#63666A

700

#6FC2B4

800

#00ABAB

800

#0097A9

900

#007680

1000

#004F59

900

#A0DCFF

1100

#00A3E0

700

#0076A8

700

#005587

800

#012169

800

#041E42

900

#FFCD00

900

#B22222

1000

#FFA500

#E3E48D

#C4D600

#43B02A

#009A44

#046A38

#2C5234

#75787B

#63666A

#6FC2B4

#00ABAB

800

#0097A9

#007680

#004F59

#A0DCFF

#00A3E0

700

#0076A8

700

#005587

#012169

#041E42

#FFCD00

#B22222

#FFA500

(F)

3.2 Key Feature 2 - The Token Architecture Strategy

I developed a three-tier token system that would serve different user needs:


Brand Tokens: The foundational palette containing all approved colours

Alias Tokens: Semantic groupings that communicate the colours' purpose and usage

Mapped Tokens: Context-specific applications for different themes and components

This structure allowed for maximum flexibility while maintaining strict governance over colour usage.

(F)

3.3 Key Feature 3 - Theme Flexibility


The new system supported multiple built-in themes, allowing for:

Light and dark mode compatibility

High contrast options for accessibility

Brand-specific themes for different product lines

(F)

3.4 Key Feature 2 - Accessibility-First Approach


Every colour combination was tested across multiple visual impairment scenarios:

Protanopia (red-green colour blindness)

Deuteranopia (green colour blindness)

Tritanopia (blue-yellow colour blindness)


This testing revealed that several bright colours in previous colour palate were indistinguishable to users with colour vision deficiencies, leading to strategic refinements that improved usability for all users.

(F)

Graphs & Visualisation colours

The appropriate use of certain colours in the design system was critical in making data visualisation successful by ensuring adequate contrast from primary colour groups, limiting single-colour usage per chart to maintain brand consistency, and applying semantic colour meaning across different chart types for intuitive user comprehension.

Popular times

Tuesdays

peak

9a

12p

3p

6p

9p

Sales by product

Alpha

Beta

Gamma

Delta

Company performance

1500

1000

500

0

2013

2014

2015

2016

Sales

Expenses

Users in the last 30 days

600

400

200

0

Nov 5

15

25

Dec 5

Category A

Category B

Category C

Popular times

Tuesdays

peak

9a

12p

3p

6p

9p

Sales by product

Alpha

Beta

Gamma

Delta

Company performance

1500

1000

500

0

2013

2014

2015

2016

Sales

Expenses

Users in the last 30 days

600

400

200

0

Nov 5

15

25

Dec 5

Category A

Category B

Category C

(A)

Before and After

We consolidated the interface from competing blue and green primary colours to a unified theme system, establishing a primary colour as the singular colour for all interactive elements while keeping graph and visualisation elements distinctive, creating stronger brand consistency and reducing cognitive load for users.

Part Five

Implementation and Impact

5.1 Rollout Strategy


The implementation was carefully orchestrated across three phases:

Phase 1: Documentation and training for design and development teams

Phase 2: Implementation in new projects and major updates

Phase 3: Gradual migration of existing applications


5.2 Measuring Success


In the first 2 months after rolling out the new colour system.


Quantitative Results:

70% reduction in colour-related design decisions during project work

100% WCAG AA compliance across all new implementations

60% faster developer implementation of colour changes

40% reduction in colour-related bug reports


Qualitative Improvements:

Increased confidence in design decisions

Stronger brand consistency across all touch-points

Improved collaboration between design and development teams

Better accessibility outcomes for end users


5.3 Long-term Impact


The new colour system became the foundation for broader design system improvements, enabling:


Faster onboarding of new team members

More efficient cross-team collaboration

Stronger brand presence in the market

Better user experiences across all applications

(I)

Key Learnings

This project reinforced several important principles about design systems work:


1. Systems thinking requires deep user empathy - Understanding the needs of internal users (designers and developers) was just as important as considering end-user needs.


2. Accessibility isn't optional - Building accessibility into the foundation of the system was far more effective than trying to retrofit it later.


3. Change management is design work - The success of a design system depends heavily on adoption, which requires careful attention to communication, training, and transition planning.


4. Collaboration amplifies impact - Working closely with brand, engineering, and product teams created better outcomes than working in isolation.


Through this project, I learned that effective design systems aren't just about creating beautiful, consistent interfaces—they're about empowering teams to work more efficiently while ensuring that every user interaction reflects both usability best practices and brand values.


The true measure of success wasn't just in the visual improvements, but in how the system enabled better collaboration and more inclusive user experiences across our entire product ecosystem.

You may also like

Work with me

Want to make your dream project come true?

Want to make your dream project come true?

Want to make your dream project come true?

Send me a project inquiry

Or send me an email

Recommendations

“Dedicated and detail-oriented designer with a strong growth mindset, always striving to improve and enhance user experiences.”

Ivana D.

Senior Product Designer at Deloitte UK

“Highly creative, hard-working designer with strong project management and communication skills. He excels at meeting deadlines, presenting ideas, and solving design challenges.”

Katherine M.

Marketing Manager at South Bank Colleges

“Proactive and insightful designer who quickly delivers quality work. At Helsa, his clickable prototype played a key role in securing VC-backed accelerator funding.”

Rob C.

Entrepreneur & Fintech Leader

Let's talk

drigofernando@gmail.com

© Rodrigo Fernando 2025

© Rodrigo Fernando 2025

© Rodrigo Fernando 2025

Rodrigo Fernando

Rodrigo Fernando

Rodrigo Fernando