You Should Always Do User Testing Before Release (yeah yeah...)
How many times have you heard people on the inside of forward-thinking companies telling you how important it is to do user testing before release - and then saying that they didn't do it the last time, but nevertheless, it's REALLY important...?
I was at the Future of Web Apps conference last week and listening to Daniel Burka (of Digg and Pownce fame) who, among many other good tips, made this recommendation closely followed by this admission.
It really winds me up, I have to say, as everyone knows how good it would be to do some cheap, easy, user testing but nobody seems to do it. In my meagre experience, once you manage to build in the time (2 days) and the budget (£100) to do it, the testing itself is very easy and valuable.
The tough part is getting stressed, overworked stakeholders on an overbudget, late project to build in this tiny bit of time.
Why? We haven't got the arguments to be convincing enough at the time they need to be. Everyone pays lipservice, but very few have changed the way they work.
I was at the Future of Web Apps conference last week and listening to Daniel Burka (of Digg and Pownce fame) who, among many other good tips, made this recommendation closely followed by this admission.
It really winds me up, I have to say, as everyone knows how good it would be to do some cheap, easy, user testing but nobody seems to do it. In my meagre experience, once you manage to build in the time (2 days) and the budget (£100) to do it, the testing itself is very easy and valuable.
The tough part is getting stressed, overworked stakeholders on an overbudget, late project to build in this tiny bit of time.
Why? We haven't got the arguments to be convincing enough at the time they need to be. Everyone pays lipservice, but very few have changed the way they work.
0 Comments :
Post a Comment
Links to this post :
Create a Link
<< Home