• Save
PSEWEB 2011: Plan it and they will come
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

PSEWEB 2011: Plan it and they will come

on

  • 430 views

Plan it and they will come: Lessons learned from planning a post-secondary web redesign

Plan it and they will come: Lessons learned from planning a post-secondary web redesign

Presentation given at the 2011 PSWEB conference held in Toronto, Ontario. http://pseweb.ca/

Statistics

Views

Total Views
430
Views on SlideShare
430
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

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
  • [ CHRIS ]
  • The answer to all of these questions for our institution, the Justice Institute of British Columbia, or JIBC as we’re known, was unfortunately a resounding yes. If that’s also the answer for your institution, you may be a prime candidate for a web redesign. But this isn’t a session about how to determine whether you need to do a redesign, or what elements to include in a redesigned website - it’s about how to plan the project once you’ve bitten the bullet. Planning is key because web redesigns can easily become megaprojects that you lose control of. When that happens, forget about on time and on budget. Sound planning steps you take early in the project will pay dividends later when you’re in crunch time. Planning isn’t sexy, but it will reduce the pain in a redesign. And believe me, there will be a lot of pain.
  • I’ll hand it over to Lori to talk about Our School.
  • [ LORI ]
  • Process & design - driven by vendor
  • [ FLIP TO LIVE WEBSITE HOMEPAGE ]
  • [ CHRIS ]
  • So you’ve decided to go the redesign route, which may or may not include changing your CMS. Where do you start? In our case, we had a head start: Before I joined JIBC in late 2009, an extensive evaluation of the website had already been completed by a consultant. The evaluation, including interviews with students, staff and other stakeholders, was informally seen by senior management as a valid case for redesigning the site. But no funding had been committed and no plan was in place to make it happen. What next?
  • Honest assess: What support do you have in senior management and in other parts of the organization - who are your key supporters and who needs to be brought onside What financial and human resources are available – what are you up against: our organization was going through some tough financial times, so we knew our business case needed to be compelling What gaps will you need to fill in your core team: Web Editor to rewrite content was key hire What’s the skill set of staff, which will point to what kind of CMS would be most appropriate for them Whether you need to build bridges with IT – we had a good relationship, and knew they were technology agnostic
  • Then you’re ready to prepare a business case, which can be boiled down to this: Where are we: results of evaluation – it helps to have done one Where can we go: easy - show other sites so they can visualize the possibilities Why should we go there: it’s a marketing imperative, it’s about the reputation of our school, and it’s about service to our students How can we get there: the seeds of a plan How long will it take: not too long, not too short How much will it cost: less than the consultant said
  • After our business case was approved, there was more writing to do: a Project Charter Strategy Deliverables Tasks and timeline Defining what’s in scope and, perhaps more important, what’s not in scope. Budget: an estimate Identifying project risks and having a plan for mitigating them Roles & responsibilities of the team It’s not just a document to put away after it’s done – if it’s thorough and relevant, you’ll refer to it constantly throughout the project. Important to have senior management to sign off on this – in our case, it went right to the top, with the President signing off Your organization may have a template. If you would like me to send you the template we used - email me at the address that appears at the end of the presentation or talk to me after the session.
  • To be honest we struggled with coming up with an accurate timeline. But this gives an idea of how it worked in the end. [Briefly touch on all phases] So it’s not a clean and tidy process where one phase ends and another starts: there’s a lot of overlap And it’s not cut and dry. While most of the design work happened in the first half, the design vendor stayed involved right to the end, reviewing how their design was implemented.
  • [ CHRIS ]
  • One of the first things we did in this process was gather and prioritize a detailed list of draft requirements, which was included right in the RFP we conducted to find a web vendor and select a CMS. Advantage: made it crystal clear what was in scope for the CMS & website. Disadvantage: it could have hemmed us in. But that didn’t turn out to be a bad thing – forced us to focus on what’s essential. [ Flip to the actual requirements document in Word]
  • Research: Proprietary or open source, vendors for both Scope: Our CMS needed to talk to somewhat difficult to work with SIS: Training Partner Process: Ensure the same info is available to all proponents. If there are questions about the RFP, issue amendments with the questions and answers. To make it fair, don’t just tell individual proponents. Decide if you want to invite specific vendors to respond, in addition to public posting of RFP If you have decided to not reveal the project’s budget, for example, stick to that no matter how much proponents pressure you, and they will. Decisions like that are your prerogative. Separate web & design RFPs - web firms aren't necessarily the best choices for design, and vice versa.
  • Vendors will tell you that the CMS they’re aligned with perfectly matches your requirements, but dig deeper Customization could be huge - there's no such thing as off-the-shelf – and that’s certainly true with Drupal, which required a fair bit of customization So how do you know? Get a look at it from as many angles as possible (four white bullets) Vendors: ultimately have to assess whether you think they will put up with you and give you that extra level of support and service that will make a huge difference in the project
  • [ LORI ]
  • A true partnership, but clear who the lead dept. was and who the project lead was approvals from executive & senior management worked as a team with student services & technology services (IT) various working groups and committees our hands-on people were local admins and content editors uber admin is our webmaster
  • Give & take relationship with vendors. e.g. requirements - didn’t deliver on every single one But went well beyond call of duty in many other ways (program & course search/online registration, and something as simple as accordions)
  • key to the success of website – heart of the student experience real team approach
  • our solution to get input and buy-in on the project
  • [ LORI ]
  • various means of dealing with content
  • used extensively during project free, easy to use and to manipulate content and levels able to share ‘view only’ or edit access glitchy
  • distributed model, differing skill levels Institute content written to get our messages across (who we are, etc) defined Drupal roles & levels of access (no green text!)
  • Created levels of access and permissions
  • [ CHRIS ] Overall, staff gave us good feedback on how the project went, and that was because of communication - they felt like they were in the loop. So communication is key.
  • [Go through the different tactics] Communicate clearly to internal stakeholders how much extra time will be involved for them in delivering their part of the website. They need to understand that they will need to adjust their schedules and at crunch time, it will be all hands on deck. Be sure to acknowledge team members for their contributions during the project and after the launch.
  • Abandoned Basecamp – too many places to communicate in can cause info overload – better to keep it simple Weekly conference call kept issues on everyone’s radar Occasional face to face was helpful in working with vendors
  • Make sure your vendor has a solid issues management platform - you’ll be living in there. We used Lighthouse.
  • It’s free and easy to do.
  • [ LORI + CHRIS ]
  • [ LORI ]
  • [ CHRIS ] Program and course search/online registration scope change and missing times from course pages Meant 2 more months to the project, but well worth it
  • [ LORI ] Sometimes you drop the ball. Own up, take quick and decisive action, and move on.
  • [ CHRIS ] Taking the heat (HTML) Unexpected issues/budget reserves: (no course times) Showing up late (my online courses)
  • Participating in web analytics project to track key metrics, spearheaded by Karine Joly, the woman behind Higher Ed Experts and collegewebeditor.com. Site has only been live for three months: high traffic, compared to what we’ve seen in the past, in first two months. Bit of a dip in April, but still about double where we were a year before. So we know there are a lot of eyeballs on our site. Now we’re doing a post-launch evaluation to see if they’re looking in the right places. There will be more usability testing, measurement, and tweaking. The fun never stops. But this presentation has to stop. On that note …
  • [ LORI ]
  • [ CHRIS ] If you ask a question you'll get some JIBC chocolate

