Branding guide · Decision tool
Brand guidelines are not a moodboard or a PDF trophy. They are operating rules for logo use, color roles, type hierarchy, voice, image style, proof language, accessibility, and misuse.
rules · roles · misuse · surfaces
A useful guideline system grows with operating complexity. Every rule needs a current asset, an example, an owner, and a way to handle exceptions; otherwise the document records preferences but cannot control execution.
| Operating stage | Minimum contents | Control model | Review trigger |
|---|---|---|---|
| Founder-led | Position, promise, voice, primary mark, palette, type, image direction, and core templates. | One named owner and one current asset location. | A new channel, offer, contributor, or recurring misuse. |
| Growing team | Add audience rules, message hierarchy, component examples, accessibility, production files, and approval thresholds. | Functional owners with a documented approval path. | A new team, vendor, market, or material delivery inconsistency. |
| Multi-offer | Add offer relationships, naming rules, endorsement logic, cross-sell language, and shared-versus-local assets. | Architecture owner plus offer-level stewards. | An acquisition, launch, overlap, or buyer confusion between offers. |
| Multi-market | Add localization principles, language ownership, cultural review, legal constraints, and market exceptions. | Global standards with named local decision rights. | Entry into a new language, jurisdiction, or distribution model. |
| Regulated or high-risk | Add claim substantiation, mandatory disclosures, records, accessibility evidence, escalation, and version history. | Formal review roles and auditable release records. | A rule change, claim change, incident, or approved exception. |
A working guidelines outline with real applications, owners and exception rules.
Build the guide around failure points, not around decoration.
| Area | Rule to define | Surface to test | Common failure |
|---|---|---|---|
| Logo and wordmark | Clear space, minimum size, color versions, lockups | Header, avatar, package, deck, partner page | Stretched mark or fake lockup |
| Color | Primary cue, accents, backgrounds, functional states | Buttons, labels, charts, packaging, dark mode | Mood color replacing role color |
| Typography | Scale, hierarchy, case, spacing, fallback | Homepage, product UI, proposal, mobile | Big type with no reading system |
| Voice | Sentence behavior, proof style, forbidden tone | Support, search, sales, social, policies | Every channel sounds like a different company |
| Imagery | Subject, crop, light, proof standard, no-use examples | Hero, product, case study, article, social | Generic stock doing the brand's job |
| Proof language | Claims allowed, claims banned, evidence needed | CTA, promise, comparison, guarantee, FAQ | Confident adjectives with no backing |
These findings provide context for the choices above. Their original dates and scope remain visible; they are not measurements of your business.
Follow-up questions and the limits of the method.
Long enough to resolve recurring decisions, and no longer. A small team may need a concise operational guide; a multi-market or regulated organization may need linked standards, asset libraries, and approval records rather than one oversized PDF.
Include the minimum strategic context needed to explain each rule: audience, position, promise, proof, personality, and deliberate tradeoffs. Without that context, teams can apply assets correctly while communicating the wrong idea.
Show a real surface, identify the decision, explain why the approved version works, and name the failure in the rejected version. Decorative mockups do not teach teams how to handle production constraints.
Assign one accountable system owner, then name decision rights for strategy, language, design, product, accessibility, legal review, and local exceptions. Shared participation should not mean unclear final authority.
Update when a rule, asset, channel, offer, market, or responsibility changes. Also schedule a periodic usage review so the guide reflects approved practice rather than preserving obsolete instructions.
If a name, color, mark, message, voice, or page is starting to affect sales or trust, get the public-facing decision checked before rollout makes it harder to change.