Operation integration

17
Hollyce Balentine Karen Zelt HighEdWeb 2013 #PST22

description

It started with nine free-range departmental websites with disparate content and next to no order. We charged into a full-scale redesign with the end goal of a comprehensive service-focused, up-to-date and user-friendly resource. These are the steps we followed and the challenges we encountered.

Transcript of Operation integration

Page 1: Operation integration

Hollyce Balentine

Karen Zelt

HighEdWeb 2013

#PST22

Page 2: Operation integration

1. Plan! Plan! Plan!

#PST22

Determine your desired launch date and work backwards. Do it

skimp on steps and stick to your guns.

Page 3: Operation integration

2. Wrangle content

We lassoed everything from grounds services to campus telephones to interior design.

#PST22

DETOURS

VEHICLE RENTAL

PAINTING

Page 4: Operation integration

3. Card sort

Write topics on cards or sticky notes. Disregard old site structure; group the cards logically.

#PST22

Page 5: Operation integration

4. Audit

Perform a ROT analysis on every page: Is this Relevant? Outdated? Trivial? Fix it!

How do we stay the course in the face of opposition? Audits (along with analytics) are your greatest defenses. Establish that optimal user/customer experience is the focus. Does this change make navigating easier for the

#PST22

Page 6: Operation integration

5. Examine analytics

Learn what visitors search for and, what pages are most visited, etc.

#PST22

Page 7: Operation integration

5. Examine analytics

How do we know if all that content is actually organized well?

Look at analytics data. Review in-site search terms and compare them with page traffic to see if users are actually finding what they need.

#PST22

Wield your research!

Back up your decisions by showing how they align with best web practices and university goals.

Page 8: Operation integration

6. Map information architecture

The card sort informs this.

#PST22

Page 9: Operation integration

7. Sell to stakeholders

Meet with managers and subject-matter experts for their input.

Prevent them from breaking out pitchforks. Beware of territorial issues! Learn where stakeholders are coming from and listen to their concerns. Make compromises without degrading usability.

#PST22

Page 10: Operation integration

8. Ask the audience

Rustle up wireframes (paper or interactive). User-test the site with key audience groups.

#PST22

Page 11: Operation integration

#PST22

How do we prevent a massive heart attack if our unit reorganizes mid-redesign?

answer. You might not get thrown into a top-level reorganization, but down the line you will probably need to quickly add new content areas to your site. Prepare for future development during the initial construction and as you organize present content.

Page 12: Operation integration

9. Finalize

User tests and stakeholder input inform this.

#PST22

Page 13: Operation integration

10. Customize CMS

Work with developers to make the system fit

#PST22

Page 14: Operation integration

11. Launch!

to celebrate!

deal to get here.

#PST22

Page 15: Operation integration

12. Govern

Establish a governance board for big decisions.

Appoint a variety of members with a spectrum of knowledge.

#PST22

Page 16: Operation integration

13. Tend

Create an audit schedule for routine maintenance. Continue brainstorming for future development and solutions.

Feed it, water it! Designate responsible parties to keep their content accurate.

#PST22

Page 17: Operation integration

Contact

Hollyce Balentine, Digital Communications Manager Michigan State University Infrastructure Planning and Facilities 517-884-4059 [email protected] | ipf.msu.edu |@HollyceB Karen Zelt, Communications Manager Michigan State University Infrastructure Planning and Facilities 517-432-3624 [email protected] | ipf.msu.edu |@zeltkare

#PST22