Brand Decision Memo Template

Use the memo before the brand decision becomes a design invoice, agency scope, website rebuild, package run, or launch calendar.

The useful version is short. If the team cannot fit the verdict, evidence, preservation rule, test, and kill condition onto one page, the decision is not ready.

The memo should be written before a proposal becomes production. That timing matters because the room is still able to stop, narrow, test, or preserve the current cue.

A weak memo records what people like. A useful memo records what the market already knows, what will change, what must stay, what proof supports the move, and what result stops the rollout.

The evidence section should include customer facts, source links, search behavior, sales objections, case comparisons, recognition tests, support questions, conversion data, or public proof. If the evidence cannot be named, the verdict should not be PASS.

The preservation line is the most important line. It protects the name, mark, color, phrase, product cue, service ritual, page route, or proof block that still helps buyers choose.

The kill condition prevents sunk-cost theater. Decide in advance what drop in recognition, search, leads, conversion, trust, retention, or support clarity gives someone authority to pause or reverse the launch.

Use the memo as a boundary for agencies and internal teams. A scope that cannot answer the memo questions should be adjusted before budget moves.

The memo also protects institutional memory. Six months later, the team should be able to see why the change was approved, what evidence mattered, what was preserved, and what signal would have stopped it.

A useful memo is not long. It is specific. The best version can be read by the founder, designer, sales lead, support lead, agency, and future operator without needing the meeting transcript.

If the memo exposes that the team cannot name the problem, do not soften the verdict. Write ADJUST or STOP, then run the missing test before the work becomes public.

Attach the memo to the launch checklist. The preserved asset, source list, test threshold, and rollback owner should travel into production, otherwise the decision record dies before the risky work begins.

The memo is also a way to say no cleanly. A team can reject a name, logo, message, color, or website proposal without insulting the work when the record shows which proof, cue, or risk was missing.

A decision memo should have a review date. If the launch passes the threshold, archive the result. If the threshold fails, the owner has to choose repair, rollback, or a narrower rollout instead of letting the market absorb confusion.

Keep the memo close to the public assets. The website, source files, launch notes, search snippets, AI files, and internal handoff should all repeat the same preserved cue and proof rule so the decision survives implementation.

The weak version starts with a familiar sentence: the logo feels old, the website looks tired, the name sounds generic, the message feels flat, or AI describes the brand like everybody else. Those may be real symptoms. They are not yet a diagnosis.

The useful move is to name the broken layer. Is the customer unable to recognize the brand, trust the proof, understand the offer, repeat the name, cite the source, or take the next action? Each answer points to a different repair.

Do not let the team buy a new surface while the old constraint stays untouched. If the problem is proof, the work is proof. If the problem is retrieval, the work is source and category clarity. If the problem is recognition, the work is protecting the cue before changing it.

The stop rule should be written before the spend moves: what signal pauses the project, who owns the decision, and what happens if the change makes branded search, qualified leads, trust, or buyer comprehension worse?