The first is the exploratory stage. This is a point, usually very early on, when you’re exploring a number of different avenues and possibilities simultaneously. It’s a creative moment in time when nothing is set and you’re building ideas.
When sketching initial website designs, for example, there are endless possibilities and combinations to process. Using our previous example, you aren’t only deciding where your ‘add to cart’ button should go, you’re simultaneously deciding its size, shape, colour, background colour, and so on. Data is of limited help here. You may have some data on what the best practices are, or what your competitors are doing, but ultimately it’s your own opinion and preferences that make the decision.
We’ve heard it said that those who are data-driven “lose sight of the bigger picture”. Or that the data-driven approach is ineffective because it tries to replace the irreplaceable human instinct. “If people designed websites solely through data,” they protest, “then every website would look identical.”
These are criticisms of attempts to force data into the exploratory stage. Because here the human instinct certainly is irreplaceable. Its individuality is crucial to designing beautiful websites - crucial to designing anything beautiful, for that matter. Using data in design will have you lost in the details because there’s simply too much information to process, too many options to test. To date nothing creates as wonderfully as the human mind, because to date nothing can process so much at the same time. (Whether AI one day catches up is another matter.)
However, once you reach a certain point, the human mind can be a massive hindrance. This is the second stage, the optimisation stage.
You have a website up and running and now you want to make specific tweaks. This stage is about high-level performance boosting. Fine-tuning your e-commerce machine to gain a competitive advantage.
With a foundation already set you can identify individual areas to modify. You already know how to do it - by keeping all factors deliberately the same except one, you generate data that tells you the answer. The key is to know in advance what you’re testing, how you’ll test it, and what the measure of success is. Follow this step-by-step guide and you can’t go wrong:
1) We believe that… Start with a simple premise, for example, “We believe that position A for the ‘add to cart’ button is best for conversion, and that the button should be placed here”. Notice that included in this premise is the consequence of success. If the data proves this premise correct, your decision is already made for you.
2) And to prove it we will… This is the test you will carry out. “And to prove it we will conduct a test for a set period of time between position A and position B”.
3) And measure… You must only measure 1 variable per test. “And measure the page’s conversion rate.”
4) We are right if… This should link back to the first premise so that even before beginning the test you know what the measure of success is. “We are right if the page delivers better conversion rates when the button is in position A.” We already know from the first premise that if this takes place the button moves to A. No questions asked.
Once you have the results, the most important thing is to follow the data. Because in controlled situations such as this the data simply doesn’t lie. There’s no room for opinion. It doesn’t matter what you might think will give a better result because you have scientific proof of what actually gives better results.
This is where the human mind can hinder proceedings. We’ve seen it happen before - tests are delivered but the results don’t match with a boss’ opinion (read: ego). They think they know best and ignore the data, opting for what they prefer. The result? No competitive advantage whatsoever.
At the optimisation stage everyone involved must be prepared to let the data take the lead. If this cannot be agreed upon, don’t waste your time conducting the tests in the first place.