All writing
Skill guide

Design systems for tiny teams (the African startup way)

You do not need a design systems team to have a design system. You need taste, three tokens, and the discipline to actually use them.

Dre 08 Dec 2025 9 min read
A modular design system grid with reusable UI components.

Most design systems content online is written for the team building Material Design at Google. Six designers, three engineers, a release schedule. Most African startups do not have that. They have one designer, two engineers, and a deadline. The good news is that the design system you actually need at this size is much smaller than the internet would have you believe.

Three tokens beat fifty components

At the smallest scale, a design system is three things: colour, type, and spacing. Get those right and the components write themselves. Pick six colours. Pick two font sizes for body and three for headings. Pick a spacing scale of four, eight, twelve, sixteen, twenty four. That is the system. Everything else is built on top.

Save them as Figma variables on day one

The moment you have your six colours, save them as variables, not as styles. Variables can be referenced in code, switched between themes, and updated globally. Same with your spacing scale and your font sizes. The cost of doing this on day one is ten minutes. The cost of doing it after the fact is days of cleanup.

Component library, not pattern library

Build five components in the first week. Button, input, card, badge, modal. That is enough for ninety percent of a marketing site or an internal tool. Resist the urge to design a 'system' of twenty components before the first one ships. Designing in the abstract is fun. Designing against real screens is what makes a system useful.

Documentation, the cheap version

Documentation does not mean a Notion site with twenty pages. It means one paragraph per component, in the Figma file, explaining when to use it and when not to. If a new designer joins the team and reads the file, they should be able to ship a screen without bothering anyone. That is the bar.

The audit

Open your current product file. Count the unique colours used. If it is more than ten, you have drift. Count the unique font sizes. If it is more than seven, you have drift. Count the gap values. If you see threes, fives, sevens, you have drift. Spend a weekend pulling everything back into the system. Productivity for the rest of the year will compound from that fix.

I used to design every new feature with new colours and new spacing because I was bored. Then I had to ship four features in a month. The system saved me. Boredom is not a design constraint.
Cohort 01 student
D

Dre

08 Dec 2025 , 9 min read

All writing
Cohort 01 · Now enrolling

You know the path.
Take the first step.