Competing in the Attention Age<br />
The Information Age has ended, and the Attention Age is in full swing<br />In the new age anyone can create, share and con...
Competing for Attention<br />
Web giants such as Facebook and Twitter are raising the bar for user expectations<br />Incredibly easy to use, streamlined...
Example: 4 Distinct UIs<br />
Not easy to use, not streamlined<br />Why do I have to log in again?<br />Why does this interface look different, and how ...
Example: Item Status<br />
Facebook/Second Cup Example<br />
Not lack of resources<br />Not lack of technical know-how<br />Given the solutions available, it’s virtually impossible fo...
Everything comes back to interoperability<br />Library systems are not truly open<br />Library systems are not integrated ...
Emphasis on standards vs. ad hoc recombination of functionality<br />Focus on data integration, “record sharing” vs. appli...
Standardization over innovation<br />Data over users<br />Centralized control over decentralized collaboration<br />Inform...
Interoperability is active, not passive<br />Just implementing standards is not enough<br />New, more powerful forms of in...
The Bad News: Interoperability is Difficult<br />
What is an Open API?<br />Publicly accessible web service<br />Free or nearly-free<br />Promoted on an API directory such ...
Example: Pie Palace BiblioPress<br />
What is a White Label Solution?<br />Software you can brand and integrate tightly into your domain to create a seamless us...
Example: BiblioCommons<br />
Openness and configurability only gets us 50% of the way there<br />True interoperability is multidirectional<br />Single-...
What is Software as a Service?<br />Software delivery model in which applications are hosted by a vendor and made availabl...
Interoperability is a culture, not a technology<br />Integration needs to be a core organizational capability<br />SaaS is...
BiblioCommonsDrupal Integration<br />
BiblioCommonsDrupal Integration<br />
The Attention Age is upon us and libraries are competing for attention with web giants<br />Web giants have a significant ...
Upcoming SlideShare
Loading in …5
×

Competing In The Attention Age

402 views

Published on

This is a presentation I gave as part of the Top Tech Trends panel at OLA Super Conference 2010.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
402
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Competing In The Attention Age

  1. 1. Competing in the Attention Age<br />
  2. 2. The Information Age has ended, and the Attention Age is in full swing<br />In the new age anyone can create, share and consume information instantly and freely<br />Information is now cheap so attention is the most valuable commodity<br />The Attention Age<br />
  3. 3. Competing for Attention<br />
  4. 4. Web giants such as Facebook and Twitter are raising the bar for user expectations<br />Incredibly easy to use, streamlined user interfaces<br />Seamless integrations and ubiquitous connectivity<br />How do libraries stack up?<br />New User Expectations<br />
  5. 5. Example: 4 Distinct UIs<br />
  6. 6. Not easy to use, not streamlined<br />Why do I have to log in again?<br />Why does this interface look different, and how do I use it?<br />Not seamless, not ubiquitous<br />How do I find an award winning book that’s available at my branch right now?<br />Why can’t I access My Account from my cell phone?<br />Library Systems<br />
  7. 7. Example: Item Status<br />
  8. 8. Facebook/Second Cup Example<br />
  9. 9. Not lack of resources<br />Not lack of technical know-how<br />Given the solutions available, it’s virtually impossible for a library:<br />To tie solutions together in a way that creates a seamless user interface<br />To extend the reach of library data and systems to new applications and channels<br />What’s the Problem?<br />
  10. 10. Everything comes back to interoperability<br />Library systems are not truly open<br />Library systems are not integrated with each other<br />Vendors are building vertical ‘silos’ of functionality<br />The Problem<br />
  11. 11. Emphasis on standards vs. ad hoc recombination of functionality<br />Focus on data integration, “record sharing” vs. application integration<br />Disconnected vendor silos vs. interconnected eco-system of service providers<br />Traditional Library Approaches to Interoperability<br />
  12. 12. Standardization over innovation<br />Data over users<br />Centralized control over decentralized collaboration<br />Information Age Paradigms<br />
  13. 13. Interoperability is active, not passive<br />Just implementing standards is not enough<br />New, more powerful forms of interoperability are required: <br />Open APIs<br />White Label solutions<br />Software as a Service (SaaS)<br />New Rules in the Attention Age<br />
  14. 14. The Bad News: Interoperability is Difficult<br />
  15. 15. What is an Open API?<br />Publicly accessible web service<br />Free or nearly-free<br />Promoted on an API directory such as programmableweb.com<br />Key challenge for doing this right:<br />Enabling infrastructure including hardware, bandwidth, key management, usage metering, documentation, developer forums and support<br />Open APIs<br />
  16. 16. Example: Pie Palace BiblioPress<br />
  17. 17. What is a White Label Solution?<br />Software you can brand and integrate tightly into your domain to create a seamless user experience<br />Key challenge for doing this right: <br />Configurability vs. customization <br />White Label Solutions<br />
  18. 18. Example: BiblioCommons<br />
  19. 19. Openness and configurability only gets us 50% of the way there<br />True interoperability is multidirectional<br />Single-Sign-On should just work<br />“Save To” should always save to the same place<br />“Tell a Friend” should always show same list of friends<br />Every vendor needs to proactively integrate other solutions into their product<br />What’s Missing?<br />
  20. 20. What is Software as a Service?<br />Software delivery model in which applications are hosted by a vendor and made available to customers over a network<br />Key challenge for doing this right:<br />Software on demand vs. ASP<br />Software as a Service (SaaS)<br />
  21. 21. Interoperability is a culture, not a technology<br />Integration needs to be a core organizational capability<br />SaaS is an agile delivery model which enables this capability<br />The multi-tenant nature of SaaS creates economies of scale<br />How SaaS Enables Interoperability<br />
  22. 22. BiblioCommonsDrupal Integration<br />
  23. 23. BiblioCommonsDrupal Integration<br />
  24. 24. The Attention Age is upon us and libraries are competing for attention with web giants<br />Web giants have a significant head start when it comes to interoperability<br />Vendors must embrace new forms of interoperability, but they’re difficult to get right<br />Conclusion<br />

×