Branding guide · evidence and decision
Use this logo change decision tree to decide whether to keep the mark, refresh it, redesign it, repair a different brand problem.
decision · proof · use
Change a logo only when the current mark creates a real business problem: buyers misread it, the mark fails at the surfaces where money is earned, it looks too close to competitors, it cannot survive small digital use, it carries trust damage, or it blocks a new category or audience. Refresh when recognition works but execution is messy. Keep the logo when customers still recognize and trust it. Repair proof, positioning, offer, website, or sales flow first when the logo is being blamed for a different problem. Stop when the team cannot name the recognition cue to protect, the test surface, the buyer risk, and the rollback condition.
Most teams ask about the logo when the business feels stale, confusing, or ignored. The logo may be part of the problem. It may also be the easiest object to blame.
A useful logo decision starts by naming the job the current mark performs. Does it help people recognize the company, find it in search, remember it on a sign, trust it on an invoice, choose it on a shelf, or identify it in an app? If the old cue still performs that job, the new mark has to beat it under real conditions.
A logo should change when the mark creates measurable friction: poor legibility, weak small-size performance, category confusion, competitor similarity, legal risk, damaged trust, poor accessibility, or a mismatch with a real audience or business-model shift.
A logo should not change because the founder is bored, a competitor looks newer, a redesign deck looks polished, or the website is not converting. Those may be proof, offer, positioning, traffic, or sales problems wearing a logo costume.
The decision should end in one of five verdicts: keep the logo, refresh the system, redesign the mark, repair a different brand problem first, or stop.
These cases show when a cleaner mark damaged recognition, when simplification worked, and when real-world reading conditions changed the answer.
Do not approve the logo at presentation size. Run it through the surfaces where customers actually see, search, trust, and choose the brand.
01
Keep the current mark when customers still recognize it, search it, refer to it, trust it, and identify it faster than the proposed replacement.
Show the current cue in the buying surface: shelf, sign, homepage, proposal, invoice, app icon, vehicle, package, or search result.
02
Refresh when the recognition cue works but execution is inconsistent: old file formats, weak spacing, messy lockups, poor templates, bad contrast, or outdated supporting type.
Name what stays exactly the same and what execution rules will be cleaned.
03
Redesign when the mark itself creates the problem: buyers misread it, it fails small, it resembles competitors, it cannot meet accessibility needs, or it no longer fits the category the business truly serves.
Show the failed mark beside competitors and at the smallest repeated surface.
04
Do not change the logo when the real issue is weak offer clarity, poor proof, unclear positioning, low-quality traffic, thin reviews, bad sales follow-up, or a website that does not explain the business.
Name the non-logo problem and the page, proof, offer, or sales behavior that must be fixed first.
05
Stop when nobody can name the protected recognition cue, the test audience, the test surface, the rollout bridge, the search and AI migration risk, and the rollback condition.
No protected cue, no surface test, no rollback means no approval.
06
Compare the old and proposed marks at favicon, phone, social avatar, package side, invoice, vehicle, storefront, presentation footer, and search result scale.
If the new mark is slower to recognize at the real surface, adjust or stop.
07
If the mark changes name, letterform, symbol, or public vocabulary, search snippets, AI summaries, third-party profiles, reviews, and old articles may keep retrieving the old cue.
Map old terms, new terms, redirects, alt text, logo files, social profiles, and entity names before launch.
08
Define the number that pauses the rollout if recognition, branded search, qualified leads, conversion, sales, or support confusion gets worse.
Use a threshold, date, owner, and reversal action before publishing the new mark.
A decision page has to prevent a bad approval, not merely define a term.
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 decision reason.
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?
Gap, Tropicana, Mastercard, Kia, Airbnb show why the same surface move can mean different things under different constraints.
Change the logo only if the current mark creates a real business problem: poor recognition, misreading, competitor confusion, small-size failure, damaged trust, legal risk, or a category shift the old mark cannot carry.
Do not change it when the real problem is offer clarity, positioning, proof, traffic quality, website conversion, sales follow-up, or founder boredom with a mark customers still recognize.
Refresh when the recognition cue still works and only execution needs cleanup. Redesign when the mark itself creates confusion, legibility failure, competitor overlap, accessibility problems, or category drag.
Run the old and new marks at the real surface: favicon, phone, sign, package, invoice, proposal, app icon, search result, and competitor row. If the new mark is slower to identify, it is not ready.
Bad reasons include trend pressure, internal boredom, copying a competitor, vague modernization, or using a logo change to avoid fixing proof, offer, product, website, or sales problems.
Keep the strongest cue, test the new mark beside the old one, bridge old and new language, update search and AI surfaces, and define the rollback condition before launch.
Decide the business problem, protected cue, test surface, buyer risk, search and AI migration plan, rollout owner, budget risk, and rollback condition.