← All work

MIB / Astralis Design System

Better services.
Shared foundations.

I introduced and designed MIB’s first design system, bringing a shared visual language to a growing family of services.

My role
Design direction · System design
The client
Motor Insurers’ Bureau
In use across
Check Services · Sign-in · Accounts
MIB’s design systemAstralis

A shared language.
A stronger starting point.

Astralis green and neutral colour scales
TYPOGRAPHYAa

Clear hierarchy.
Consistent rhythm.

Astralis button variants, colours and interaction states

01 / The starting point

Why MIB needed a design system

MIB’s services had developed different interfaces and ways of working. Inconsistent design, workflows and messaging made the experience feel disjointed. Bespoke solutions also meant the same design decisions had to be revisited each time a service changed.

I introduced Astralis to give that work a shared foundation. The ambition was to support individual service improvements while making MIB’s wider digital experience more coherent.

From

Disconnected services.

Different interfaces. Bespoke solutions. Inconsistent experiences.

To

Shared foundations.

A common design language that connects services and supports the next improvement.

02 / Making the case

An investment in how we work

Designing the library was one part of the task. I also created material to help the business understand why a design system was worth investing in, connecting consistency and reuse with the practical work of maintaining and improving services.

The case was about more than individual screens: it was about creating a stronger starting point for the teams designing them.

View the business-case presentation ↗
01

Foundations

Colour, typography and visual style.

02

Components

Reusable controls, variants and states.

03

Services

Shared foundations applied to real customer tasks.

03 / Colour

A common language for colour

The base library separates accent, neutral and semantic colours. Its colour scales group values by their role, from backgrounds and interactive components to borders, solid fills and text.

That gives colour a purpose within the interface. The same structure extends into light and dark schemes, with the theme variables providing a shared place to configure the visual language.

Astralis light colour scales grouped by interface role
Light scheme: accent and neutral scales, organised around how colour is used.
Astralis dark colour scales grouped by interface role
Dark scheme: the corresponding scales in the base library.

04 / Typography

Hierarchy that carries across the experience

The typography foundations pair font size with line height and letter spacing, rather than treating each setting in isolation. A nine-step scale creates a consistent hierarchy, supported by light, regular, medium and bold weights.

These shared decisions give different services a common rhythm, from a short field label to a page heading or a longer piece of guidance.

TYPE SCALEAa

One hierarchy.
Many different tasks.

Light · Regular · Medium · Bold
Original Astralis typography guidance with nine type sizes, line heights, letter spacing and four weights
The typography specification, exported from Astralis Base.

05 / Components

Shared parts, built for different needs

Astralis brings common interface building blocks into one place. The library includes buttons, text fields, selection controls, navigation, feedback and data-display components.

Component properties make the variations explicit. Buttons, for example, have sizes, visual variants, colour roles, icon options and loading states. Those choices allow a shared component to support different tasks without starting again each time.

The original Astralis button component set showing sizes, variants, accent neutral and error colours, and states
One component family, with consistent options across size, colour, variant and state.

06 / Interaction and guidance

Designing beyond the default state

The system defines more than how a control looks before someone uses it. Button properties include default, hover, active and disabled states, alongside focus-ring and loading options.

The supporting documentation shows how those properties work, with examples in light and dark schemes. It connects the component library to the decisions a designer makes when using it.

Astralis button usage documentation showing component properties and examples in light and dark themes
DOCUMENTED IN FIGMA

Options with context.

Size. Variant. Colour. Contrast. Icons. State. Loading.

The library brings the available choices and their examples together.

Explore the button library ↗

07 / From system to service

Putting the foundations to work

I used Astralis across the Check Services and Okta optimisation work, from choosing a service and entering information to signing in and recovering access.

These projects gave the system real customer journeys to support. Shared typography, colour, controls and hierarchy help connect different tasks into a more consistent family of experiences.

Astralis applied to the Check Services landing pageAstralis applied to MIB account sign-in
Shared foundations in use across Check Services and account access.

08 / A foundation for what comes next

Better together

Astralis established MIB’s first shared design system and gave the optimisation work a common starting point. The value is visible in the relationship between the library and the services: reusable parts supporting clearer customer journeys.

The Check Services case study shows those foundations in use. Vehicle Hub explores the longer-term vision they could help support.

Something you’re working on?

Get Jim on it

A new role, a project, or just a conversation.