Selected works
04 / 05

Prefab Design System

My largest design system: modular, token-based and community-driven.

Company
Strike
Role
Design system lead
Tools
Figma, Confluence

The context

Strike (now Purplebricks) is a prop-tech company serving home buyers and sellers. Its products were growing, and a design system is what keeps a growing product coherent.

Shortly after joining, I was asked to lead the rebuild of the existing system. It's the largest design system I've worked on.

The problem

The existing design system was hard to find and hard to use. If people can't find a system, they don't use it, and then it isn't really a system.

The result showed up in handoffs. Developers received designs that lacked coherence, because designers had each made slightly different choices.

Type was a clear example. Ad hoc type sizes were used here and there, and a change in one place caused unexpected changes elsewhere.

The vision

I pitched a system that felt like a “beautiful store with an intuitive structure”: you walk in, you can see what's there, and you can take what you need.

It also had to be community-driven. A system owned by one person doesn't scale, so I wanted designers to feel they could contribute, not just consume.

The Prefab pitch presentation

What I did

  • Built a modular system, so teams take only the parts they need.
  • Moved to design tokens after ad hoc type sizes caused unexpected changes. One source of truth meant a change happened once and flowed everywhere.
  • Named it Prefab, a play on prefabricated buildings: ready-made parts that fit together to build something real.
  • Set up Figma libraries that can be toggled per file, so a file only carries what it uses.
  • Used Confluence for documentation and for communicating changes, so people knew what had changed and why.
  • Treated it as a living, version-controlled product, with releases and change notes, rather than a project that ends.
Type styles for mobile, tablet and desktopType tokens mapped to each breakpointPrefab componentsFigma libraries toggled per file

Making it a community

Adoption is the hard part, so I treated it as a product with users. Designers and developers were my customers, and I asked what got in their way.

I welcomed contributions and feedback, and I made it easy to see how a new idea could become part of the system. People who feel heard keep contributing.

Prefab documentation

The outcome

It was adopted and contributed to pretty much instantly.

Handoffs became more coherent, because designers and developers now worked from the same parts and the same tokens.

Takeaways

Building is hard, maintaining is harder. A launch is the start of the work, not the end of it.

Pitch a vision, then ask for time to expand it. A clear picture of where the system could go makes it easier to get the time to take it there.

Value feedback. The best improvements to Prefab came from the people using it.

Next work

Strike Hub redesign