Back to selected work

Element

Foundations that grow with the product.

Element is a shared effort across design, engineering and product. As engineering lead, I work on the architecture and tooling that help teams build with it.

My role
Design-system engineering lead
Team
2–4 engineers, alongside design and product
Platforms
Web and native
Element components, including usage charts, billing summaries and promotional cards
A selection of interfaces built from Element components. Image: Jason Christie.

Built alongside the product

Our shared challenge was to bring web and app patterns closer together while giving teams a practical path from older versions of Element.

The wider team rebuilt the logged-in customer experience in 12 weeks. Working on both product features and Element exposed where shared components helped, and where their APIs needed to change.

Alongside design and product counterparts, my remit covers engineering architecture, standards and releases. I also implement Element upgrades and build with its components in our app and websites.

That hands-on work feeds back into the system, alongside usage comparisons and a shared Forms API for web and native.

Four OVO quick-link cards for billing, moving home, switching supplier and meter readings.
  1. CardShared container
  2. Heading4Card title
  3. PSupporting copy
  4. ButtonIcon-only action
These OVO homepage cards combine four Element components with an image and custom hover styling. Shared foundations leave room for a distinct product pattern.

Tokens with clear contracts

I established a Style Dictionary token architecture that supports brands, themes and platform outputs. Teams can extend or override tokens while retaining the shared foundations.

Missing types and missed updates caused recurring friction. Stronger typing, tests and output validation made those contracts explicit, helping engineers change and consume tokens with more confidence.

  1. Primitivegreen-50
  2. Semanticcolor-brand-brand
  3. Componentbutton-filled-bg
A primitive green becomes the brand colour, then the background of a filled button.

The same foundations support AI-assisted development. Shared instructions and skills give coding tools our repository conventions; typed contracts, tests and visual review help us check what they produce.

Review without local setup

Flaky local Loki runs could take several attempts before a change was ready for review. Snapshot generation now runs entirely in CI, removing that setup from onboarding.

I built the pull-request sign-off workflow: reviewers approve a visual change, its baseline updates automatically, and a PR comment records the result. The team keeps control without repeating the manual work.

Baseline
Proposed
Illustrative snapshot comparison: the proposed button is taller and spans the form width. Reviewers can inspect the change before accepting a new baseline.

Understanding adoption together

The adoption dashboard is a collaboration with another engineer and our lead designer, who also manages Element. I developed much of the dashboard; we shaped its features and improvements together.

Opted-in repositories report component usage, library coverage and style deviations through react-scanner and GitHub Actions. The pilot covered a handful of projects, with wider rollout underway.

Stakeholders use it for adoption reporting. For the team, it starts conversations about overrides, upgrades and where support is needed.

Element overviewSample data
Component adoption
Style deviations
12%

24 of 200 instances with overrides

Projects on latest DS version
7of 12 projects
Illustrative sample data, not measured Element results: adoption rises from January to June, while 24 of 200 component instances have style overrides (12%) and 7 of 12 projects use the latest version.

For the wider design-system context, see Jason Christie’s account of Element.

Back to selected work