Somewhere in a university department right now, someone is using letterhead with a logo from four years ago. Not because they’re difficult. Not because they don’t care about the institution. Because no one gave them a compelling reason to do it differently, and the old file is right there on their desktop.

This is what brand inconsistency looks like in practice. Not a rogue creative director. Not a vendor who missed the brief. An administrator, a tenured member, a department manager are doing their job the same way they’ve always done it, completely unaware that anything has changed, or unconvinced that it matters if it has.

The University of Rochester launched a rebrand last year. The work itself — the visual system, the strategy behind it — was serious and considered. But if you ask the people who work there, many of them found out about it a few days before it went public. Some found out when they saw it. Some are still using the old templates.

That gap between a brand system that exists and a brand that actually lives in an organization is almost never a design problem. It’s a culture problem. And the design industry keeps treating it like the former.

The usual explanation

When a rebrand doesn’t take hold, the typical response is to produce more: more guidelines, more templates, more training sessions, more emails from central reminding people to use the updated assets.

The assumption is that the problem is informational. People don’t comply because they don’t know what to do.

This is rarely true. In most organizations, people know there’s a new brand. They just don’t believe in it, or more precisely, they don’t feel any ownership over it.

They weren’t part of the decision, they weren’t brought along on the thinking, and when it arrived, it arrived as a directive. Not an invitation.

The response to that isn’t more assets. It’s a different kind of process.

What happened at the University of Rochester

The University of Rochester’s rebrand followed a model that’s common in higher education and, honestly, in most large institutions: a small, central team did the work, leadership was briefed, and then it launched.

Deans and department chairs were brought in. Everyone else found out when the internal announcement went out, a few days before the rebrand went public.

The problem with this model isn’t that the circle of involvement was small. It should be small. Brand work done by committee is brand work that gets compromised.

The problem is that being outside the circle, and finding out at the end, signals something specific to the people on the receiving end: this wasn’t for you to weigh in on, and it isn’t really for you now. Here are the new rules. Good luck.

When leaders can’t explain the thinking behind a rebrand with any real conviction, their reports hear the silence — and decide the rebrand probably doesn’t matter much.

When you rely on trickle-down communication (brief the deans and department chairs, trust that they’ll will brief their departments) you lose the rationale at every layer.

A dean or department chair who sat in a presentation and got the full story can still communicate the gist. But the gist isn’t the same as the argument.

And when those leaders communicate to their departments, what lands isn’t “here’s why this matters strategically,” it’s “we have a new look, here’s where to find the templates.”

That’s not a failure of leadership. It’s a predictable consequence of a rollout model that treats internal communication as a relay race. Something gets lost in every handoff.

The deeper issue: design as decoration

There’s something else at play in universities specifically, though it’s not unique to them. Design — and brand strategy — isn’t widely understood as a strategic practice. It’s understood as a visual one.

This means when a rebrand happens, people receive it as: we changed how things look. Some people think it looks better. Some think it looks worse. Most go back to their day.

The strategic argument, that a brand is how an institution expresses what it stands for, differentiates itself, earns trust with the people it’s trying to reach, largely doesn’t land with people who weren’t in the room when it was made. Not because people are incapable of understanding it, but because they were never given the chance to engage with it.

If you want people to respect a rebrand as a strategic decision, you have to let them in on the strategy. Not to approve it. Not to give notes. But enough to understand what problem it’s solving and why it matters to them specifically.

The finance team doesn’t need to know about type systems. But they do need to know why the institution’s old identity was creating friction with the audiences that fund it, and what this new one is trying to do instead.

A different model

The solution here isn’t radical. It’s mostly about sequencing, and about who you treat as a stakeholder before the launch, not just after.

The first thing to change is when the internal conversation starts. Most institutions communicate the rebrand when it’s finished. The more effective approach is to communicate the problem it’s solving before the work begins, or during it.

Not a preview of the design. That can stay under wraps. But a clear articulation of why the current brand isn’t working, what a new one needs to do, and why this matters now.

This doesn’t require a town hall. It might just be an honest message from leadership that names the problem out loud, before the solution arrives.

The second thing to change is the assumption that leader communication scales. It doesn’t, not reliably.

What works better is identifying brand stewards within departments, people who are trusted locally, understand the work, and can be the go-to resource for their colleagues. Not a title, not a committee: a relationship. Someone who knows where to point people to find resources or how to advocate for the new brand when a faculty or staff member is using an old slide deck template.

The third is resource design. If the path of least resistance is using the old template saved to someone’s desktop, you have a resource design problem.

New templates need to be easier to find, easier to use, and easier to understand than whatever they replaced. Not theoretically easier, but actually easier, tested with the people who will use them, not the people who designed them.

This is a brand practitioner’s problem to solve

None of this is the design team’s fault. At UR, as at most institutions, the design team did what design teams do: they built the system. The gap isn’t in the work; it’s in the organizational infrastructure around the work, and that usually isn’t considered part of the brief.

But maybe it should be. Because if you believe — as this publication does, as most serious brand practitioners do — that a brand is a strategic system and not just a visual one, then delivering the guidelines and stepping back isn’t finishing the job. It’s stopping just before the hardest part.

The hardest part is landing it. Getting an organization to understand what changed and why, to believe the change was worth making, and to actually behave differently as a result. That’s not a communications team problem. It’s not an HR problem. It’s a brand problem, and brand practitioners who want to be taken seriously as strategists need to own it.

The proof of a successful rebrand isn’t a beautiful system. It’s whether the organization can actually live inside it. And right now, too many organizations can’t. Not because the design failed, but because no one treated internal adoption as part of the work.

The old letterhead on the desktop is still there. That’s the real brief.