Most brand guidelines fail quietly. Nobody rejects them — they are approved, filed, and everyone carries on designing from the last file they opened. As a Product Studio that builds brands and the products they live in, the guidelines we are handed at the start of a project are usually a PDF nobody has opened in two years — beautiful, complete, and describing a company that no longer exists. What follows is what belongs in the document, what keeps it in use, and twelve public examples worth studying.

What Are Brand Guidelines (Brand Book)

Brand guidelines are the decisions about how a brand is expressed, written down so other people can apply them without asking.

"Brand book", "brand manual" and "style guide" usually mean the same artefact. The distinction worth keeping is between the brand layer — logo, colour, type, voice, imagery — and the product layer, a design system of real components. Large companies maintain both and connect them; smaller ones need one document covering both.

The document is not the brand. The brand is what people experience; the guidelines keep that experience consistent when fifteen people are producing work in parallel.

The test: if someone new can produce a correct banner, email and product screen without asking a designer, the guidelines work. If they have to ask, it's a reference document rather than a working one.

Why Tech Companies Need Brand Guidelines

In a tech company the brand is applied by people who are not designers. Engineers ship interfaces, sales builds decks, support writes help articles, recruiters design job posts — all making brand decisions all week.

Without written rules, those decisions get made from whatever file is nearest — a two-year-old deck, a screenshot, a competitor's site. Nothing looks obviously wrong, and the whole thing drifts.

The second reason is speed: a guideline is a decision made once instead of every time.

The third is procurement. Enterprise buyers, app stores and marketplaces ask for brand assets with usage rules attached, and not having them is a visible gap at the wrong moment.

What to Include in Brand Guidelines

Logo Usage

Primary logo, variants and rules — minimum size, clear space, approved backgrounds, and what can never be done to it.

The part most often skipped is the one most needed: a "don't" section with real examples. Stretched, recoloured, placed on a photo, outlined, used as a watermark. People copy pictures, not paragraphs. Say which file to use where, too — most misuse is someone grabbing a PNG off a slide.

Color Palette

Primary, secondary and functional colours with values in every space they will be used — HEX, RGB, and CMYK or Pantone if anything is printed.

Values alone are not rules. State proportion, approved pairings and the contrast requirement. Accessibility belongs here, not in an appendix: a colour pair that fails contrast is not a brand decision, it is a defect. For products, express colours as tokens — a token survives a palette change, a hex copied into forty files does not.

Typography

Typefaces, weights, scale, line height, and licensing — who holds the licence and what it covers. A web licence bought for a marketing site frequently does not cover an app or a client-facing document. Specify fallbacks, and the font non-designers use in slides and email when the brand font isn't installed — otherwise they choose one themselves.

Tone of Voice

The hardest section to write and the one that changes the most work. Three sentences of adjectives are not a tone of voice.

What works: before-and-after pairs — the same message written badly and well, with a note on what changed. Rules for the moments that matter: errors, refusals, pricing, bad news. A short list of words you use and words you don't.

Imagery and Iconography

Photography direction with examples of what fits and what doesn't, illustration style, icon grid and stroke weight, and how screenshots of your own product are framed.

Product screenshots are the most-used image type in a tech company and the least governed. Decide the frame, the data shown, light or dark, and whether real customer data may appear at all.

UI Kit and Digital Components

Where the brand becomes a product: tokens, components, states, spacing, grid, and behaviour at each breakpoint.

The connection point matters most. A component library that drifts from the brand layer produces a product that looks like a relative of the marketing site rather than the same company. Name one source of truth per decision.

Rules for AI-Generated Content

New, and increasingly the section that saves the most rework. Teams are generating copy, images and whole layouts, and without rules the output is a plausible average of the internet.

Cover at least: whether generated imagery may be published and where, whether your typeface licences permit it, what must be disclosed, who reviews before publication, and the voice instructions to paste into a prompt. If the guidelines don't answer these, each team invents its own answer this quarter.

12 Brand Guidelines Examples from Tech Companies

Public documents worth reading for what each does well.

1. Atlassian Design System — brand and product in one system, with content guidance sitting beside components rather than in a separate document.

2. Shopify Polaris — exceptional content and voice guidance for an interface, down to how to word an error.

3. IBM Carbon — the clearest public example of a design system tied to a parent design language.

4. Material Design 3 — the reference for token-based theming and for explaining the reasoning behind each rule.

5. Microsoft Fluent 2 — one system across web, desktop and mobile, with platform differences stated rather than hidden.

6. GitHub Primer — a working brand section alongside the product system, including real "don't" examples.

7. Spotify Design & Branding Guidelines — written for third parties, which forces unusual precision about what is and isn't allowed.

8. Mailchimp Content Style Guide — still the benchmark for tone of voice, with a voice and tone section built around the reader's emotional state.

9. Mozilla — identity rules for an organisation whose assets are used by contributors worldwide.

10. Figma brand guidelines — short, specific trademark and logo rules aimed at people outside the company.

11. Uber Base — a product system built for a brand that has to work in dozens of markets and scripts.

12. Apple Human Interface Guidelines — not a brand book, but the model for explaining why a rule exists.

A pattern across all twelve: they are websites, not PDFs. The format is the point.

How to Keep Brand Guidelines Alive

Put them on a URL, not in a file. A PDF is out of date the moment it's attached to an email. A page can be corrected on a Tuesday.

Name an owner. Not a committee — one person who decides and can be asked.

Date every section and log changes. "Updated March 2026" tells a reader whether to trust the page.

Put assets one click away. Most violations are convenience, not rebellion. If the logo pack sits behind a request form, people use whatever is on their desktop.

Show the exceptions you approved. Real campaigns that broke a rule, with the reason. Without them the document reads as theoretical and gets ignored on the first hard case.

Review it when the business changes, not on a calendar. New market, product line or segment — those are the moments guidelines go stale.

Our branding work treats guidelines as a deliverable with an owner and a review date, not a file handed over at the end — the FlyStraightLine case shows that applied across a product and its communications. For building a brand rather than documenting one, see branding for startups.

Brand Guidelines Template

A minimum structure. Everything here earns its place; anything else is optional.

01  BRAND BASICS

What we do, for whom, in one paragraph

What we are not

02  LOGO

Primary / variants / minimum size / clear space

Approved backgrounds — Don'ts, with pictures

Which file to use where

03  COLOUR

Primary / secondary / functional — HEX, RGB, print

Proportion, approved pairings, contrast minimums

Token names (product)

04  TYPOGRAPHY

Typefaces, weights, scale, line height

Licence holder and what it covers

Fallbacks for slides and email

05  VOICE

How we sound — before / after pairs

Errors, refusals, pricing, bad news

Words we use / words we don't

06  IMAGERY

Photography direction / illustration / icons

Product screenshots: frame, data, theme

07  DIGITAL

Tokens, components, states, spacing, grid

Source of truth per decision

08  AI-GENERATED CONTENT

Where allowed, licensing, disclosure, reviewer

Voice instructions for prompts

09  ADMIN

Owner, last updated, change log, asset links

U1CORE is a product digital studio that works like consultants. Partner in Crime for strong businesses whose digital and operations don't yet play at their level. Websites · Product · Branding · Software — see our branding work, or book a strategy call.