Defining the objectives and scope for a website usability review

Defining the objectives, scope and limitations for any project prior to starting provides a sound base for progress, yet it’s surprising how often this is not done even in big companies. This is the first in a series of 3 articles covering a website usability review. The second covers the actual process, and the final one is an actual review.

Spending time defining the objectives and scope prior to commencing helps ensure that:

  • The issues to be tackled have been correctly identified and that any solutions subsequently proposed will address them
  • The work to be carried out is clearly defined.
  • Upon completion of the work there are a set of requirements against which the work may be tested

I often start with a document containing the following headings:

  1. Overview – a brief statement of why the work is required
  2. Scope – an outline of what will be included and excluded from the work to be undertaken
  3. Objectives – what will be done and  how the will it be judged
  4. Main body of document
  5. Limitations – factors outside of my control but essential for successful delivery
  6. Conclusions – review of the findings of the main body of the document
  7. Appendix – supporting material

There are many possible variations on the structure set out above. What’s important is to communicate clearly the objectives, the findings, the conclusions and any supporting material. The more in depth the document, the more important the overview, scope, objectives and conclusions become as these provide a summary for those people who are not going to read the whole document. Next, the review process.

Tags: