Wanna Use SharePoint....What's User Pain...What about User adoption...once you are ready with it....???? So lots of things to discuss here....User Training....what to tell them and what's not....lot's of thingssssssssssssss................So how to manage it.....here are few tips.....
Don’t let IT Run the project – SharePoint is a business facing application. Unless there is a fresh installation needed, try to keep the project run by someone in the business who understands the challenges in the business rather than of the technology.
Requirements gathering – Ask end users what they want by actually asking the question ‘tell me about the challenges in your business’. Count the blank looks on people’s faces when you ask ‘tell me what you want SharePoint to do.
Custom code – There is always a time and a place for this but avoid wherever you can. For every 5 days of development, the same can be achieved with configuration in 1.
‘Out of the box’ Features - Get to know all of the features that are in SharePoint. Knowing what the product can actually offer can avoid custom code!
3rd Party Products – SharePoint, like all systems, has its shortfalls, but there are thousands of products that can be bolted onto SharePoint to address these. These costs a fraction of the cost of developing from scratch and are supported also.
Micro-Projects - Wherever possible, try to deliver SharePoint offering in small chunks. This will make SharePoint become viral and also make it easier to improve on each piece that you deliver. Hard to do with a ‘big bang’ approach.
End User Training - Train Train Train – Allow a decent budget for training end users on how to actually use SharePoint. How will people use the tool if they don’t know how to?
Support - Log a ticket approach doesn’t work with SharePoint. Try to identify the ‘power users’ that can be accessible to help the business users.