Lead with what changes for the people who already deal with you, not with the new logo. A rebrand announcement that opens with color palettes and a redesigned wordmark is talking to your design agency, not your customers, who want to know whether their account, their contract, their contact person and the thing they bought from you are still the same. Get that order wrong and the coverage, if you get any, focuses on the name change as a curiosity rather than the business reason behind it. Here is what actually belongs in the announcement, two real examples of how different this can look, and the part most companies forget: what a rebrand does to the AI assistants and search engines that already have your old name memorized.
What actually has to be in a rebrand announcement?
Three things, in this order: why the rebrand is happening, what stays exactly the same for the customer, and what the new name or identity actually is.
The reason comes first because it's the only part of the announcement that is actually news. A new name on its own is not a story, it's an edit to a database. A reason tied to something real, a merger, a restructuring, an expansion into a market the old name didn't fit, a reputation the company is deliberately moving past, is the story a journalist can write and a reader can understand. Right after that, be explicit about continuity: the same product, the same support line, the same account team, the same contract terms, unless any of those are also changing, in which case say so plainly rather than letting a customer discover it later. Only then does the new name, logo and any visual identity belong in the release, as the answer to a question the reader already understands the reason for.
Is a marketing nickname the same as a legal rebrand?
No, and conflating the two is a common and avoidable mistake.
RadioShack's 2009 campaign is the clearest public example of the difference. The company began using "The Shack" in its advertising starting August 6, 2009, backing it with a large share of its roughly $200 million annual ad budget and a three-day launch event in Times Square and San Francisco's Justin Herman Plaza, according to contemporaneous coverage from ABC News and Chain Store Age. Critically, the company said at the time that it was not changing its legal name or its store signage, only the shorthand it used in marketing, the same way people already said "Coke" instead of "Coca-Cola." Then-CMO Lee Applbaum framed it as modernizing how people talked about the brand. It still drew plenty of mockery as a company trying too hard to sound current, criticism Applbaum later said faded. The lesson isn't that nickname rebrands fail, it's that announcing one as a full identity change when it isn't invites exactly the confusion RadioShack had to spend the launch explaining away.
What does a rebrand driven by a restructuring actually look like?
Anthology's move to Blackboard in March 2026 is a useful recent example, because the rebrand was a direct consequence of a business event, not a standalone marketing decision.
After completing a Chapter 11 restructuring that had been announced the previous fall, Anthology's core Teaching and Learning business re-emerged under the Blackboard name as a stand-alone company, according to Campus Technology's reporting. The same restructuring saw other parts of the business, the Enterprise Operations and Lifecycle Engagement units, sold off separately, with Ellucian and Encoura stepping in as buyers. Blackboard also announced $70 million in new financing as part of the relaunch. The company's own "We are now Blackboard" page was explicit that the full visual identity would follow at a later company event, rather than trying to land the restructuring news and a finished brand refresh in the same announcement. Separating "here is what just changed in the business" from "here is what the new brand will eventually look like" let each message land clearly instead of competing for attention in one release.
What makes a rebrand announcement backfire?
Treating the new identity as self-explanatory, and underestimating how attached customers are to the thing you're replacing.
A name, logo or color scheme that customers already recognize is a business asset, not just a design choice, and abandoning it abruptly without explaining the reason is the single most common way a rebrand turns into a story about the company rather than about whatever the rebrand was meant to signal. The RadioShack case shows the milder version of this, a nickname that drew eye-rolling coverage but did no lasting damage because the company was clear about what hadn't actually changed. The more expensive version happens when a company changes something customers relied on to identify the brand with no transition plan and no acknowledgment of what's being given up. Either way, the announcement is the place to get ahead of that reaction directly: say what you're keeping, not just what's new.
Who needs to know before the public does?
Employees, existing customers under contract, and any partner whose own materials reference your old name.
A rebrand that employees read about in the press before hearing it internally damages trust with the people who have to explain the change to customers on the ground. The same applies to any partner or reseller whose website, contracts or co-branded material still shows your old name or logo, since a public announcement they weren't warned about turns them into a second wave of confused customers. None of this needs to be elaborate, a short internal note and a heads-up email to key partners a day or two ahead covers most of it, but skipping it entirely is how a rebrand announcement generates avoidable "wait, since when" replies on the day it matters most.
What happens to your AI visibility when you change your name?
It resets, in effect, and nothing about the rebrand announcement itself fixes that automatically.
Every AI assistant and search engine that has indexed your old name, your old domain if that's changing too, and the pages that reference you, keeps reading and citing that material until something newer and more authoritative replaces it in what they're pulling from. A press release alone does not do that work, the same point covered in whether a press release or a blog post should carry a given piece of news. What does help is updating the structured parts of your own site, the kind of markup covered in using schema to help AI systems cite you accurately, getting your Wikipedia entry updated if you have one rather than left describing a company that no longer exists under that name, and making sure any llms.txt file, as described in the llms.txt guide, reflects the new name rather than the old one. None of that happens on its own the week you announce, and the gap between the announcement and an AI assistant actually catching up is exactly the period where a customer searching your old name should still reliably land on you.
The direct answer, for anyone who read this far
A rebrand announcement works when it leads with the business reason, states plainly what isn't changing for the customer, and only then introduces the new name or identity, in that order. Be precise about whether you're changing a legal name, as Anthology did in becoming Blackboard after its restructuring, or adopting a marketing nickname, as RadioShack did with "The Shack," because conflating the two creates confusion neither company intended. Brief employees and partners before the public announcement, not after. And plan for the fact that AI assistants and search engines will keep citing your old name for a while after the press release goes out, because the announcement itself does not update what they've already indexed, only your own updated pages and structured data do.
If you're planning a rebrand and want help sequencing the announcement and the AI-visibility cleanup that has to follow it, get in touch.
