A team that sees its logo every day may tire of it long before customers do. That feeling is understandable, but I do not treat it as a sufficient reason to refresh a brand. First I ask what the identity or communication can no longer accomplish. Is it failing to explain a new offer, creating the wrong expectation, or simply being applied inconsistently?

Put the problem into three separate categories

The first is strategy: has the audience, offer or business model changed? The second is expression: is the direction sound but poorly communicated? The third is execution: is the guidance adequate but interpreted differently across teams? Confusing these can turn a manageable implementation issue into an unnecessary identity project.

Inconsistent website headlines, for example, do not establish that the entire brand voice is wrong. I begin with a consistency audit to locate the problem. Even repetition across several channels does not, by itself, explain its cause.

Describe the reason in observable terms

Instead of “we need to look more modern”, try “people struggle to find our new range under the current category names”. The first invites a debate about taste; the second identifies something that can be investigated. Support enquiries, interviews and content reviews may provide useful evidence.

I distinguish direct observations from team interpretations in the decision record. One customer comment can be a valuable clue without representing the whole audience. Research synthesis helps retain that distinction when individual findings become a broader recommendation.

Identify what should survive

A colour, familiar phrase or long-standing product name may carry recognition. I would not assess that value only through internal preference. Ask what people actually associate with the brand and where confusion occurs. A refresh need not erase everything that came before it.

Then compare possible scopes: repairing the application guidelines, updating visual expression, or reconsidering identity alongside strategy. Record the effect on packaging, websites, asset libraries and team training. The design fee is only one part of the transition cost.

Define success before showing the new look

What problem should the change reduce? Easier product discovery, more accurate understanding and fewer production inconsistencies require different evidence. Specifying the intended improvement before launch makes it easier to evaluate the work after the initial excitement.

A sound refresh decision should explain more than why the new version looks better. It should show which problem is being addressed, what existing value is retained and what the team will do differently tomorrow. If those answers remain unclear, the brief probably needs more work before the identity does.

Test an alternative explanation before committing to a refresh

In a fictional example, visitors contact support because they cannot find a new product range. The team interprets this as “our brand no longer explains what we do”. The same observation could also reflect an unclear category label or its position in the menu. A support enquiry signals a problem; it does not establish that the whole identity needs to change.

First ask: “Can people find the range when the category label and description are clearer?” Change only that area in a limited prototype. Record participant profiles, the task and the versions compared. This does not replace research into how widespread the problem is. It helps investigate whether a smaller intervention could address it.

Close the decision note with three statements:

  • Observed: Which task and version caused difficulty, for how many participants, and in what way.
  • Unresolved: What remains unknown about the relationship to the offer, its expression or its implementation.
  • Next decision: Continue the smaller correction, test another explanation or open a broader strategic investigation.

Hearing one piece of feedback repeated in several meetings does not increase the number of independent observations. Keep the original source and avoid counting copies of the same incident as separate findings. Instead of treating a universal number of comments as sufficient evidence for a refresh, consider the cost of reversing the decision and the consequences of being wrong. State which uncertainties the team accepts before a broad change.

The SBA’s research guidance identifies business-specific buying-experience questions as a use for direct customer research. The prototype and decision note above are original editorial suggestions, not a refresh threshold prescribed by that source.

If the underlying promise needs reconsideration, revisit brand positioning. Connect the scope to the brand communication guide so that an implementation problem does not automatically become a complete identity project.