Design Systems

A design system is a shared set of decisions, written down once and used everywhere. It cuts development time and costs, raises product quality, keeps the brand consistent and gets designers and developers talking the same language.

How it works

It runs in three steps.

1. Audit. We look at how your team works today and choose an approach that fits it.
2. A shared language. We name the colours, type, spacing and components, and organise the information so everyone finds it.
3. The design system. We build it, prototype with it and support your team while it settles in.

What you get

The service is built to get a team up to speed fast, so they learn how to make a design system real and keep using it. You get templates to start from, live coaching sessions, remote team workshops and recordings of every session. Bring your whole team.

Who it’s for

Product teams of about 10 people or more. At that size communication gets complex, and a design system starts to save time. Teams usually see their productivity go up by around 10 percent, sometimes much more.

Questions teams ask

Do we need new tools? Most likely not. A design system works with what you already use: Figma, Sketch, Notion, GitHub or GitLab.

We don’t have the resources. How does this get on our roadmap? We start with an MVP design system and apply it in one pilot project. It helps you use the resources you have, before you commit more.

Do we need to hire someone for it? Usually not. One team can run the design system for everyone, or people from each team share the work.

Is it worth starting one? Yes, for teams that want to scale their design and engineering output without hiring. A design system can raise a team’s efficiency by 5 to 50 percent and lower costs. Ask us for examples.