By ToniVC from Flickr under CC BY-NC-ND
Enterprise 2.0:
- Where did my Time go?
- Generic Toolbox or Specific Solution?
Dion Hinchcliffe‘s article on 14 Reasons Why Enterprise 2.0 Projects Fail provides some insight into the current effectiveness of the QUT Library’s initiatives, and some lessons that they could take on board. There is a a definite road bump in the form of governance (point seven), as well as islands of participation surrounded by inaction (point ten). I’m going to talk about “Pushing Enterprise 2.0 as a generic toolbox instead of the solution to specific problems” (point eight), which can lead to “Not waiting long enough to let critical mass build” (point fourteen).
There are a range of issues in the area of pushing Enterprise 2.0 as a generic solution, rather than choosing solutions that best fit specific problems.
For example, the Library does have a twitter account, which at the moment is almost exclusively used for announcements and Library news. This is an old point, but Twitter usually works best as a social platform, not a broadcast platform. It can be used that way, but I think this could be partly due to seeing Web 2.0 and Enterprise 2.0 as a hammer, and treating everything as a nail.
A central issue for the Library is one of time. Staff time. Student time. Students have little time to spare, and adding to that load through extra features on the Library website may not be the best path. Instead, some specific issues should be addressed.
For example, rather than incorporating rating functionality that requires extra work, a recommendation system could use the number of visits, visit lengths, and time of stay to calculate ratings for each resource. This would utilise a core element of Web 2.0 – data is important, and can be used for a huge range of things. Essentially, the ratings are already there, just waiting for an algorithm to extract them, and a method of displaying them.
Finally, in the course of using tools that might not fit the purpose or building functionality that requires more user input, there is a very real risk that these errors will not be seen as the cause. Lack of adoption might be blamed on promotion or issues from lack of strict governance. Finding tools that fit a specific problem is only the first step – how the tools are used, and the extra time required is an important consideration.