Discussion on:

Message 25 of 25
0 Votes
+ -
Why go with SharePoint then?
It wasn't my call. Its successful implementation at our other site has my superiors wondering why the users at my site aren't don't get it. By extension, there are questions about my ability to recognize its value and 'sell' it to them. (Hell, I have questions about how to best use it. I've never seen a similar system and don't recognize when it would be the appropriate tool.)

Our DocsOpen installation is over a decade old, unsupported, and must be replaced. SharePoint is the logical candidate, but my users won't consider it until the existing data in DocsOpen is migrated. I've seen no actions on this front, only an agreement that it needs to be done. Such an operation is over my head.

There's also the question of SP's capabilities being oversold to the users. I was excluded from the presentations that were held over a year before roll-out. Users have told me that the final implementation has fallen well short of the promises and potential present in those meetings. It leaves an understandable bad taste in their mouths.

Part of the implementation is an emphasis on content management by the users. Frankly, they don't have the skills, and I wouldn't expect them to; content management isn't their job. This is accompanied by the usual lack of training. It was rolled out with a 'Here it is! Have at it!" approach. This may have worked at the other site, with a much higher percentage of engineers, project managers, propeller heads, and other types who enjoy playing with new technologies, but not here.
Updated - 5th May 2010