-
1
Catalog current usage before you write a rule
Before you write a single rule, document how the brand is actually being used today across every surface. A guideline written in a vacuum gets ignored because it does not match reality. Pull one week of calendar time and inventory the live surfaces: the homepage, five top landing pages, the latest investor deck, the sales deck, the top five social posts of the quarter, the last three customer emails, the last three partner comps, the product dashboard login, the hiring page, and the support macros. Screenshot each one and tag the inconsistencies (two blues in rotation, three logo variants, four voices between Sales and Support, random font pairings in the deck). This audit becomes the exhibit list that justifies every rule you are about to write and gives the Head of Sales or the CS lead something concrete to react to when they push back on a constraint later.
- Screenshot 20-30 live surfaces: homepage, top landing pages, decks, emails, social, product, hiring, support macros
- Tag inconsistencies by category: logo, color, type, voice, imagery, layout
- Pull the top 5 offenders into a one-page audit; this becomes the business case for the guideline
- Share the audit with Sales, CS, Product, and the founder before writing rules so pushback happens early
Tip: Half the rules you think you need will turn out to already be in use, and half the rules you did not expect to need will show up in the audit. Write the guideline against the audit, not against a Pinterest board.
-
2
Write 3 to 5 brand pillars that stand for something
The pillars are the top of the guideline because every downstream rule (voice, visual, imagery) ladders back to them. Write three to five pillars, each a short phrase and a two-to-three-sentence paragraph that says what the pillar means and what it rejects. A pillar that only says what the brand is for is weak; a pillar that also names what the brand refuses to be is a rule you can enforce. Draft the pillars from the brand strategy doc if one exists, from the customer research if not, and run them past three current customers and three employees before you lock them in. Avoid interchangeable adjectives (modern, bold, innovative, human) that any competitor could also claim. The test for a good pillar is whether a stranger could read it and tell your brand apart from the two closest competitors without seeing the logo.
- Draft 3-5 pillars; each has a short phrase, a two-to-three-sentence meaning, and an explicit rejection line
- Test every pillar with the differentiation question: could a competitor claim this with a straight face?
- Run the draft past 3 customers and 3 employees; cut any pillar that nobody can repeat 24 hours later
- Lock the final list and reference it at the top of every voice, visual, and imagery section downstream
Tip: If your pillars include the word "innovative," cut it. Every B2B company between $5m and $500m claims to be innovative; it is noise in the guideline, not a rule.
-
3
Write the voice section with do and do not examples
The voice section is where most guidelines go abstract and useless. A rule like "be confident but friendly" cannot be enforced, so write voice with concrete examples instead. For each voice attribute (typically 3 to 5), give a one-line definition, a short rationale that connects to a pillar, two do examples pulled from real approved copy, and two do not examples pulled from the audit or rewritten from competitor copy. Cover the places voice actually ships: subject lines, hero headlines, body copy, button labels, sales emails, support replies, release notes, error states, and social captions. Document the tone-shift rules (the voice bends more formal in security content, warmer in CS, more technical in product). Keep the voice section under eight pages; a 40-page voice guide gets skimmed and ignored.
- Define 3-5 voice attributes with one-line definitions and a rationale that ladders to a pillar
- Give 2 do and 2 do not examples per attribute, pulled from real copy or the audit, not invented
- Cover subject lines, headlines, body, buttons, sales email, support reply, release notes, errors, social
- Document tone-shift rules by context: security formal, CS warm, product technical; name the exceptions
Tip: The do not column teaches faster than the do column. Pull your worst three sentences from the last quarter of marketing emails and let them live as the "never again" exhibit at the bottom of the voice section.
-
4
Document the visual rules: logo, color, type, imagery
The visual section is where a guideline either becomes a tool or becomes decoration. Build it so a non-designer can produce a correct asset at 11pm. Cover the logo first (primary mark, lockups, clear space, minimum size, monochrome and reversed treatments, approved backgrounds, four to six misuse examples). Then color (primary, secondary, functional, and neutral palettes with hex, RGB, CMYK, and Pantone, plus AA accessibility pairings for every text-on-background combination). Then typography (primary and secondary families, weights in production use, hierarchy for H1 through body and caption, line-height and letter-spacing rules, approved web and desktop fallback stacks). Then layout and spacing (grid, modular scale, button and card specs, iconography set). Every rule should include a correct example, an incorrect example, and the asset path or Figma library link so a non-designer can grab the right file rather than rebuild it.
- Logo: primary, lockup variants, clear space, minimum size, mono and reversed, 4-6 misuse exhibits
- Color: primary, secondary, functional, neutral; hex, RGB, CMYK, Pantone; AA pairings for every combo
- Type: primary and secondary families with weights in use, H1 through caption hierarchy, line-height, fallbacks
- Layout and iconography: grid, modular scale, button and card specs, approved icon set and usage rules
Tip: Every visual rule needs a direct link to the production asset (Figma library, S3 bucket, Drive folder). A rule the designer or marketer cannot click through to is a rule they will skip under deadline pressure.
-
5
Define photography and illustration treatment
Photography and illustration are where off-brand work slips in most often because the rules are vague and the stock library is one search away. Define photography first: the subjects you will show (real customers and real product, not models in headsets), the lighting (natural, not studio), the framing (environmental, not isolated), the color grading (consistent lift and tone across the library), and the editing rules (no stock-photo smiles, no composite handshakes, no clip-art people pointing at laptops). Then define illustration: the style (geometric, hand-drawn, isometric, line-only), the palette constraint (uses the brand color system, not rainbow), the use cases (feature callouts, empty states, blog posts), and the don'ts (no 3D renders, no mascots, no clipart). Include six to ten approved examples per category and three to five rejected examples with annotations that say exactly which rule failed.
- Photography: subject, lighting, framing, color grading, editing; show 8-12 approved and 4-6 rejected
- Illustration: style, palette constraint, use cases; show 8-12 approved and 4-6 rejected with annotations
- Document AI-generated imagery policy explicitly: when it is allowed, when it is not, who approves
- Link to the approved stock accounts and the internal shoot library so no one defaults to free stock
Tip: The AI image rule now belongs in every B2B guideline. Decide whether AI-generated people are allowed on the site (the honest answer for most B2B companies is no), and write it down so the question stops showing up in Slack every month.
-
6
Build the template library: deck, doc, social, email
The guideline tells teams what to do; the template library is what actually makes them do it. Build a starter template for every surface people produce weekly: a sales deck master in Figma or Keynote with 12 to 20 approved layouts, a one-page proposal and a case-study doc template, three social post templates (announcement, data point, customer story), two email templates (newsletter and promo), a webinar landing page template, a one-pager and a long-form whitepaper template. Each template should ship with the brand assets pre-wired, voice-approved placeholder copy, locked color and type, and a one-paragraph instruction at the top that names the pillar and the voice attribute the template is enforcing. Templates are the lever that pulls the whole guideline into daily use; without them, the guideline is a reference nobody opens.
- Build sales deck master, proposal doc, case-study doc, 3 social templates, 2 email templates, 1 landing template
- Pre-wire assets, lock color and type, pre-fill voice-approved placeholder copy, add top-of-file instructions
- Name the owner for each template; templates get versioned with the guideline, not frozen in time
- Pilot each template with the team that will use it before locking; iterate based on real-use friction
Tip: The team never asks for the guideline. They ask for "the deck" or "the email template." If the templates are good, the guideline enforces itself through the templates. If the templates are bad, no amount of PDF enforcement will save you.
-
7
Publish to a shared workspace with version control
A guideline that lives as a PDF on Dropbox is a guideline that is already three versions behind. Publish the guideline to a shared workspace that supports version history, comments, and linked assets: Notion, Confluence, Guru, or a dedicated brand tool like Frontify or Brandfolder work. Give it a short memorable URL (brand.yourcompany.com or go.yourcompany.com/brand) and link it from the company handbook, the Slack welcome bot, the onboarding checklist, and the footer of the shared drive. Version the guideline semantically (v1.0 locked at launch, v1.1 for the first round of edits, v2.0 when a pillar changes), log a changelog at the top with date and reason, and name a single brand owner responsible for merge requests. Agencies and contractors get read access by default; edit access is restricted to the brand owner and a named deputy.
- Publish to Notion, Confluence, Guru, Frontify, or Brandfolder with a short memorable URL
- Version semantically: v1.0 locked at launch, v1.1 small edits, v2.0 when a pillar changes; keep a changelog
- Name a single brand owner plus one deputy; everyone else is read-access or submits comments
- Link from onboarding, Slack welcome bot, shared drive footer, and the sales and partner portals
Tip: The guideline URL belongs in every new hire's first-day welcome message. If a new seller or marketer joins and does not see the link in the first 24 hours, you have already lost a month of consistent output.
-
8
Train the team at a kickoff and set a review cadence
The guideline does not land because you published it; it lands because you ran a kickoff and set a review cadence. Hold a 45-minute cross-functional kickoff within two weeks of publishing: five minutes on the strategic reason, ten minutes on the pillars with the audit exhibit, fifteen minutes on voice with real do and do not examples, ten minutes on visual rules walking the Figma library live, and five minutes on how to submit a question or request an exception. Record it, post it in the brand workspace, and require it as part of new-hire onboarding for marketing, sales, CS, and product. Set a quarterly brand review on the calendar where the brand owner, one marketer, one seller, and one CS rep walk the live site, decks, and emails against the guideline and log drift. Rebuild the audit every six months. Without the cadence, drift compounds and you are back to a 2026 guideline running against 2027 reality.
- Hold a 45-minute cross-functional kickoff within 2 weeks of publishing; record it and post in the brand workspace
- Add the recording and a short quiz to new-hire onboarding for marketing, sales, CS, and product
- Schedule a quarterly brand review: brand owner plus 1 marketer, 1 seller, 1 CS rep walk live surfaces
- Rebuild the drift audit every 6 months and reset the top 5 offenders; version-bump the guideline
Tip: The quarterly brand review is 60 minutes on the calendar or the guideline dies. Put it in the ops cadence next to the pipeline review and the renewals forecast; it is the only recurring forcing function that keeps the brand from drifting back to pre-guideline chaos.