Six beliefs, checked
The loop is understood badly in both directions: by readers who think the changes are arbitrary, and by readers who think a change that helps the reader is the point. Six beliefs, each checked against the ten samples, with four false, one partly true and one that holds.
- beliefs checked
- 6
- false
- 4
- partly true
- 1
- true
- 1
Four of the six common beliefs about interface testing are false, one is partly true and one holds. Layouts are not random - they are two versions shown at once, a control at 4.30% and a variant at 5.16%. The data is not anonymous once an account id joins the events. And a change is shipped on the operator's metric, not on the reader's outcome.
The six beliefs
"The layout changes at random." It changes between two versions shown at the same time. The control converts 4.30% of its visitors and the variant 5.16%, and the change is kept if the lift survives its interval - 0.86 point against +/-0.34. Randomness is in the assignment, not in the design.
"The data collected about me is anonymous." It is anonymous until an account id joins it, and on the samples the account field is attached after sign-in to 1,240 events of one session. A session replay of the same events shown to a human is not an anonymous record; it is a recording of a person's screen.
"If a change makes things easier for me it helped me." The same change lifted first deposits by 20.0% relative and raised the mean first-week net loss of the readers it worked on by 11.8%, from 61.20 to 68.40. Easier for the reader and better for the reader are two different claims.
"A small improvement is a small change." A 0.86-point lift on 100,000 monthly visitors is 860 extra first deposits, 34,400.00 of deposits and 29,412.00 of revenue over 90 days. A rate move that reads as trivial is a large number of people as soon as it meets real traffic.
"They test everything, all the time." On the samples 120 changes shipped in a year, but 41 of 120 failed to reproduce, 11 of 24 addressed a cause outside the page and only 3 of 40 records named a guardrail. Something is running constantly; whether it is measuring anything is a separate question.
"The metric is the operator's, not mine." This one holds. The primary metric is the first-deposit rate, and the reader's later outcome is a guardrail at best: the guardrail moved 11.8% against a rule of 5% and the change shipped. The direction of a screen is set by the number it is measured on.
How the six were chosen
Each belief was taken from the way the subject is usually described in public - by readers, by the trade press and by the operators themselves - and each was then tested against one of the desk's ten samples. A belief was marked false when the samples contradicted it outright, partly true when the direction was right and the scale was wrong, and true when the samples supported it as stated.
- Assume a change you notice was measured, and that the measurement was of the operator's number.
- Assume a recording may exist if the privacy notice names analytics at all.
- Use the account-level controls for a limit, because they are the part no experiment is allowed to optimise away.
- Keep your own dates and figures, since they are the only comparable you can hold.
- Ask, in writing, which metric the deposit page is tested against, and keep the reply.