How to Build a Brand Style Guide

Key Takeaways

• Order by frequency of use, not by conceptual hierarchy. Logo, colour, type, voice, then everything else.
• Exact values or it does not count. Hex, RGB, CMYK, font weights, minimum sizes, clear space. Approximations get approximated further.
• The "do not" examples are the most-read part of any guide, and the part most often left out.
• Voice needs examples, not adjectives. Show the same sentence written correctly and incorrectly.
• Put the files next to the rules. A guide that describes a logo without linking the logo gets ignored.
• Ship a short version. A five-page guide people read beats a fifty-page guide they do not.

Order by What Gets Asked

Open your messages and look at what people actually ask about the brand. It will be some version of: which logo file do I use, what is the exact blue, what font is this, can I use the logo on a photo, and how do we refer to the product.

Your guide should answer those in that order. Most guides do the reverse, opening with mission, values and brand essence, which are real and which nobody has ever opened a style guide to find.

A structure that works:

1. Logo: the files, the variants, when to use each, clear space, minimum size.
2. Colour: the palette with exact values, which is primary, accessible pairings.
3. Typography: the fonts, the weights, the scale, what to use when a font is unavailable.
4. Voice: how we write, with examples.
5. Imagery: what our photography and illustration look like, with examples.
6. Applications: common formats, laid out.
7. Do not: the mistakes, shown.

The essence and positioning material can exist and it belongs at the back or in a separate document. It is for people writing strategy, not for the person exporting a deck at five o'clock.

Exact Values, Not Approximations

Anything approximate gets approximated further by everyone downstream.

Colour needs hex, RGB and CMYK at minimum, plus Pantone if anything is printed. "Our blue" produces eleven blues within a year, all slightly wrong, all defensible.

Give the palette a hierarchy. Which is primary, which are secondary, which are accents, and what proportions look right. A palette of eight colours with no hierarchy produces work that uses all eight equally, which is why so much brand material looks like a paint chart.

Type needs the family, the weights you actually use, a size scale, and line heights. Also the fallback: what to use when the licensed font is not available, which happens constantly in email, in slide templates and on client machines. If you do not specify a fallback, everyone picks their own.

Logos need clear space and minimum size, expressed relative to the logo itself rather than in absolute pixels, so the rule survives scaling.

Accessibility belongs here, concretely. Which colour pairings pass contrast requirements for body text, and which are decorative only. Say it in the palette section, where it will be seen, rather than as an afterthought.

The Do-Not Section Is the Most-Read Page

Everyone who has made a style guide knows the do-not page gets more traffic than the rest combined, and a surprising number of guides omit it.

Show the mistakes, do not describe them. A grid of the logo stretched, recoloured, on a busy photo, too small, with a drop shadow, rotated. One image communicates more than a paragraph.

Include the mistakes that have actually happened. Generic misuse examples are copied from other guides; yours should include the specific thing your team keeps doing. If three people have put the logo on a photograph with no scrim, that goes on the page.

Say why for the ones that are not obvious. "Do not use the reversed logo on light backgrounds" is obvious. "Do not use the wordmark alone below 24px" needs the reason, which is that it becomes illegible, or people will assume it is a preference and override it.

Keep it visual and keep it near the front. Some guides put it last, where it is functionally invisible.

Voice Needs Examples

Voice sections fail more reliably than any other part of a style guide, because they are written as adjectives.

"Confident but not arrogant, friendly but not casual, clear but not simplistic" describes almost every brand ever documented and helps nobody write a sentence.

Show the same content written three ways and mark which is right. One too formal, one too casual, one correct. A reader learns more from that comparison than from a page of principles.

Give the specific rules that actually recur. Do we use contractions. Do we capitalise product names. Is it "sign up" or "signup". Do we say customers, users, or people. Are exclamation marks allowed. These are the questions writers hit hourly and they are answerable in a list.

Include a word list. Terms we use, terms we do not, and the correct spelling and capitalisation of our own product names. This is the most-used part of any voice section and the cheapest to write.

Name the things we never say. Competitor comparisons phrased a certain way, claims that legal will reject, jargon the founder dislikes. A short banned list is more useful than a long tonal description.

Put the Files Next to the Rules

A guide that describes assets without linking them creates a second search every time it is used.

Every logo variant shown should be downloadable from that page. Every colour should be copyable as a value. Every font should say where to get it and how it is licensed.

Licensing is the part people forget. A guide that says "our font is Inter" without saying who holds the licence and whether a freelancer may use it produces either a rights problem or a substitution nobody documented.

Templates beat instructions. A deck template, a social template, a document template do more for consistency than any amount of prose about how the brand should look, because most people are not building from scratch and do not want to.

If your guide is a PDF, accept that it will be out of date within months. A web page or a shared document that can be updated in place is better, and the single most important property of a guide is being current.

Ship the Short Version First

Most style guides fail by being ambitious.

A five-page guide covering logo, colour, type, voice basics and the do-not page is genuinely useful and can be made in a day. A fifty-page guide takes a month, is read by nobody, and is out of date on delivery.

Ship the short version, then extend it where questions keep arriving. The questions tell you what the next section should be, and a guide grown that way is composed entirely of things people needed.

Version and date it. People will have older copies, and a visible version number is how they discover that.

Name an owner. Style guides decay exactly like asset libraries, and for the same reason. Someone has to answer the edge cases and fold the answers back in.

Where Style Guides Legitimately Stop

A style guide describes decisions. It cannot make new ones, and pretending otherwise leads to guides that try to cover every case and become unusable.

There will always be a situation the guide does not cover: an unusual format, a co-branded piece, a campaign that needs to break the rules deliberately. The guide's job in those cases is to say who decides, not to have anticipated the case.

Add one line to the front: for anything this guide does not cover, ask [name]. That sentence prevents both paralysis and improvisation, and it is missing from most guides.

Storyflow is our product and it is not a brand guide tool. It does not host a style guide, does not manage brand assets or permissions, has no version control for guidelines and no templating for downstream files. Use a web page, a shared document, or a dedicated brand platform, and keep the assets in your library or DAM. The adjacent job is earlier: the exploration where the brand's directions get compared and chosen before anything is codified. Paid-only during early access, with the Free plan landing before the end of 2026, and anyone a paid member invites to a board joins free now.

The Bottom Line

A style guide is a reference document that people open in a hurry, and almost every failure comes from writing it as a presentation instead.

Order it by what gets asked, which means logo, colour, type, voice, then everything else.

Give exact values everywhere, because anything approximate gets approximated further by everyone downstream.

Write the do-not page and make it visual, including the specific mistakes your team keeps making.

Show voice, do not describe it, and include the word list, which is the part writers use hourly.

Put the files next to the rules, with licensing stated, and ship templates rather than instructions.

Then keep it short, keep it current, and name someone to ask for everything it does not cover.

A style guide is not a description of the brand. It is a set of answers to questions people are about to get wrong.