The Bell Atlantic data are at least a starting point. Organizational Issues Usability testing of web sites presents an interesting organizational problem. Ideally, usability testing first occurs at a functional prototype stage. Here, an interface has been specified and mocked up so that base functionality is in place, although content or data may be missing. This allows testing at a stage where we know enough about what the application is supposed to do to be able to make meaningful design recommendations but where we have not invested too many resources, in case major interface redesign is required.
Web sites are different however.
The usability of a web interface is closely tied to the underlying information. In order to adequately assess the amount of frustration and confusion which will result when a user has to tunnel through numerous links and pages to get one desired piece of information, all those links and pages and all that information must be in place. Thus, as usability professionals, we are in some ways undermining our hard-fought battle for early involvement by telling designers it is best to wait a bit. We must effectively communicate this rationale to ensure that we are not sending mixed signals. Final Thoughts Clearly, significant issues exist regarding usability testing of web sites.