From a technology perspective it fits very nicely with where the rest of the industry is going for collaborative authoring experiences for the organization. MOSS is a key enabling technology behind the dynamic systems stack led by Microsoft.
One key is to focus in on the Intranet as piece of plumbing. You control the pipes, determine where they go, and if necessary, adjust some shutoff valves. If you were to roll out MOSS and keep a centralized deployment team, you are really not taking advantage of enabling dynamic business processes.
Building a SharePoint portal brings a different paradigm than we had with Dreamweaver and Sitecore. It gives the authors yet a third paradigm for creating content. It's not hard, but I'm confident that our end users was freak.
When you combine the cultural changes, paradigm shifts and its ability to really enable a dynamic organization, I can certainly predict doom for this initiative. We have a single department with a very tight hold on content, we sort of does alright cultural changes, but the big driver here is the organization’s tendency to shy away from a dynamic environment. By no means is this a show stopper, and I’m being a bit cynical here, but when we attempt to deploy dynamic technology into the enterprise we really need to understand the cultural considerations of the organization.
Subscribe to:
Post Comments (Atom)
1 comment:
Yeah, sharepoint would have to be so locked down to please M&C that you would lose a lot of the value I suspect. The alternative is to introduce more and more MOSS through the IS site and build a groundswell of interest rather than a wholesale bopnet replacement. Of course M&C is justified in wanting to control the internal messages of the org but then we don't get to leverage user participation. What to do?
Post a Comment