Web Content Migration - Regis University 5-7 year old site - 2 years to plan; 10 weeks to build Nav = confusing 7,000+ pages (duplicated and outdated) 1,000 Undergrad - 150+ editors - operating under silo (just like us) No goals or strategy No the “Regis” Story ITS Owned; kept it functioning New Architecture/Focus New CMS Platform (error prone proprietary) - SiteCore New Design and marketing/content strategies Hired CMO after web project was started Accountability (university asset; marketing ownership) New governance Project Teams 3 Admissions Deans, CIO, communications director Wrote request for proposal, chose vendor Chose and purchased CMS Guided discovery, strategy and creative processes Approved new architecture and design Web Advisory Committee (did not serve much; obligation to include) 40-50 mid-level managers, faculty and student Presentation and Q&A Web Marketing Team Accountable for build, strategy and branding Built site in CMS and migrated content Evolve content, design, strategy and function Partner with ITS Web analytics Governance Editor training Assist with faculty/staff/student pages Content Owner Meetings Need content updated? What it needs to say? What forms do you need Structure Let’s talk strategy Content Inventory and Mapping Development of Image and PDF library (avoiding PDFS) Forms Development Moved to SharePoint… Custom CMS Development Server and software setup Acquitted and integrated 3rd party software Redeveloped custom apps Processes and policies: Content and Layout Testing/implementing features and upgrades Community COMM Editor training/permissions Governance policy Visual/writing style guides Mobile policies Build and Launch Built pages/layouts Plunked (cut/paste) edited and wrote new content Uploaded and placed images Client content reviews app integration testing launch announcement and celebration Lessons: Involve web experts in the entire process, not just the build (group of 5) Insist on detailed costs, timelines and deliverables from vendors Be aware of business referral partnerships ITS was pushing for SharePoint! May not be the best thing! Project went WAY over budget because PM did not know what was being promised Evaluate business need and effectiveness or developing and/or redeveloping custom features Clearly communicate new process and policies to community Educate Leadership on process, milestones and resource requirements Get leadership support, don’t be afraid to name drop Make sure leadership is aware of consequences of change! Insist on client review and sign off on content, document all client communication Client is responsible for the content Determine brand strategy BEFORE you develop the website Clear, consistent voice and look/feel Document details along the way Really mean it when you ask for input and participation Success Earned - Be transparent Set up project site post proposal, status reports, committee members Hold update meetings Make ITS your friends, meet with them and content owners early! One team, same team policy Emphasize partnership and common goals TEDIOUS DOCUMENTATION IS WORTH THE EFFORT Content Inventory Content mapping Detailed Site Map timelines status meetings vendor website Improvement is contagious!!!!! Don’t get burned Expect and plan for time and money shortage Expect one major thing to go wrong Sales pitches vs requirements Stick to your story Communicated causes and effects Squash Rumors Comprise team of people who care Set up team support during overtime head out before burn out celebrate small wins play = stress relief participate All other duties were forgone 10 weeks of web dev only If you build it, will they come? - Grinnell College Goals:
...