how not to introduce a project change: lesson learned from NBA basketball experience

6 Dec 2006 - 9:31am
832 reads
David VanEsselstyn

What if you introduced a design change in a product, heard immediate
complaints from established users, and then users' fingers started bleeding
and hurting so badly they had to tape them a few months into the adoption?

A lesson on how not to test and evaluate user experience (the testing is
especially laughable...) comes from the National Basketball Association:

--David VanEsselstyn
--Wireless Generation
--Senior Usability Analyst

Syndicate content Get the feed