3.9 out of 5 (15 Ratings)
May 24, 2017
The tool is great for collaboration across team members. The platform is pretty easy to adopt, with a very small learning curve. However, there is often many bugs when trying to sync heavy files. Daily, it is an irritant. The simultaneous collaboration on same files by different people does not always work, unlike Google's tools.
May 18, 2017
Very helpful in support a complex farm implementation. Most of the team were strong technical folks
May 16, 2017
On-prem Sharepoint missing some key features (eg new OneDrive sync client) vs Sharepoint online to achieve great hybrid setup. User experience not always as good as we could expect from Microsoft products, but we're globally satisfied anyway with our cloud deployment.
May 16, 2017
While the platform has been stable and solid the feature support and overall direction is confusing, every iteration and version the platform seems to go off in a different direction dropping support for existing features or formats
May 11, 2017
The organizaiton is highly dependant on Microsoft tools. Use if Sharepoint as the EDMS solution was a predetermined choise. Users tylcailly find doc management solution cubersome, and the SP solution is no different. Easier to store on shared drives or locally, however Sharepoint provided the solution we needed.
May 8, 2017
While we have a long standing relationship with Microsoft, we hope that they would improve their SP delivery on the cloud. The impediments in the Washington State sector with Microsoft SharePoint online is that, neither, Microsoft, nor the State is willing to work out a realistic implementation strategy. To give you some background - we are currently on SP 2010 on-prem. We would like to move our SP data online. To accomplish this - we need to upgrade to 2013 enroute to 2016 and then go online. However, we are limited by the non-availability of infrastructure to connect to SP online. The only option that is provided is shared tenancy (vs. our preferred own tenancy). Performance so far on the shared tenancy is not attractive. To add to our challenges we have one-source integrated with SP. Decoupling one-source is another challenge.
May 8, 2017
Implementation was relatively easy, however, would have like additional help from a 3rd party to ensure setup is done correctly. Also, over time, SP 2010 became antiquated pretty quickly which is why we are moving to SP 2016 offering more functionality.
Mar 17, 2017
Microsoft did a thorough job on a Technology assessment to align our previous environment (On-premise SharePoint 2010) and the content hosted to a SharePoint Online migration. The Microsoft Partner (Planet Technologies) executed the design adroitly and lead to a successful 3-month migration.
Mar 7, 2017
Very helpful for collaborating and keeping order in project processes.
Jan 27, 2017
I feel Microsoft has struggled in the past to precisely define the core capabilities of SharePoint. . My experience leading my organizatgion to implement SharePoint as the internal/external collaboration tool, as well as to host our Intranet, proved that anyone taking over a tool implementation needs to formally review the business requirements driving such implementation and align the technology capabilities to the strenghts of the tool. In our case, we focused on what we determined, and confirmed with analysts, to be the strong capabilties offered by SharePoint at the time: web content management for internal sites, team collaboration and basic content management with workflow.