> That's not an A/B test - you already knew a bigger button will result in more click-throughs, you don't need a test to show you that.
You'd be amazed how often "intuitive" things like that often don't actually work.
One product we sell is a specialist piece of software for managing "projects". Let me paint a picture of the interface: you have a list of "projects" which you select then hit a button at the bottom of the page to open the case. Within the project screen there is another button to go to a report page.
As this is about the most common page people use so I trialled installing an "open reports" button directly next to the "open" case button. Hardly anyone clicked on it in our test period (even clients who got an update notification telling them about it) - we actually got one piece of feedback saying it confused them.
I can list 10's of similar examples with our products where a) "intuitive" improvements turned out to be useless and b) split tests caught useless changes quickly.
Users are very fickle :) split tests can be useful.
You'd be amazed how often "intuitive" things like that often don't actually work.
One product we sell is a specialist piece of software for managing "projects". Let me paint a picture of the interface: you have a list of "projects" which you select then hit a button at the bottom of the page to open the case. Within the project screen there is another button to go to a report page.
As this is about the most common page people use so I trialled installing an "open reports" button directly next to the "open" case button. Hardly anyone clicked on it in our test period (even clients who got an update notification telling them about it) - we actually got one piece of feedback saying it confused them.
I can list 10's of similar examples with our products where a) "intuitive" improvements turned out to be useless and b) split tests caught useless changes quickly.
Users are very fickle :) split tests can be useful.
(sure, not an exact science though).