Design systems have a reputation for being something only large companies can afford: hundreds of components, a dedicated team and a documentation site of their own. Small organizations need them just as much, for a simpler reason. When everyone who touches your brand makes the same small decisions the same way, you look consistent without having to think about it.
Start with decisions, not components
A design system is really a set of decisions written down. Which colors do we use, and for what? Which typefaces, at which sizes? How much space goes between things? What do buttons look like? Make these few decisions once, deliberately, and you've removed hundreds of small choices people would otherwise make differently every time.
Keep the palette small
Most brands need far fewer colors than they think: a background, a text color, a softer text color for secondary information, one accent and a couple of colors for success and error messages. Give each color a job, not just a name. When a color has a job, people know when to use it and, just as importantly, when not to.
Pick a type scale and stick to it
Choose a handful of text sizes, from a large headline down to small print, and use only those. A fixed scale is what makes a page feel organized. It also makes life easier for anyone writing content, because they're choosing from four or five options instead of guessing.
Build the pieces you actually use
Look at what your website and documents need today: buttons, cards, a navigation bar, a few page layouts, form fields. Design those properly and stop there. You can add more pieces when a real need appears. A small system that's fully used is worth more than a large one that's mostly ignored.
Write down the why
A short note next to each decision explaining the reasoning helps people apply it to new situations. "We use the accent color only for things people can click" is far more useful than a color swatch on its own, because it answers the next question before anyone has to ask it.
Make it easy to follow
The best system is the one that's easier to use than to ignore. On a website, that means the decisions live in the code, so building a new page with the right colors and spacing is the default. For documents and social posts, it means templates that already follow the rules. People are rarely trying to break a brand. They're usually just missing a template.
Let it grow with you
Treat the system as a living thing. When something new comes up that doesn't fit, decide how to handle it and add that decision to the system. Every few months, look at what's being used and what isn't, and tidy up. A small system that's maintained stays useful for years.
Where we come in
When we design a brand or build a website, we leave behind a simple system like this: the colors, type and components we used, how to use them and the templates to make it easy. It means the work stays consistent long after launch, whoever is making the next page or post.
