This wasn't A/B testing. This was fixing UI mistakes based on UX analysis. There... | Hacker News

Hacker News new | past | comments | ask | show | jobs | submit

login

njharman on Nov 2, 2010 | parent | context | favorite | on: Expedia on how one extra data field can cost $12m

This wasn't A/B testing. This was fixing UI mistakes based on UX analysis. There was no 'B'. They weren't comparing A and B.

samd on Nov 2, 2010 | [–]

UX analysis and A/B testing go hand in hand. There'd be no way to know that the Company field was a UI mistake if it had not been tested.

CapitalistCartr on Nov 2, 2010 | [–]

In this case, the A/B testing would have been with that field and without.

pavel_lishin on Nov 2, 2010 | [–]

How would you know which fields to use?

Consider applying for YC's Spring batch! Applications are open till Feb 11.
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact