Forecasting Which Assets Survive a Rebrand: A Fame vs. Uniqueness Stress Test

Marketing Academy · Field Work●Brand Strategy

All projects·From: Distinctive Brand Assets

MiniForecast· 30 minutes

Nubank (Nu Holdings)

Objective: Use Fame/Uniqueness thresholds and a real rebrand-backlash precedent to forecast which assets should be excluded from a proposed visual refresh, and estimate the risk of overruling that forecast.

Nubank's leadership team has proposed a full visual refresh for next quarter. You're asked to forecast which existing assets are safe to redesign and which should be protected before the creative brief goes out.

Turn Fame/Uniqueness data into a clear forecast leadership can act on, not just a preference.

Before you start

What you'll need

Free path (everything below is enough to finish)

Google Sheets

FreeLog asset scores and build the forecast/risk table

Free, fast to build a shareable forecast table for a leadership review

The process

2 steps

Step 01 of 02

Stage 2: Test Fame and Uniqueness

The Ehrenberg-Bass benchmark for a genuine competitive moat is Fame above 70% and Uniqueness above 60%; anything below is still being built.

Nubank's purple brand color tests at 81% Fame and 76% Uniqueness in a category study. Its app's rounded-card visual style tests at 45% Fame and 58% Uniqueness. If leadership proposes a full visual refresh next quarter, which asset should you forecast as 'do not touch' and which as 'safe to redesign'?

Google Sheets— Log both assets and their scores in a simple table, then apply the two thresholds.

Procedure

Enter both assets with their Fame and Uniqueness scores in a sheet
Mark each asset PASS or FAIL against the 70%/60% thresholds
Forecast the outcome of touching each asset given its pass/fail status
Write a one-line recommendation for the refresh brief

Sample output

ASSET FORECAST
Purple brand color: Fame 81% PASS, Uniqueness 76% PASS -> PROTECT, do not touch
Rounded-card style: Fame 45% FAIL, Uniqueness 58% FAIL -> safe to redesign, still being built

RECOMMENDATION: Refresh brief should explicitly exclude the purple from any color exploration.

Healthy

A refresh brief that names the purple as out-of-scope before any designer starts exploring alternatives.

Unhealthy

Letting 'we're refreshing everything' apply uniformly, putting a proven 81%/76% asset on the table alongside a genuinely weak one.

What this means

Fame and Uniqueness scores, not internal creative fatigue, should decide what's eligible for a redesign.

So what do I do about it?

Symptom	Action	Effort
A rebrand brief doesn't distinguish protected assets from redesign candidates	Attach the Fame/Uniqueness table to the creative brief before work starts	30 min

YouYou can do this yourself, no engineering access required.

Step 02 of 02

Stage 3: Classify and Prioritize

GAP's 2010 logo redesign lasted six days before reversal under consumer backlash, because it changed an asset with decades of accumulated Fame.

If leadership overrules the recommendation and redesigns the purple anyway, what should you forecast happening in the first two weeks post-launch, based on the GAP precedent?

Google Sheets— Add a forecast row to the same sheet estimating likely backlash risk and recovery cost.

Procedure

Note the GAP 2010 timeline as a reference case (redesigned, then reversed within 6 days)
Forecast the likely customer reaction to changing an 81%/76% asset
Estimate the cost of a possible reversal (design hours, PR, re-issued assets) versus the cost of not changing it at all
Write the forecast as a short risk note for leadership

Sample output

FORECAST RISK NOTE
Precedent: GAP 2010 logo change reversed in 6 days after public backlash
Nubank purple: Fame 81%, Uniqueness 76%, well above both protect thresholds
Forecast: High probability of visible backlash within days of launch; reversal cost (design + PR + re-issued cards) likely exceeds the cost of never changing it
RECOMMENDATION: Do not proceed without a separate, dedicated equity-risk review

Healthy

Leadership sees a concrete forecast with a real precedent before greenlighting, not just a designer's opinion.

Unhealthy

Presenting the risk only after the redesign has shipped, when reversal is expensive and public.

What this means

A Protect-bucket asset carries real reversal cost if changed; forecasting that cost before launch is cheaper than discovering it after.

So what do I do about it?

Symptom	Action	Effort
A redesign proposal touches a Protect-bucket asset with no risk forecast attached	Require a documented Fame/Uniqueness risk note before any Protect-bucket asset enters a creative brief	30 min

EitherYou or a developer can handle this, depending on your access.

Final deliverable

A one-page forecast table and risk note recommending which assets are safe to redesign and which should be excluded, with a cited precedent.

See a reference example

Sample output

Adyen, Asset Forecast (excerpt)

Core navy blue: Fame 77%, Uniqueness 65% -> PROTECT
Secondary icon set: Fame 38%, Uniqueness 41% -> safe to redesign

RECOMMENDATION: Exclude navy from Q3 visual refresh scope.

Success criteria

You're done when you can:

Correctly identifies the 81%/76% asset as Protect and excludes it from redesign scope
Cites the GAP 2010 precedent to support the forecast
Risk note quantifies the cost tradeoff, not just 'this is risky'