Posting Date: August 12, 2002
Are usability analysts promising too much? (ZDNet Australia) -- "Neither Jakob Nielsen’s or Dr Shiffman’s techniques, by their very nature, are a substitute for rigorous functional testing because they have been developed to provide insight into broad user needs and user behaviour. They can measure the effectiveness with which a website or piece of software fails to support those needs, in terms of the broader conceptual model, information architecture, feedback and error messaging and so on – but that is all."
Thanks Jeff. This is now fixed.
This is the second time the URL has been buggered. Whatcha doin', John?
MadMan, I swear I am doing everthing the same. Before I post, I always do a preview. I really, really, really hope that Movable Type isn't going belly up.
I think, from a business perspective the answer is yes. However it depends on the company in questions.
I have heard many usability firms promise the world with little or no accountability for their actions. I have also heard a smaller but growing number recognize that the average manger is becoming more aware of usability and its benefits and pitfalls - and thus offer a far more pragmatic and realistic solution and service....which I think is are the right steps in the right direction.
One final note, this author is no different to the previous author he talks about...he is promoting his business as well.
This article is far better than the two he references. He gives Dr. Shiffman way too much credit - going out of his way to be politically correct, perhaps?
Many usability professionals frequently label these reasons, “technical” and dismiss them as mere “bugs”.
Is it just me, or is this abrupt transition toward the end of the article confusing? Looks like some very bad editing. Can anyone figure out what he is referring to when he says "reasons"?
Actually I don't think he is being PC, but more supporting the local guy.
I not sure if Ron Zeno is referring to this, but why, at the end, the article is talking about Quality Assurance? Usability professionnal ( maybe ) can promise a usable interface on a properly functionning web site. They should not have to do bug reporting. Do we ask ergonomist to test for the solidity of a chair, even if everyone agree that it won't be confortable if it's broken?
Yes, as Richard points out, the transition I mention is where the author starts discussing QA issues. After contacting the author, I still don't understand the leap to QA, or how it relates to anything other than the author's own business.