Wednesday, June 25, 2008

Considering using Microsoft SharePoint for government websites and intranets? Consider your options carefully

I've seen a lot of hype about SharePoint, Microsoft's solution for, well, just about anything related to online.

The product has been promoted as a Information Management system, as a Web Content Management system (Web CMS), as a replacement for shared drives and file systems, as an enterprise search tool and even as a platform for enterprise applications.

Amazingly enough it can fulfil all of these roles. However like other jack-of-all trades, it's not necessarily the best product for any one of them as detailed in this post, Advice for (prospective) SharePoint customers.

I've particularly been seeing a lot of push for SharePoint in the public sector.

Where agencies have selected a Microsoft technology path there's many good reasons to consider SharePoint as well - less complex environments to maintain, easier to train and recruit staff, there's plenty of synergies that can be leveraged with other Microsoft products.

However when considering any product for a role as important as being the engine of your online channel it's valuable to understand your options and undertake appropriate due diligence before investing public funds.

For instance, the initial purchase price of a Web CMS solution is a very small part of the picture, there's the lifetime cost to consider as well.

Generally I'd expect to use the same platform over a 3-5 year window at least, with substantial ongoing development to meet changing organisational needs. The cost of this development can be substantial.

Another major consideration is the staff costs related to content authoring and publishing. This is the real cost to staff in terms of the time required to use a system in the workplace. While a Web CMS might be cheap to purchase, if it is difficult or time-intensive to use that will seriously compromise the success and the viability of your online channel.

Other factors to consider include content migration, the split of responsibilities between IT and business areas, the cost of extensions to the system and the overall network and hardware costs of the system.

So while SharePoint is one options - and I've seen excellent implementations of the technology in agencies (such as in DEWR) - there are over 140 Web Content Management Systems available for purchase in Australia.

Many of them work very well within a Microsoft environment.

3 comments:

  1. Thanks for this Craig. Choosing a CMS is no simple task and any information that helps sort the good from the bad (or in between) helps.

    ReplyDelete
  2. Thanks Craig, the link in your posting broken and should point to: http://www.prescientdigital.com/articles/sharepoint/advice-to-sharepoint-customers-prospects

    ReplyDelete
  3. Hi Craig,

    I know its been awhile since this post was created but you might still be able to answer my questions.

    I am currently writing a business case for a state govt agency looking at redeveloping both intranet and internets sites. As Sharepoint could be one of the WCM tools considered I wonder if you could
    1.Elaborate more on the staff cost related to content authoring.(In our case we are aiming at distributing content authoring across the agency inorder to minimise bottlenecks in the webmaster are and also reduce IT support involvement).
    2. What are the typical extensions that you see requested for sharepoint.(Our requests are normally webforms and new websites - does this come standard with sharepoint or would a programmer be involved?)

    3. We will obviously be looking at sharepoint 2010. How different is this to 2007?

    ReplyDelete

Note: Only a member of this blog may post a comment.

Bookmark and Share