Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Shine the light, cast out the demons! REFORGING FACULTY DIRECTORIES INTO A MIGHTY TOOL OF POWER

17 views

Published on

Montana State University recently overhauled our faulty directory and faculty profile pages for over 1000 faculty members.

Published in: Education
  • Be the first to comment

  • Be the first to like this

Shine the light, cast out the demons! REFORGING FACULTY DIRECTORIES INTO A MIGHTY TOOL OF POWER

  1. 1. #AUD11 #heweb19 Shine the light, cast out the demons! REFORGING FACULTY DIRECTORIES INTO A MIGHTY TOOL OF POWER
  2. 2. #AUD11 #heweb19 I’m Justin Assistant Director of Web & Digital Communications at Montana State University, Bozeman. @justinwayneshow
  3. 3. Who are you, and why are you here? #AUD11 #heweb19
  4. 4. Why are you here? #AUD11 #heweb19
  5. 5. Here be monsters! #AUD11 #heweb19
  6. 6. #AUD11 #heweb19 Faculty directories and profiles are all over the place
  7. 7. We did it. We fixed our Faculty Directories and Faculty Profiles. We’ll tell you how we did it, what worked well, what we would do differently next time, and about our secret weapon… #AUD11 #heweb19
  8. 8. Hoggle Ian. If you’re going to do this, find your guide.
  9. 9. Spoiler Alert! Presentation Takeaway Cheat sheet #AUD11 #heweb19 • Set a deadline. • Keep pushing the communication. • Use existing data. • Use existing systems the faculty already use. • Find your champion. • Adoption by snowball: get enough and all will follow (FOMO works!) • Build-in easy access to your CMS. • Write good documentation. • Will quell some of the “outside of brand” issues.
  10. 10. Montana State University, Bozeman Montana #AUD11 #heweb19
  11. 11. Current students 16,902 #AUD11 #heweb19
  12. 12. Web team 9 #AUD11 #heweb19
  13. 13. Number of Faculty Members 1,038 #AUD11 #heweb19
  14. 14. Some of our demons… #AUD11 #heweb19 Some of our demons…
  15. 15. #AUD11 #heweb19
  16. 16. #AUD11 #heweb19
  17. 17. #AUD11 #heweb19
  18. 18. #AUD11 #heweb19
  19. 19. #AUD11 #heweb19
  20. 20. #AUD11 #heweb19
  21. 21. #AUD11 #heweb19
  22. 22. #AUD11 #heweb19
  23. 23. #AUD11 #heweb19
  24. 24. #AUD11 #heweb19
  25. 25. #AUD11 #heweb19
  26. 26. #AUD11 #heweb19
  27. 27. #AUD11 #heweb19
  28. 28. Establish goals. Consistent, organized, current, and maintainable. #AUD11 #heweb19
  29. 29. OK! Let’s distribute a template! Whoops! Bad idea. #AUD11 #heweb19
  30. 30. #AUD11 #heweb19
  31. 31. We got a call from the Office of Planning and Analysis It was Ian (our future “Hoggle”.) “Could you use the data we collect annually from all of the faculty to create consistent web profiles?” #AUD11 #heweb19
  32. 32. No, thanks. That’s right, at first we said, “no.” #AUD11 #heweb19
  33. 33. In other words… turning a one-month template design project into a six-month (at least) application design project. #AUD11 #heweb19
  34. 34. And, we remembered that templates were a bad idea… twice before. #AUD11 #heweb19
  35. 35. However… we went back to our goals and we realized that our answer should be… #AUD11 #heweb19
  36. 36. Very YES. #AUD11 #heweb19
  37. 37. Benefits of cooperation • the data already exists and is current-ish (Activity Insight), • since the data is higher quality, we can store and reuse, • faculty already know how to use this system, • we gain a champion in a higher office. #AUD11 #heweb19
  38. 38. Let’s get to it. #AUD11 #heweb19
  39. 39. Communication time! It’s time to start telling everyone what you’re about to do. #AUD11 #heweb19
  40. 40. #AUD11 #heweb19
  41. 41. Start talking to those faculty. Department heads, faculty members, key stakeholders #AUD11 #heweb19
  42. 42. #AUD11 #heweb19
  43. 43. Start talking to that API. API = application programming interface. Pull the data, store it and update it regularly (we do at 3am daily). #AUD11 #heweb19
  44. 44. Ask your service providers for things. #AUD11 #heweb19
  45. 45. Now display the data. Liaise with design colleagues, stakeholders… #AUD11 #heweb19
  46. 46. Once you have the data, you can use it in all the places! • Search • Sorting by expertise • Call the data in news/blog stories • Calendar posts #AUD11 #heweb19
  47. 47. #AUD11 #heweb19 We did it!
  48. 48. #AUD11 #heweb19
  49. 49. [image of current directory search] #AUD11 #heweb19
  50. 50. [image of current directory]
  51. 51. [image of current directory]
  52. 52. What was the score in the end? #AUD11 #heweb19
  53. 53. What was the score in the end? • Nearly 2 years • 2000 development hours • 30 presentations to faculty • 10 big meetings with key stakeholders (Provost, VPs…) #AUD11 #heweb19
  54. 54. What was the score in the end? • 100+ consistent staff and faculty directory pages • 1000+ consistent faculty profile pages with up to date(ish) data • 1 happy Office of Planning and Analysis administrator. #AUD11 #heweb19
  55. 55. Hoggle Ian. Ian is very happy.
  56. 56. What would we have done differently? #AUD11 #heweb19
  57. 57. What would we have done differently? • Set a due date from the start. 3 months at the most. • Used the existing faculty user interface from the start (we tried to build our own.) • Leveraged other departments and included other administrators’ priorities earlier, instead of going it on our own for so long. #AUD11 #heweb19
  58. 58. Takeaways. #AUD11 #heweb19
  59. 59. Takeaways from the Faculty Directory forge. • Set a deadline. • Keep pushing the communication. • Use existing data. • Use existing systems the faculty already use. • Find your champion. • Adoption by snowball: get enough and all will follow (FOMO works!) • Build-in easy access to your CMS. • Write good documentation. • Will quell some of the “outside of brand” issues #AUD11 #heweb19
  60. 60. ROCK AND STONE!
  61. 61. #AUD11 #heweb19 I’m Justin Assistant Director of Web & Digital Communications at Montana State University, Bozeman. @justinwayneshow

×