• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Case study: NYU - 	NYU.edu: Reimagining the User Experience
 

Case study: NYU - NYU.edu: Reimagining the User Experience

on

  • 1,731 views

 

Statistics

Views

Total Views
1,731
Views on SlideShare
1,729
Embed Views
2

Actions

Likes
1
Downloads
0
Comments
0

1 Embed 2

http://www.slideshare.net 2

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Case study: NYU - 	NYU.edu: Reimagining the User Experience Case study: NYU - NYU.edu: Reimagining the User Experience Presentation Transcript

    • NYU.edu: Re-imagining the Eric Bross User Experience New York University
    • Introduction
    • New York University • Largest private, non-profit university in the United States • 18 schools and colleges in 6 major centers within NYC • 50,000+ students • 4,000 full-time faculty & 10,000 full-time staff • 50+ international programs with full academic centers in 12 countries • Sister institution opening in Abu Dhabi in 2010
    • The New York University Landscape
    • The Wild West of NYU Web Sites • 100+ decentralized Administrative Unit Web sites • No enterprise-level CMS -- require technical knowledge to maintain sites • No official Web standards: technical, content, or identity • No consistent coding standards for best search engine optimization • Inconsistently updated content - many NOT updated after initial launch • No official NYU branding until Summer of 2008
    • The NYU Web Master • Few dedicated Web professionals • Most charged with site maintenance as an “other duty as assigned” • Many Web masters are students (Grad or Undergrad) contracted for short periods of time • ...or units contract time with the Office of Web Communications • Independent, recovery-based design & production shop of 9 FTEs
    • Content Ownership & Generation • Content is owned and generated by each unit within the university • No centralized editorial group for public-facing content • Core NYU.edu content has ad hoc management by: • WebComm in conjunction with: • Public Affairs • Advertising & Publications
    • New Directions
    • Redesign • About a 1+ years ago, two conversations about an NYU.edu redesign began: • WebComm • Provost’s Office • New aesthetic look and feel, as well as information organization • More established standards to ensure a more consistent user experience • Need tools to remove technical bottle-necks
    • Governance • In addition to the redesign charge, University Leadership Team bestowed governance: • WebComm through a Web Advisory Group • Web standards for a better and common user experience • Purview of all public-facing Web sites
    • Topically-based Site • NYU is attempting to ‘reimagine’ content so it is more easily found by key audiences • Topical organization of information • ex. “Registering and Paying for Classes” instead of “Registrar” & “Bursar” home A B C D
    • Topically-based Site • NYU is attempting to ‘reimagine’ content so it is more easily found by key audiences • Topical organization of information • ex. “Registering and Paying for Classes” instead of “Registrar” & “Bursar” home B D D A C
    • Current NYU.edu design
    • New NYU.edu design
    • Day’s CQ 5
    • Learning Curves • Information Architecture • Re-educating NYU Web masters • Technical • Getting up to speed on Java-based programming, JCRs & Sling • Design • Putting our skills to the enterprise-level test • CMS User • Culture change: reducing tech fears and gaining more content authors
    • Challenges • Documentation • Have seen improvement • Permissions • Changes from CQ 4 to CQ 5 • DAM features/tools • Excited to see upgraded core features in future releases • Reduced Reference Paragraph functionality • Formally requested resurrection of functionality from CQ 4 back to CQ 5
    • Advantages • Ease of use for NYU CMS Users • “Freedom within the Framework(s)” • Reference Paragraph • News at NYU • leveraging CQ Blog tools and data storage schema • iCal Feed Importer
    • Future Plans
    • Future Plans • Calendar with RSVP • Merging two university services into one • Leverage CQ’s, Day-supported tools • Portal environment - Personalized NYU.edu • “Academic Networking” • Social collaboration tools customized for the academic setting • Use of connectors to external social networking sites
    • Thank you. Questions?