Let’s face it - Testing scares stakeholders. After all, testing creates accountability. It removes a lot of padding that you can typically rely on in marketing:
“I didn’t know”, “how could we have known”, “no one could have guessed”
Well, perhaps no one could have guessed, but almost everyone could have tested, if they had thought about it, or knew how ….or dared.
So, we take this piece of human nature into account, and deal with it.
The most typical exampel of all is most likely the company website.
After all, what does your Google Analytics report tell you about what’s right or wrong? Why should you listen to anyone telling you that typically menus should go on the left, and images go on the right? God forbid you should do an eytracking heatmap analysis - to find out that your colorful logo does in fact actually attract the eye more than the 10p black text next to it.
No, really? Fascinating! Now what?
Compare the above happy, safe environment where nothing is really wrong and nothing is really right, to:
Creating version A and version B of your site, then watch a random population of new visitors experience these, each visitor most likely oblivious to the existance of the other version.
Now we find that version B does in fact ceteris paribus generate twice as much revenue as version A.
Let’s say you are the designer/champion of version A. This isn’t a nice, padded environment you are facing. It’s a situation where you are proven brutally wrong.
But, it’s also a situation where we’ve just found out that version B might earn your company enough money to give you a raise next year, and you’ve just been part of something hugely valuable that will help you create much better things next time.
Saying that your version stinks is also perhaps not true, perhaps it was a great result - only B was even better. Perhaps the foundation of your version A, was crucial to coming up with B. Perhaps you shouldn’t be burned at the stake after all?
Ideally, of course, you were the one ushering in this process in the company, so you worked on both versions, always communicating openly to your colleagues that no one can really tell what’s best before it’s tested.
Which is, of course, the truth.