The Sharepoint Effect Revisited
Sharepoint starts many processes. As Jim indicates, the use of Sharepoint is pretty pervasive. Interestingly, in a previous post, Jim Sinur referred to Sharepoint as a virus (for good or ill). In this article, Jim asks two key questions:Like the hydra, Sharepoint is a beast with many heads. You chop one off and three more grow in its place! A recent posting by Jim Sinur posits that
- Will the SharePoint Processes be Upward Compatible?
- Will the SharePoint Content be Managed Well?
- Usually very few people understand what the process is supposed to be. You kind of have to know what it is to leverage it.
- There are lots of deadwood Sharepoint sites/sections/processes. More than live ones… Making it harder to find the stuff that is “active” – nothing worse than thinking you’ve submitted your vacation form only to find out that the vacation request process has moved!
- There is a tension between control and chaos that is particularly problematic on Sharepoint. To get wiki-like collaboration benefits, you need to open up the gates for users to do their own designs/layouts/etc. But when you do that, you lose the control and policing necessary to make sure that everything in Sharepoint is “managed” in an enterprise sense.
The Sharepoint Effect. This is almost the opposite of the Bus Brake Effect. Where the bus brake effect concerns too many vetos and not enough yes-votes, the Sharepoint Effect represents the unbridled proliferation of ungoverned, adhoc processes using unmanageable technology. Sharepoint becomes a substitute for process, or a substitute for the Excel-based or Access-based processes of the past. However, there’s no way to find the appropriate Sharepoint site for the appropriate process or process task. […]It isn’t that enterprises shouldn’t use Sharepoint, but the business and IT should be careful not to let the tail wag the dog with the proliferation of such sites… otherwise you run the risk of Excel/Access purgatory part 2.