The redesign went live and sales dipped.
Was it the design, the season, or the price rise that went out the same week? Nobody can say, so nobody changes anything.
Most teams don't. They launch and hope. We show you how to try changes on real customers before you commit, then teach your team to do it without us.
We have been the client: ten years in house, five agency side · Nine markets across Europe and North America
Was it the design, the season, or the price rise that went out the same week? Nobody can say, so nobody changes anything.
Each new senior hire brings a view of what the site should say. Each view is reasonable. None of them gets checked.
Compared with what? A report that only covers the weeks after launch cannot tell you what would have happened without it.
Everyone has a list. The list gets settled by whoever is most senior or most persuasive, not by what customers actually do.
Nobody here is doing anything wrong. This is how decisions get made when there is no way to check them.
There is a way to check
Half your visitors see what is currently there. Half see the change. After a few weeks you keep whichever did better, and you know it was the change that did it, not the weather or the price rise.
This is called experimentation, or A/B testing. Large online businesses do it every week. It works for smaller ones too, with one honest condition: you need enough customers to see a difference.
A test is only as good as the research behind it, the design in it, the build and the numbers that judge it. We cover all four, bringing in specialists when the work needs them, and teach your team each one as we go.
Talk to customers and watch them use your site, so you test what is actually getting in their way.
Design the changes worth testing, and finish the ones worth keeping so they are ready to ship.
Set up tracking you can trust, then turn the numbers into decisions rather than another report.
Build the tests ourselves, so they do not sit in a queue behind your product roadmap.
Need one of these on its own? We do that too, on the same terms: your team learns it, then we step back.
Get these right at the beginning and testing becomes part of how your team decides. Get them wrong and it becomes another tool nobody uses.
What matters is how many people buy, book or sign up, not how many visit. With fewer customers you can only spot big differences, which is fine if you test big ideas. The check below tells you in ten seconds.
Eventually, but not first. Testing rarely fails because of the software. It fails because nobody owns it. Decide who will run it, then choose a tool that suits them.
Usually not yet. Give it to someone who already understands the business, and protect two days a week of their time in writing.
The things your leadership already argues about, not what is easiest to change. Your first list is sitting in last quarter's meeting notes.
Sometimes not. Work out what it would cost to run against what it could return before you spend anything else. If the numbers do not add up, the right answer is to wait.
Free · instant · no email needed
Two numbers from your analytics. We will tell you how long you would wait to know whether a change worked, and whether testing is worth it for you yet.
That is a 2.0% conversion rate. Use whatever counts as a sale for you.
Smallest change you could spot in six weeks
11%
A 10% change would take 7 weeks to spot. We never run a test longer than six weeks, so the change has to be bigger.
Test bolder changes: ones you expect to move results by 11% or more.
Half your visitors see each version, with 95% confidence and an 80% chance of spotting a real change. We cap tests at six weeks: run longer and returning visitors start to blur the result. A guide, not a promise.
If your numbers work
Tell us your site and roughly how many orders, bookings or sign ups you get a month. The person who would do the work looks at both, then talks you through what they found in a 30 minute call.
At your traffic you would wait five weeks to detect anything smaller than a ten percent change. Testing is not your next move.
We would rather tell you that now than sell you something that cannot pay back.
When the answer is yes
Four stages, always in this order, with no months attached. We move on when your team is ready for the next one, and we leave when they pass the standard below.
We set everything up and run your first tests while your team watches. The aim is early proof, not teaching.
Named people in your team take pieces of the work. We review everything in the open.
Your team runs it. We sit in and say nothing unless something is wrong. Most of the learning happens here.
We check your team against the standard, write the handover, then we stop. If they are not ready yet, that is our problem to solve, not yours to pay for.
What we expected, how many people saw it, what happened and what was decided. Most tests do not win, so we show the losses too. Sector and journey only. Never the client.
Eight real tests · scroll or swipe for more
We expected fewer, plainer words to get more people started, because the next step would look less complicated.
Decision. The authoring team rolled the new wording out across Europe.
Prices on the deal buttons meant fewer people clicked into deals. So we moved the price into the deal pictures instead, and orders went up.
Decision. Keep the second version. The first test told us where the price belonged.
Bookings were the same with and without it. That is still useful: without the test, someone would have credited the banner for the next good month.
Decision. Try a bolder change rather than run this one longer.
We showed a short prompt only to visitors whose behaviour suggested they were planning a visit. More of them started a booking, and more finished one.
Decision. Keep it, and refine the wording in the next round.
We expected that seeing delivery details earlier would reassure people before they paid. Instead, far fewer of them went on to checkout.
Decision. Stop the test and keep the postcode box below the checkout button.
Big purchases are often paid monthly. We expected that letting people choose how prices are shown would get more of them to add an item to their basket.
Decision. Keep the switch, and keep testing how the two prices are shown.
It looked like an obvious improvement for customers. It cut bookings, and the result was clear enough to act on.
Decision. Drop it. Helpful for customers is not always helpful for bookings.
Fewer fields usually means more completed forms. Here it did not: bookings dipped slightly without the box, so there was no case for removing it.
Decision. Keep the comments box.
For teams already testing
That is rarely a testing problem. Score your programme against the seven bars we hand over against, or ask us for a programme diagnostic to find what is actually wrong. Usually it is ownership.
Running an agency? Same product, delivered with your team under your brand. We work under your brand and we do not approach your clients, during or after.
Who you will work with
We have done this from both sides of the table. Ten years in house, holding the budget and managing the agency. Five years agency side, doing the work.
When a project needs research, design, analytics or development, we bring in specialists we have worked with before, for as long as the work needs them and no longer. There is no bench to keep busy, which is why we can promise to leave.
In house at a motorcycle manufacturer, a builders’ merchant and a premium car brand.
Start here
The person who would do the work reads every message and replies within two working days, with a question rather than a calendar link.
Prefer email? hello@learnedbehaviour.co.uk