1 / 33

iSchool Redesign: Phase I

iSchool Redesign: Phase I. Presented by: Beatriz Collazo Stephanie Handy Emily Lawrence Courtney Smith Sayali Patwardhan. Goals. Study the UMD iSchool Web site in detail ( http://www.ischool.umd.edu ) Conduct Phase I of the research

roman
Download Presentation

iSchool Redesign: Phase I

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. iSchool Redesign: Phase I Presented by: Beatriz Collazo Stephanie Handy Emily Lawrence Courtney Smith SayaliPatwardhan

  2. Goals • Study the UMD iSchool Web site in detail (http://www.ischool.umd.edu) • Conduct Phase I of the research • Suggest improvements and modifications to the existing website design

  3. Deliverables • Site Map • Survey • Faculty/Staff Interviews • Card Sort • Site Evaluation • Additional Resources • Wiki • Further Suggestions http://www.freedigitalphotos.net/images/view_photog.php?photogid=1962

  4. Process • Met with Michelle Dozier from NARA • Created initial project plan: • Web Statistics • Site Map • Survey • Card Sort • Amended project plan to include: • Wiki • Faculty & Staff interviews • Resource list • iSchool Evaluation & Comparison http://www.freedigitalphotos.net/images/view_photog.php?photogid=1152

  5. Site Map • No site map left by previous Webmaster • No way to properly ensure lack of unreachable pages. • Divided website’s main sections among group members to be mapped out. • Within the map of each section, all links were noted, along with page hierarchies. • Completed site map allowed for observation of duplications, loops or logical inconsistencies in the site structure (for example, that the student intranet is located within the Faculty & Staff section of the website). • Site map later used as the basis for the card sort.

  6. Site Map (contd)Site Map Excerpt Prospective Students Masters Program Tuition and Fees Graduate Students (takes you to Office of Bursar site) Advance to Candidacy (takes you to Office of Bursar site) Student Organizations National Organizations State Organizations Student Organizations State Organizations (actually same page as National Organization) State Organizations Student Organizations New Student Checklist (“Jump to” links, but on same page)

  7. SurveyWhy do one? • No use statistics available • “An opportunity to learn many types of information” about a site’s users (usability.gov): • Who are they? • How do they use the site? • Are they satisfied with the site?

  8. SurveyWhat was ours like? • SurveyMonkey – used iSchool site license • http://www.surveymonkey.com/s/iSchoolwebsite • Sent to student and faculty/staff listservs on Aug. 2 (closed Aug. 8) • 15 questions • Gathered some data that would otherwise be retrieved via web analytics • A mix of open-ended and closed questions

  9. SurveyWho are the users? • 109 respondents • 78% were 20-39 years old • All respondents completed college; 58% obtained a graduate degree

  10. SurveyHow are people using the site? • 57% arrive at the iSchool website by navigating to the main page • 33% get there via search engine

  11. SurveyAre the users satisfied? • What do you like about the site? • “Interface is clean and reflects the vibrancy of the school.” • “The information is usually there somewhere.” • “Pretty much nothing.” • What do you dislike about the site? • “The navigation is horrible.” • “Search could definitely be better.” • “Information is outdated.”

  12. SurveyAre the users satisfied? • 30% felt the site positively affected their impression of the iSchool • 29% felt the site negatively affected their impression of the ischool • 24% felt that other users would have an easy time using the site • 40% felt that other users would have a difficult time using the site

  13. SurveyRecommendations • Use Google Analytics to obtain user info, but also… • Include an abbreviated version of the survey on the new site • Increase # of career planning/prep resources • Add instructor bios/more faculty info • Improve the search function

  14. SurveyRecommendations • Fix or remove broken links • Add more info about Shady Grove programs • Cultivate a more active social media presence • Include a site map and improve site organization/navigation

  15. Faculty/Staff Feedback • E-mailed interview Questions to 21 Faculty and Staff Members of the iSchool • Several completed online survey • Dean Preece showed special interest

  16. 1 Faculty Member Responded! • Mostly uses site for Course Descriptions, Course Schedules, Syllabi • Feels these sections meet needs • Only uses Staff & Faculty section to get to Practicum List (problematic) • Info needed as new faculty was spread between iSchool and UMD web sites • Able to locate info only with effort and experience Thanks to Dr. Kurtz!

  17. Extra Feedback • Dr. Yates sent a report he created based on usability analysis done by his LBSC 690 spring 2011 class • Full report located on our Wiki site • Highlights positive feedback • Includes concerns and critiques relating to: • Content • Confusing Classification of Content • Inconsistent or Poor Navigation • Miscellaneous Other Critiques

  18. Card Sort • Due to time constraints, began preliminary card sort before survey completion. • Initial sorting completed individually. • New hierarchical organization • Any pages/sections to be cut were noted for later discussion • Further suggestions (renaming of pages, formatting, etc.) • Adjustments made as a group based on tabulated survey results. • Submitting a recommendation of changes to the site map for the next group to expound upon

  19. Card Sort (contd)Notable Suggestions • Include Tuition and Fees Information for all Program • Make Student Intranet its own Menu Heading • Fix All Broken Links • Rename Student Affairs to Current Students • Update Alumni Profiles to include Ph.D. and female students • Standardize components of Programs • Field Study should be prominently displayed on home page 23

  20. Site Evaluation • Web Design Criteria • Checklist • Usability Study • User Preference • Keep for future use

  21. iSchool Comparison Compared leading iSchools Temperature Check Tool for later reference Key: Use this key to understand the categories.

  22. iSchool Comparison

  23. Additional Resources • For the next group to consult and use • Comprehensive List located on the Wiki • Includes: • 9 Monographs • 5 Scholarly Articles • 6 Web sites

  24. iSchool Redesign Wiki http://ischoolredesign.wikispaces.com/iSchool+Redesign+Welcome

  25. Challenges • Process was fraught with problems: • Limited Time/Summer • To IRB or not to IRB? • Survey Monkey Access limited • Listserv Delay • Our client was not our NARA mentor • No Webmaster • No Web usage statistics http://www.freedigitalphotos.net/images/view_photog.php?photogid=721

  26. Solutions • Reached out about IRB • Forged ahead and gained access to Survey Monkey with a backup plan (unusual risk management challenge) • Added Web analytics to list of suggestions • Created questions for Faculty & Staff interviews • Reached out to the Dean • Sent survey http://www.freedigitalphotos.net/images/view_photog.php?photogid=721

  27. Recommendations • Search Engine • Menu Consistency • Decrease White-Space • 508 Compliance • Centralize Current Student Content • Usability comparison with UMD iSchool site and other top scoring iSchool sites http://www.freedigitalphotos.net/images/view_photog.php?photogid=809

  28. Next Steps • Interview Faculty and Staff • Comparative usability study • Revisit Card Sort • Initiate dialogue and collaborate with new webmaster

  29. Questions and Feedback?

More Related