PSEWEB 2011: Plan it and they will come Presentation Transcript

  • 1. Plan it and they will come Lessons learned from planning a post-secondary web redesign Chris Wong & Lori Munro Justice Institute of British Columbia
  • 2.
    • Are navigation and search on your website so bad that students call to ask for help… and staff trying to help them get lost too?
  • 3. Do staff at your institution avoid linking prospective students to your website when marketing & recruiting?
  • 4. Do you cringe every time your homepage comes up, due to its antiquated design?
    •  
    •  
    •  
    •  
    •  
    •  
    •  
  • 5. Today’s Session
    • Our School
    • The Overall Plan
    • RFP Process & Choosing Vendors
    • Partnerships
    • The Content
    • Communication
    • Lessons Learned
  • 6. Our School
    •  
  • 7. Justice Institute of British Columbia
    • Founded in 1978 by provincial government
    • Originally training facility for police, correctional officers, etc.
    • Has evolved into degree-granting public post-secondary institution
    • Diverse programs: from fire to conflict resolution
    • 30,000 students annually - but low FTEs due to short course length
  • 8. 2007: launch of previous website 
    •  
  • 9. Previous Website Redesign
    • Final design chosen by staff vote
    • Chosen CMS was Macromedia Contribute
      • Pros: low cost
      • Cons: wasn’t Dreamweaver, staff hated it
  • 10. January 2010: began website redesign process
    • Key goals:
      • Improve usability - especially navigation & search
      • Improve course/program search & online registration process
      • Develop engaging content - web friendly, consistent in tone
      • Get strategic with messaging
      • Change to a user-friendly, cost-effective CMS that works for JIBC
  • 11. February 2011: Site Launch
      • Consistent navigation elements present on each page (main, utility, breadcrumbs, search box); navigation for Schools added
      • Course/program search and registration completely redesigned; microcopy revised for every step
      • All content rewritten
      • Success Stories – in-depth features & striking images tell story of who we are/what we do
      • Drupal as our CMS
  • 12. The Overall Plan
  • 13.           Where Do You Start?          
  • 14. Assess Yourself!
    • What are your organizational assets and liabilities?
  • 15. Organizational Assessment
    • Honestly assess:
      • Senior management support
      • Buy-in throughout organization
      • Available resources
      • Skill-set of core team
      • Technical skills & web savvy of department staff who will be editing the site
      • Relationship with IT & their stance on key issues like open source vs. proprietary
  • 16. Business Case
    • Where are we?
    • Where can we go?
    • Why should we go there?
    • How can we get there?
    • How long will it take?
    • How much will it cost?
  • 17. Project Charter
    • Key elements:
      • Strategy: Goals, objectives & business outcomes
      • Deliverables
      • Tasks & Timeline
      • Scope definition
      • Budget
      • Risk management
      • Roles & responsibilities
    • Sign-off on Charter by senior management
  • 18. Timeline
  • 19. RFP Process & Choosing Vendors
  • 20. First step: Requirements, requirements, requirements
    • Gather requirements
    • Is it going to be a Rolls Royce or Honda Fit or something in between? 
  • 21. RFP Groundwork & Process
    • Research and know the market
    • Scope: what systems will need to interact with your CMS
    • Create an airtight process: be rigorous about making the same info available to all 
    • Separate RFPs for web development and design
  • 22. Making a Decision
    • Make a joint decision with IT
    • How user-friendly is the CMS? How closely does it match requirements - how much customization?
      • Get a non-technical demo for core team
      • Have users test drive it
      • Get a technical demo for IT
      • Require CMS be installed on servers for internal testing
    • Vendors: fit is important - working style, organizational knowledge, location
  • 23.
    • Partnerships
    •  
    •  
    •  
    •  
  • 24. Roles & Responsibilities
  • 25. Partnerships
    • With multiple vendors
    • With IT, as early as the RFP stage
    • With Student Services
    + +
  • 26. Program & Course Search
    • Multiple meetings with IT and Student Services
    • Considerations included
      • Consistency of info given to students
      • Government reporting requirements
      • Integration of website & student data
      • microcopy
    • Ensured we considered marketing + students + technology
  • 27. Web Steering Committee
    • Challenge: getting buy-in from 15 departments represented on website
    • Solution: give them a seat at committee table
    • Recruited members through senior management
    • Key contribution: participation in discovery sessions that helped shape strategy
    • Managed input
  • 28. The Content
  • 29. Content Plan
    • ‘ Writing for the web’ seminars (no cost to staff)
    • Content templates
    • Worked directly with each area on their navigation to ensure consistency of structure
      • Also meant we were aware of all content going on the site
  • 30. Navigation
    • WriteMaps: free tool for creating navigation
  • 31. Content Management
    • Over 50 hands-on contributors in over 15 departments
    • Past experiences informed choices
      • Roles & permissions
      • Limited formatting options
      • No access to html
  • 32. Drupal Content Roles
  • 33.
    •  
    •  
    •   Communication
    •  
    •  
    •  
    •  
    •  
    •  
    •  
    •  
  • 34. Internal Communication
    • Web Steering Committee
    • Senior Management
    • Core team
    • Working groups
    • Staff e-newsletter
    • Blog
    • Emails to Local Admins
    • Launch events
  • 35. External Communication
    • BaseCamp
    • Weekly conference calls with vendors
    • Face-to-face meetings
    • Issues management system
    • Blog
    • Usability testing
  • 36. Issues Management 
  • 37. Blog 
    •  
  • 38. Usability Testing
    • Tested pre-launch
      • Representative students
      • Common tasks - hands-on, think aloud
      • Two Communications & Marketing staff - one to guide, one to observe
    • Listen to what they say, watch what they do
    • Done cheaply: only cost was honorarium for students & lunch for staff, payoff was identifying small but important tweaks
  • 39. Lessons Learned
    •  
  • 40. Lesson Learned: Timing
    • Training staff on CMS while still customizing CMS
      • Painful but essential
      • Highlighted key issues while developer could still resolve them
  • 41. Lesson Learned: Scope Change
    • Assess the need - determine if worth it
  • 42. Lesson Learned: Communication
    • Creating myJIBC altered access to online courses
    • Had to add “My Online Courses” to navigation the morning of site launch
  • 43. A Few More Lessons Learned
    • Take the heat, be flexible, but stick to your plan
    • Unexpected issues WILL happen – be ready
    • Keep some reserves in your budget for unexpected issues
    • Don't show up late the morning after the launch
    • As workload & issues mount, stay calm - keep your eyes on the prize
  • 44. Analytics Website Traffic: Number of Visits
  • 45. Feedback
    • “ A few years ago I sent you a note to you lamenting the “new” website. At that time, I was not a fan due to the fact that it was so tough to tunnel down into the individual courses and then tunnel down to check schedules. This is certainly not the case any longer. I am thoroughly impressed with the functionality and the look of the new website.”
  • 46.  
    • Questions?
  • 47. Contact Us
    • Chris Wong [email_address]
    • Lori Munro  lmunro@jibc.ca
    • Website   www.jibc.ca
    •  
    • Facebook   www.facebook.com/justiceinstitute
    • Twitter  twitter.com/JIBCnews