It has been our observation that many, and perhaps most, SharePoint projects in the English (as distinct from Scottish, Welsh etc) National Health Service fail to a greater extent than they succeed. Yet the NHS has very strong needs for the types of solution that SharePoint provides, it has increasingly mature infrastructure and project skills as well as access to technical skills which are as competent as any other sector, whether provided internally, through contractors, suppliers (or partners as we like to call ourselves) and Microsoft itself.
In the course of our research 9and writing a much more extensive article on the subject) we have identified teh following core reasons why SharePoint projects fail:
Trusts don’t know what to ask for or even what Sharepoint might do for them; many suppliers don’t understand the NHS. Communicatoisn gaps ensure.
SharePoint is a huge application and can solve many issues, leading to prioritisation issues and massive scope creep
No single person has sufficient knowledge of SharePoint to know all the out of the box capabilities
Trusts naively beleive that they can deploy impactful technology without building in appropriate change management to drive the adoption and deliver benefits