M1 Design System
Building an unified design system for consistency and efficiency
A design system built from the ground up across our channels to minimise ambiguities and enhance workflows.
Design Lead
Audit
Leadership
Strategy
UI/UX

The problem
Designs shipped out were not governed by an established design system. There was no common foundation across M1's digital products and design artefacts were scattered across multiple Figma files.
Lack of governance and documentation
Design inconsistencies surfaced across channels
No system for documenting screen iterations

The solution
Build a unified internal design system in Figma, starting with cleaning up the UI patterns.
The objective was to bring consistency, help to reduce design time, and to provide a shared design language across all four channels (web, app, sales console and agent console).
It will also enable faster onboarding and knowledge transfer for the team.
Design system benchmark study
Before jumping straight into building our system, desk research on existing design systems was conducted to help us set a baseline for quality and features.

Our users
We also looked at who would be using the system and how we could make it easy and frictionless for them.
Designers
ProductOwners
Marketing
Tech
Constraints to work around
How we built it
Four interconnected libraries rather than have all of them in a flat file library.
Foundations › Components › Templates › Flows
Each of these libraries links from the next level down which enables better control when syncing.
•
Intended friction prevents changes rippling into dependent files.
•
Prioritises control over convenience, at least at the start.

Unifying four channels’ foundation
After our design audit, we found that each of the four channels had its own foundation artefact, with its own colours, typography scales and spacing.
From an efficiency perspective, it was essential to unify these into one shared foundation.
•
Foundations defined once and shared across all four channels.
•
Easier to scale as new channels or components are added.

Components first
Building components first was a deliberate choice, based on both our designers’ capacity and short-term delivery goals. Components are used by all screens, thus providing more rapid and accurate ways for designers to create content.
•
Designers used the components in their workflow straight away.
•
The system gave immediate value, so adoption happened naturally.

Templates for page consistency
During the enhancements, I also explored a few directions for the home screen plan card.
The existing design was built to show a fixed set of things: data, talktime, SMS. Whenever the business added a new entitlement to keep up with the market, there was nowhere good to put it, and the card got more cluttered.
From the explorations, I shortlisted two options to start the conversation with stakeholders:
•
Designers used the components in their workflow straight away.
•
The system gave immediate value, so adoption happened naturally.

What the system delivered
194
Components built for four channels
50%
Time reduction on design iterations by using components
75%
Improvement on new design requests
What’s next
Token architecture
Introduce tokens and align the system with code, addressing the trade-off made when components came first.
Roadmap
A high-level plan to be established to provide clarity of the system’s direction.
Revisit templates
Figma Slots to be added to the templates to improve scalability.
M1 Design System
Building an unified design system for consistency and efficiency
A design system built from the ground up across our channels to minimise ambiguities and enhance workflows.
Design Lead
Audit
Leadership
Strategy
UI/UX

The problem
Designs shipped out were not governed by an established design system. There was no common foundation across M1's digital products and design artefacts were scattered across multiple Figma files.
Lack of governance and documentation
Design inconsistencies surfaced across channels
No system for documenting screen iterations

The solution
Build a unified internal design system in Figma, starting with cleaning up the UI patterns.
The objective was to bring consistency, help to reduce design time, and to provide a shared design language across all four channels (web, app, sales console and agent console).
It will also enable faster onboarding and knowledge transfer for the team.
Design system benchmark study
Before jumping straight into building our system, desk research on existing design systems was conducted to help us set a baseline for quality and features.

Our users
We also looked at who would be using the system and how we could make it easy and frictionless for them.
Designers
ProductOwners
Marketing
Tech
Constraints to work around
How we built it
Four interconnected libraries rather than have all of them in a flat file library.
Foundations › Components › Templates › Flows
Each of these libraries links from the next level down which enables better control when syncing.
•
Intended friction prevents changes rippling into dependent files.
•
Prioritises control over convenience, at least at the start.

Unifying four channels’ foundation
After our design audit, we found that each of the four channels had its own foundation artefact, with its own colours, typography scales and spacing.
From an efficiency perspective, it was essential to unify these into one shared foundation.
•
Foundations defined once and shared across all four channels.
•
Easier to scale as new channels or components are added.

Components first
Building components first was a deliberate choice, based on both our designers’ capacity and short-term delivery goals. Components are used by all screens, thus providing more rapid and accurate ways for designers to create content.
•
Designers used the components in their workflow straight away.
•
The system gave immediate value, so adoption happened naturally.

Templates for page consistency
During the enhancements, I also explored a few directions for the home screen plan card.
The existing design was built to show a fixed set of things: data, talktime, SMS. Whenever the business added a new entitlement to keep up with the market, there was nowhere good to put it, and the card got more cluttered.
From the explorations, I shortlisted two options to start the conversation with stakeholders:
•
Designers used the components in their workflow straight away.
•
The system gave immediate value, so adoption happened naturally.

What the system delivered
194
Components built for four channels
50%
Time reduction on design iterations by using components
75%
Improvement on new design requests
What’s next
Token architecture
Introduce tokens and align the system with code, addressing the trade-off made when components came first.
Roadmap
A high-level plan to be established to provide clarity of the system’s direction.
Revisit templates
Figma Slots to be added to the templates to improve scalability.
M1 Design System
Building an unified design system for consistency and efficiency
A design system built from the ground up across our channels to minimise ambiguities and enhance workflows.
Design Lead
Audit
Leadership
Strategy
UI/UX

The problem
Designs shipped out were not governed by an established design system. There was no common foundation across M1's digital products and design artefacts were scattered across multiple Figma files.
Lack of governance and documentation
Design inconsistencies surfaced across channels
No system for documenting screen iterations

The solution
Build a unified internal design system in Figma, starting with cleaning up the UI patterns.
The objective was to bring consistency, help to reduce design time, and to provide a shared design language across all four channels (web, app, sales console and agent console).
It will also enable faster onboarding and knowledge transfer for the team.
Design system benchmark study
Before jumping straight into building our system, desk research on existing design systems was conducted to help us set a baseline for quality and features.

Our users
We also looked at who would be using the system and how we could make it easy and frictionless for them.
Designers
ProductOwners
Marketing
Tech
Constraints to work around
How we built it
Four interconnected libraries rather than have all of them in a flat file library.
Foundations › Components › Templates › Flows
Each of these libraries links from the next level down which enables better control when syncing.
•
Intended friction prevents changes rippling into dependent files.
•
Prioritises control over convenience, at least at the start.

Unifying four channels’ foundation
After our design audit, we found that each of the four channels had its own foundation artefact, with its own colours, typography scales and spacing.
From an efficiency perspective, it was essential to unify these into one shared foundation.
•
Foundations defined once and shared across all four channels.
•
Easier to scale as new channels or components are added.

Components first
Building components first was a deliberate choice, based on both our designers’ capacity and short-term delivery goals. Components are used by all screens, thus providing more rapid and accurate ways for designers to create content.
•
Designers used the components in their workflow straight away.
•
The system gave immediate value, so adoption happened naturally.

Templates for page consistency
After building the components, we built the page templates for all four channels to maintain layout consistency across screens.
•
Designers used the components in their workflow straight away.
•
The system gave immediate value, so adoption happened naturally.

What the system delivered
194
Components built for four channels
50%
Time reduction on design iterations by using components
75%
Improvement on new design requests
What’s next
Token architecture
Introduce tokens and align the system with code, addressing the trade-off made when components came first.
Roadmap
A high-level plan to be established to provide clarity of the system’s direction.
Revisit templates
Figma Slots to be added to the templates to improve scalability.