Hey {{first_name}}
It has never been easier to find or generate ideas on what to change on your website.
And it has never been easier to make those changes.
Brilliant.
But also dangerous.
Just because you can change something, it does not mean you should.
Change for change’s sake is bad CRO.
And I think a lot of brands (and agencies) are walking straight into this trap right now.
They have more ideas than ever.
More tools than ever.
More ways to edit, tweak, rewrite, rebuild, refresh and “optimise”.
But the actual reasoning behind the change is often flawed.
Someone thinks the hero section feels dated.
Someone saw a competitor doing something.
Someone wants the product page to look cleaner.
Someone asked ChatGPT for ideas and now the team has 47 things to try.
That is how websites slowly become Frankenstein stores.
A badge from one idea.
A pop-up from another.
A new CTA because someone liked it on a SaaS website.
A homepage section no visitors use.
And before long, the site technically has more “CRO” done.
But performance has not changed.
Or worse, it has declined.
So here is a rule.
Before you implement any new website change, write this down.
The 4-Line CRO Blueprint
Based on.. [The qualitative or quantitative data observation]
If we… [The exact design, copy, or functional change you make]
Then… [The expected user reaction or metric movement]
Because… [The psychological reason or belief driving the change]
And if you cannot write those four lines HONESTLY, leave the page alone.
Because if it ain’t broke, don’t fix it.
And if you think it is broken, prove it.
Here is what a bad version looks like.
Based on.. the fact we think the product page could be better.
If we… redesign the top section.
Then.. conversion rate should improve.
Because.. it will look nicer.
Here is a better version.
Based on.. mobile visitor session recordings showing people scrolling past the first CTA and opening reviews before adding to cart.
If we.. add a short review-backed proof block directly under the product title.
Then… more visitors should get the reassurance they need earlier and add to cart without having to hunt for reviews.
Because… customers need evidence and social proof before they believe the product is worth buying.
Now we have something.
We know what behaviour triggered the idea.
We know exactly what is changing.
We know what we expect the customer to do.
And we know the reason behind it.
The idea now has a backbone.
That is the level of thinking you want.
Specific.
Grounded in data.
Easy for the whole team to understand.
The mistake is believing CRO is about having loads of ideas and making changes.
CRO is knowing which ideas deserve to be tested, and when.
Because every change has a cost.
Even small ones.
A new section can distract people.
A new message can create doubt.
A new layout can hide something that was already working.
A new “better” CTA can reduce clarity.
A new design can look cool but make the customer suffer more decision fatigue.
Sometimes the best CRO decision is doing nothing.
Protect the thing that already works.
Leave the button alone.
Leave the headline alone.
Leave the product page alone.
Spend the time finding the actual friction instead of decorating around it.
So before you make your next website change, ask your team to fill this in:
Based on…
If we…
Then…
Because…
If it is vague, park the idea.
If the observation is missing, go find the data.
If the change is unclear, tighten it.
If the expected result is wishy-washy, you have not thought hard enough yet.
And if the reason is just “it looks better”, please step away from the theme editor.
Your website does not need more random changes.
It needs better decisions.
Once you have written the 4-Line CRO Blueprint, score the idea using the PECTI framework so you know what to prioritise next:
Chat soon,
Peter
|
|
||||
|
|||||
