Web Site Redesign

1. Web Site Redesign Homepage Committee February 2005

2. Kelker, K. & Chung, S. (2005). “If at first you don’t succeed…”: web site redesign at the UNLV Libraries, Library Hi Tech, 23(1), 50-65. Outlines the 2002 redesign of the UNLV Library Website. Focus is not on outcome, rather on the process Process

3. Basic Process • A permanent advisory team was created as a standing committee. • The original goal was to obtain more results from usability testing. • A secondary goal, though no less important, was how to capture and communicate the meaning of the testing to all team members. • And finally, they sought to identify the entire process and use that structure for the basis of the redesign.

4. In an 1999 article, Burdman outlined web production redesign in the private sector as follows : Strategy Design and specification Production Testing Launch Private Sector Process

5. Where to start? • Identify the problem – what are the problems which we see with the current web design (including student testing) • Vision – from an analysis of the testing, what is our vision for the new design • Goal setting – the team needs to establish definite goals and when they will be accomplished to progress forward

6. Strategy • An analysis of the testing data identified three main areas of concern: • Structure of the website – how many clicks, card sort test, etc. • Layout and navigation – new tools perhaps and standardization • Technical specifications – identify standards

7. Process • After looking at the card sorting tests, develop a number of prototypes • Link these prototypes to the Library webpage for student and staff evaluation • Make sure there is time for this phase as it will have a lasting effect on the design

8. Technical processes • The following issues should be considered: • Required elements • Standards – CSS or SSI • Programming – languages, etc • File naming and placement • Directory structure • Connection speeds, load times, and file sizes • Monitor resolutions and browsers

9. Production • In order to ensure all redesign elements are completed, committee should develop aWork Breakdown Structure. • WBS – create the order of production and how the changes relate to one another. • Brainstorming by all committee members.

10. UNLVWBS • Creation of development area • Create new directory structure • Produce document showing location of all pages on current site • Develop a page template from the prototype • Develop written instruction or checklist • Create schedule for completion of each section • Establish method for tracking completion of tasks • Establish method for handling and correcting redirects

11. Master Schedule • A master schedule must be maintained and updated as progress is made on the redesign. • One team member should monitor the progress and keep other members informed. • Encouragement should be given to team members who all have other responsibilities which limit their available time.

12. LAUNCH!! • Identify a launch date. • Make sure there is ample time for editorial review before launch. • Although less imperative, post launch usability testing should be performed to identify any weakness in design.

13. CELEBRATE SUCCESS • As with all lengthy and difficult tasks, it is important to celebrate success!!