The Sharepoint Effect Revisited
- September 1, 2009
- 4 Comments
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 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:
- Will the SharePoint Processes be Upward Compatible?
- Will the SharePoint Content be Managed Well?
I think the answer to both is essentially no. Oh there may be upgrade paths defined, but the ability of the average firm to execute those adequately is probably not high. This isn’t upgrading from Word 97 to Word 2003. All those customizations you’ve made will probably need to be redone/rewritten.
Sharepoint is a bit of the wild west of process. Slightly better than the random collection of spreadsheets that often are just as pervasive within organizations as the best way they have available to manage their processes. The proliferation of Sharepoint is, to my mind, a reaction by business users to not having the right tools and training available to deliver real business process solutions to their business. Often they aren’t allocated IT budget for the applications they need, and so they cobble together solutions in Excel, Access, and Sharepoint.
A few things I’ve noticed about sharepoint “processes” though:
- 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.
For a more amusing take on Sharepoint and BPM, see a previous post on this blog, noting the 6 major barriers to BPM adoption. Quoting directly:
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.