Brand Governance

When to use this

Use when a brand system exists and now has to survive an organization. Use when every decision escalates to one person, when teams route around the guidelines, when temporary exceptions have quietly become the standard, or when nobody can say who owns a decision.

Use it before a brand scales into new teams, markets, or agencies — governance written after drift begins is a cleanup project rather than a system.

Do not use it to write approval processes for their own sake. Every control has a cost paid by people trying to do their work.

Inputs

The identity system's recognition map — which elements carry recognition and which support. The verbal system's rules and its own view on which are core. The world's recurring behaviors and their owners. The strategy, so that protection can be justified by strategic contribution rather than by habit.

Also required: who actually exists. Real names, real roles, real capacity. Governance assigned to a role nobody holds is a fiction that fails on its first test.

Ask who actually holds each role, by name, before assigning any decision right. Governance assigned to a role nobody holds is a fiction that fails on its first real test.

Mission

Keep the brand coherent without turning the organization into an approval machine.

Governance is a speed instrument. Its job is to make most decisions require no permission at all, by making it obvious which few decisions genuinely matter.

Method

1. Inventory brand elements and behaviors — visual, verbal, experiential, environmental.
2. Map each on two axes: recognition importance and strategic contribution. Protection follows this map, not seniority, sentiment, or how long something has existed.
3. Classify into four tiers.
   • Core — carries recognition or strategic meaning. Changing it damages equity. Rare.
   • Controlled — significant but adaptable within rules. Reviewed, not owned.
   • Flexible — teams decide. Variation costs the brand little.
   • Experimental — deliberately open, time-boxed, observed. Most elements should end up flexible. If most are core, you have not classified; you have cataloged.
4. Assign decision rights by name: who decides, who approves, who is consulted, where it escalates, and how long a decision should take.
5. Set review thresholds with a stated reason for each. A control with no reason is a habit.
6. Name the source of truth — where current strategy, assets, templates, and rules live, who maintains it, and how someone knows they have the current version.
7. Define drift signals and how each is detected. Drift found by accident is found late.
8. Write the exception protocol: reason, owner, expiry date, and a required decision at expiry about whether the exception should become the rule.
9. Write the evolution protocol: equity at risk, expected benefit, evidence, reversibility, transition cost, affected surfaces, validation plan.

What must be established

That someone unfamiliar with the strategy can use this document to decide. Governance is written for the person under deadline who has never met the brand team, not for the brand team.

That evolution has a path. A brand that cannot change without a crisis will change during one, badly. The evolution protocol is what makes protection safe rather than brittle.

Strong versus merely controlling

Governance is strong when teams stop asking permission for things that never mattered.

Failure modes

• Protecting every historical detail equally, which trains people to ignore all of it.
• Requiring approval for low-risk choices, which creates a bottleneck and then a workaround.
• Letting temporary exceptions silently become permanent standards.
• Confusing consistency with sameness. Recognition tolerates variation; it requires the right things to recur, not everything.
• Writing governance for the brand team's convenience instead of the operating team's decisions.
• Assigning ownership to a role rather than a person, so nobody is actually accountable.
• Building a system with no route to evolution, guaranteeing the brand ages until it breaks.

Never claim without evidence

Never assert that a rule protects equity without saying what evidence supports that element being recognition-bearing. Much of what organizations protect most fiercely was never tested and is protected by habit.

Never claim that governance improved consistency, speed, or quality without a before-and-after measurement. State what you would measure and who would look.

Output

Produce governance-manual.md using the structure in references/governance-manual.md.

Verification

• Stranger test. Give the manual to someone unfamiliar with the strategy and five realistic hypothetical decisions — a new market landing page, an event backdrop, a partner co-brand, a product illustration style, an urgent campaign with no time for review. If they cannot tell what they may change, what needs review, and who decides, the governance is incomplete.
• Bottleneck test. Count the decisions routing to one person. If it is most of them, the classification failed regardless of how correct it looks.
• Exception audit. Look at every exception currently in effect. Any without an expiry is now policy that nobody decided.
• Evolution rehearsal. Walk a real proposed change to a core element through the protocol. If the protocol cannot process a plausible change, it will be bypassed when one arrives.
• Counterfactual pass. For each recommendation: if it were removed, what meaningful outcome becomes less likely? No credible answer means cut it, downgrade it, or reframe it.
• Fresh-eyes pass. Read the output as someone who must act on it and was not in the process. Cut process debris, duplicated findings, unearned certainty, and any sentence that impresses without changing a decision.

Complete when

Teams can move quickly inside clear boundaries, every consequential decision has a named owner, and the organization knows how to evolve the brand without destroying its equity by accident.

Handoff

Brand Critic and Brand Review use the classification to weight findings — drift in a core element is a different severity from drift in a flexible one, and without this map every finding looks equally urgent. Brand Ship verifies that decision rights, source of truth, and exception log are real and reachable before launch, not aspirational.