Item: Microsoft SharePoint
Rating: 10
Author: Verified User

Overall Satisfaction

Use Cases and Deployment Scope

It is being used by our entire organization. It is solving multiple business problems as we have many manual paper processes throughout the company. Additionally, our users complain that file shares are a mess. It is hard to find content. Sometimes, when they do find the content they are looking for, there are multiple copies of the same file and they are not sure what file to use. There is a lot of duplication of content across all departments.

Pros and Cons

Pros

The ability to control documents and the collaboration process. Capturing version history is a big deal for our organization.
The ability to share documents without sending attachments through emails. We have a major problem with mail storage. Moving to SharePoint has helped us alleviate this as instead of sending documents through email, users are sending a link to the document.

Cons

Anything missing can really be accomplished by developing your own solutions or purchasing an add-on product. SharePoint is just a platform for you to build it as you see fit to meet business needs.

Return on Investment

Our users are no longer walking documents around for approvals. They are using straight OOTB workflows included in SharePoint that allow for the documents to be routed around for approvals automatically. This solution in itself has been a HUGE time saver.

Alternatives Considered

none

Likelihood to Renew

I am still using it.

Likelihood to Recommend

SharePoint can become an unmanageable beast VERY quickly. Every organization implementing SharePoint should take the time to write a Governance Plan that is appropriate for the application of SharePoint within the organization. There are a lot of resources on the internet that help with this. However, don't just copy a governance plan off the internet, change some names and call it a day. It should be custom to your organization and the vision and plan for the use of SharePoint. This Governance Plan should include what SharePoint will and will not be used for, how it will be used, and it should be reviewed and updated frequently. Also, it should not just be a written plan that is never read by end users. Governance should be engrained into training.

Always remember - no matter what anyone tells you, SharePoint is not the be all, end all. Requirements should be gathered
BEFORE making the decision to move to SharePoint and/or build a solution
on SharePoint.

Training

Training Types Used

Online training
In-person training
Self-taught

In-Person Training

The face to face training I received was on SharePoint Administration. It was rushed as there was a lot of information to cover and the application of the labs weren't that great either. I like to be able to relate what I am learning to what I am currently doing.

Online Training

I like to learn at my own pace and online training allows for that. Additionally, you can skip through pieces of content that you already know or are already comfortable with. Microsoft actually offers great videos on their website for basic fundamental SharePoint Training. I have used these training videos in some of my own training sessions with end users.

Ease of SharePoint Training

Some parts were easy, others were harder to learn. It took a lot of "poking around" to really get the hang of SharePoint. There are SO many features available that it can get overwhelming very quickly. Take your time and focus on specific pieces of SharePoint. I'd recommend starting with the fundamentals - List & Libraries and then build your knowledge from there.

Comments

Please log in to join the conversation

SharePoint is not the be all, end all but it is definitely a GREAT application