When to rename vs when to reposition

Rebrand vs rename is a diagnostic question, not a creative default. Our failure case portfolio shows teams reaching for a new word when the real problem is broken meaning, and teams refreshing positioning while the name itself has become a liability. The expensive error is treating both moves as the same project.

When does repositioning solve the problem?

Repositioning repairs what the name stands for: audience, promise, category frame, or voice. Gap's 2010 logo disaster is the cautionary mirror. Leadership tried to signal modernization with a mark swap while product relevance and narrative stagnation went unaddressed. The public rejected the logo in six days; the lesson in our Failure Files is emotional equity, not file format.

Reposition when recognition is intact but meaning drifted: wrong tier signal, outdated category language, merged entities still telling two stories, or a offer change the market has not heard yet.

When is a rename actually required?

Rename when the word itself blocks the business: legal conflict, unsearchable string, unpronounceable globally, toxic association, or a name that promises a category you no longer serve. Repositioning cannot fix a homophone that reads as a slur in your primary market.

Renames also make sense after acquisitions when one equity must survive and the other carries confusion, or when a founder's personal name caps enterprise scale and the firm has outgrown it.

What should you fix first?

Stress-test before print: pronunciation, search, trademark class, competitive confusion. I outlined those screens in how to stress-test a name before you print anything.