Unfortunately, if the above is true, you are not short of company. We attended KMWorld in Washington in 2010 -
"learned helplessness" is the phrase that came to mind.

What can happen very quickly is that people grasp the flexibility and power of SharePoint and self empower themselves to do what THEY need. Once this has happened for 3-6 months, it can be totally out of control, and before you know it people are complaining that they "can't find things".

It doesn't have to be this way, and we can show and talk about many counter examples in New Zealand.

A typical assigment to get you back on track reviews the key aspects of what makes an implementation successful and sustainable. Here is some of what we can look at, in forming a make-over roadmap, that you can follow through on, or implement in partnership with us...

	Get a strategy and roadmap	See our strategy process and deliverables This puts the project in context of what is important to the business, and creates the business case for a review/make-over. It also sets clear expectations of what SharePoint should be delivering versus where other systems should be used.
	Create a Strawman	Creating mockups and showing demos of how SharePoint could be or is at other organisations can win people over to the make-over, even if they have previously been negative about what SharePoint can deliver.
	Re-do the Information Design	Often, the lack of a consistent taxonomy is at the heart of the problem. We review what is there and after working with users recommend changes that will make it easier to file and find information. In other cases, the taxonomy itself may be fine - just not very well implemented in SharePoint. The term-store in particular looks like "best practice" but often it isn't. We can show you how to do the following, as well as provide iLab training in it: Site collection set-up Use of metadata and content types Use of sites, libraries and subsites
	Self sufficiency options	Reviewing your internal SharePoint skills and what gaps there are - from deep technical to BA and 'at the desk' user support.
	Governance	What roles, policies and measures are needed to manage the implementation at technical, information architecture, support, training and business-as-usual usage levels. Expect to rein in super/power user rights, but at the same time deliver users and their team members more usability and usefulness.
	Change & Expectation Management	SharePoint may well be easier to use than other technologies, but that doesn't mean users will flock to it! Use our proven behaviour change models to form a communication, training, monitoring and enforcement framework suited to your culture. Pilot the "new way" early.
	Infrastructure Health Check	Do our health check to determine whether some of the issues are caused by incorrect or suboptimal settings