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.

Tech Tools

475 views

Published on

Tech Tools

Published in: Education
  • Be the first to comment

Tech Tools

  1. 1. What You Need to Know About Library Technology Roy Tennant
  2. 2. So this happened.
  3. 3. Photo by http://www.flickr.com/photos/annarbor/ License: CC BY 2.0
  4. 4. CC-BY NC 2.0, http://www.flickr.com/photos/37996583811@N01/
  5. 5. CC BY-SA 2.0, http://www.flickr.com/photos/jabberwock/4752711073/
  6. 6. CC BY-NC-SA 2.0, http://www.flickr.com/photos/mateus27_24-25/6232593647/
  7. 7. CC BY-SA 2.0, http://www.flickr.com/photos/secretlondon/2592690167/
  8. 8. Photo by http://www.flickr.com/photos/nox_noctis_silentium/ License: CC BY-SA 2.0
  9. 9. Photo courtesy Robert Scoble, flickr.com/photos/scobleizer/, CC BY 2.0 License ALL of what I just described happened within 15 years: 1978-1993 ALL OF IT
  10. 10. What happened in the next 20 years?
  11. 11. Photo courtesy Robert Scoble, flickr.com/photos/scobleizer/, CC BY 2.0 License
  12. 12. What can we learn?
  13. 13. The Last Century in Info Tech The Last 20 Years of the Century
  14. 14. As of 16 January 2015
  15. 15. We needed this… To eventually get here…
  16. 16. Photo courtesy Robert Scoble, flickr.com/photos/scobleizer/, CC BY 2.0 License
  17. 17. What’s different about library technology?
  18. 18. Mostly Public Organizations Photo by Wally Gobetz, Creative Commons CC BY-NC-ND 2.0 license
  19. 19. Finite Resources Photo by 401(K) 2012, Creative Commons CC BY-SA 2.0 license
  20. 20. Aging Workforce
  21. 21. Special Requirements • Specialized metadata (i.e., MARC) • Specialized workflows • Often constrained conditions (e.g., limitation on suppliers, forced reliance on central IT, etc.) • Collegial nature of many institutions makes fast adoption of technological change difficult
  22. 22. Gartner Hype Cycle
  23. 23. How to Ride Shotgun Down the Avalanche
  24. 24. Create Agile Institutions • Minimize red tape • Maximize communication channels • Use task forces to accomplish group work • Encourage new ideas, risk-taking, and trying things out • “Release” early and often • Kill things off when they stop providing value
  25. 25. Foster Ongoing Staff Development • Provide opportunities for professional development • Support conference attendance • Encourage use of current awareness resources
  26. 26. Offer Compelling Local Services • What can only be done locally, or done most effectively at a local level? • Suggestions: – Special collections – Services requiring personal contact – Services requiring physical spaces (e.g., study space) – Services requiring specific knowledge of local needs
  27. 27. There Are NO Permanent Parts • Monitor your environment • Build for constant change • Your job description will change • Professional development is an ongoing responsibility • What you know now is likely what you won’t need to know in the near future
  28. 28. Get Ready for the New • Seek out the next big thing • Monitor & evaluate initially, don’t adopt too quickly • If it approaches inevitability, prepare
  29. 29. Prepare • Inform staff early and often • Invite participation in imagining futures • Watch for potential champions • Provide space and time for innovation • Cut the deal — support for a period of time, then cut & run or to production — fail early and try often • No penalties for trying — only for NOT trying!
  30. 30. The Way Forward • Create agile institutions and foster ongoing staff development • Offer compelling local services • Refocus staff on direct user services • Realign priorities • Improvise, Innovate, and Collaborate
  31. 31. Final Advice
  32. 32. Final Advice • Neither an early adopter nor laggard be • Technology with market share tends to beat better technology • Do not underestimate the power of an upstart with a great idea • It’s the customer, stupid! • Back it up or kiss it goodbye • Never make your expensive resource wait on your inexpensive one
  33. 33. Final Advice • Never underestimate the power of a prototype • Buy hardware at the last possible moment • Don’t buy software with a zero at the end of the release number • If you’ve learned a technology thoroughly, it’s already on its way out • For any project, there are several ways it can succeed and countless ways it can fail
  34. 34. ` FreeLargePhotos.com @rtennant facebook.com/roytennant roytennant@gmail.com

×