SharePoint Reviews

SharePoint has conquered the enterprise intranet. Although the conquest is never as bloody nor expensive as more invasive conquests, such as the Mongols under Genghis Khan, intranet citizens are not always thrilled by the new system and structure under Gates Khan.

SharePoint is present in about 90% of the Fortune 100; and plays a prominent intranet role in about 70% of knowledge worker intranets (either powering the main intranet portal, or delivering associated collaboration sites and/or document repositories). This in spite of its history.

SharePoint 2007 was a dog; SharePoint 2010 was a dressed-up dog; but SharePoint 2013 represented a leap forward to a more user-friendly, true web platform. SharePoint 2016 saw improvements, but perhaps the most significant advances have come in the last couple of years with the release and evolution of SharePoint online the advent of Office 365, now Microsoft 365.

SharePoint Online, and the on-premises version SharePoint Server, represent considerable improvement to a a very usable, complex digital workplace solution. SharePoint Online Modern Experience has become a truly mobile friendly solution, with a number of improvements to collaboration (particularly Teams and a dedicated mobile app) and for hybrid cloud scenarios.

There are a lot of reasons to buy into or upgrade to SharePoint Online: the latest iteration of Microsoft’s portal-web development platform represents a massive, multi-million dollar upgrade on the previous versions of SharePoint (a version that was typically oversold given its underwhelming if not frustrating performance and lack of execution). SharePoint Online and Server are massive upgrades from previous versions: noticeable improvements to AI (Copilot), social computing (Teams, Engage, Loop and more), mobile computing (responsive design with "modern" pages and a dedicated mobile app), better Office integration, Teams, cloud and hybrid integration, search and more. SharePoint Online also comes with federated search that allows the user to search out files and content from across all Microsoft 365 apps (including SharePoint, Teams, OneDrive, etc.).

But it’s not all good news, and it’s not a solution that fits every organization.

Here at Prescient Digital Media, we upgraded move to SharePoint Online in Office 365 (which is a more feature and functionally rich version than SharePoint Server). Though some problems persist, the bugs and challenges are not as persistent as versions 2013 and 2016. There are some obvious improvements (pros) and some persistent issues (cons): 

• Cloud – you no longer need to worry about patches, maintenance and security; Microsoft takes care of this for you
• Mobile – enhanced mobile access experience with completely responsive sites and apps, and dedicated single sign-on apps for each of the tools in the 365 toolset
• Social – enhanced social networking via Engage and Teams and Loop
  
• Web CMS – enhanced publishing and management interface (employing the ‘ribbon’ from Office)
• Branding – the new "modern pages" are slick and responsive; it can be more challenging to implement new custom designs using the new modern pages versus classic, and MS has openly cautioned against customizing the home page
• Search – search is much improved with the full integration with the FAST search engine, but requires some configuration work

There are far more pros than cons, but there should be at the price MS charges. SharePoint is very good for a small to medium-size intranet in a .NET environment that requires a web development platform focused on enterprise content management. In some scenarios, SharePoint can excel as a large enterprise intranet, but it can cause headaches if its overly customized. But it is not cheap, typically requires a lot of work and customization, and doesn’t always work as promised.

Speaking of conquest, the Chinese learned Mongol lessons the hard way, and built the Great Wall. Although a firewall is requisite with any intranet, not just a SharePoint intranet, walls kill collaboration and employee knowledge management. More salient, key lessons can be drawn from implementing and working with SharePoint:

• Licensing represents a fraction of the cost
• Planning and governance are mission critical – mission critical
• Governance requires careful planning and implementation with process and roles that are independent of the technology
• Custom or third-party web parts and applications can really enhance the experience but can be costly
• Change management is the key to success

For more information see the SharePoint For Communicators white paper, at www.PrescientDigital.com.

First and foremost, SharePoint is an intranet platform. Though Microsoft states that SharePoint is "primarily sold as a document management and storage system" it is an information sharing platform and for "implementing internal applications, and for implementing business processes."

SharePoint is the know market leader for powering intranets: about 90% of the Fortune 1000 use SharePoint in some shape or form (with many using it to power their Intranet home page).

There are in fact two versions of SharePoint: the on-premises version, SharePoint Server, and SharePoint Online, which comes bundled in Microsoft 365 (the Cloud). Though those with Microsoft 365 (formerly Office 365) automatically have the latest features in SharePoint Online; those with on-premises SharePoint, have to wait for the next release to get the latest and greatest.

SharePoint’s greatest strength is it’s an all-in-one approach – it’s a portal, a content management system, a search engine, a social collaboration platform, a web development platform, and so much more. Its greatest weakness is that it’s an all-in-one solution – everything and the kitchen sink; a jack-of-all-trades, a master of none. Some argue that SharePoint is a “mile wide, but a foot deep.” It offers so much, but some features are seen as still ‘developing’ or even sub-par. But there are a lot of tools and features, and with each release, it gets better and better (though more complex).

It’s important to note that SharePoint is still a technology. It doesn’t include all of the people, process and planning that is required to make any intranet technology work. Intranet technology will fail without careful planning, process and committed people. Most of the key ingredients of a successful intranet in the digital workplace are based on people, and process; technology is merely an enabler.

Features include:

1. Cloud / Hybrid - Hybrid enables you to integrate your on-premises farm with the cloud, at your own pace.
2. Durable Links - Resource-based URLs now retain links when documents are renamed or moved in SharePoint.
3. Video recording, storage, and screen recording - an all-in-one video solution using Stream, including video editing.
4. Large files - now supports uploading and downloading files larger than 2,047 MBs
5. Mobile - an improved mobile navigation experience, including a very fast and easy to use app.
6. Search - SharePoint Search integrated the FAST Search engine, with more features, and indexes up to 500 million documents (per app).
7. Sharing - better user sharing options, including a Shared folder, and invitation email notifications.
8. Microsoft Teams - full integration with Microsoft Teams (all Teams files are stored in SharePoint).

We are Intranet consultants (www.PrescientDigital.com) and and principally use Microsoft 365 - SharePoint Online for Enterprise Content Management; improving the way our organization functions in terms of employee collaboration and knowledge sharing specifically via document management, and social collaboration (discussion groups, profiles and blogging being the most used social tools). Increasingly we use Teams, and use it with external clients that can be invited to a specific Team (project site).

Web content management and social media tools (e.g. wikis) are not best-of-breed, and usability is an issue with many features. We also encountered many, many problems with deployment -- customization and implementation requires more work than you expect. Additionally, like most organizations, a customized user experience can break (particularly specific webparts) with every SharePoint patch and upgrade. However, we found no issues with stability or scalability. 

80% of our clients use SharePoint, and probably some 90% of the Fortune 1000 use SharePoint in some shape or form. We are first and foremost SharePoint intranet consultants, so we build and design other intranets, and need to deeply understand the ins and outs of SharePoint. 

The initial setup of SharePoint is very easy - out-of-the-box deployment is simple, fast and a novice could manage a deployment. Customization requires a lot of work, particularly using SPFx (hiring an outside expert is strongly recommended).

A note of caution: planning is everything. The intranet is more about people and process, and any intranet requires a through plan -- for information architecture, content management, design, and change management -- plan, plan, plan. And plan to run over-budget (unless you hire very strong outside experts to develop and run your plan and budget) for customization activities. 

SharePoint features major upgrades to the user experience design and mobile access, including a new dedicated SharePoint app. It’s very clean and modern, with a major emphasis on images, and video. The new "modern UX" is fully responsive, and has it's own dedicated mobile app.

Among the new UX features, particularly noticeable in the new SharePoint Communications Sites, are drag-and-drop web parts for image galleries, slideshows, hero slideshow, and video.

Continue reading: The New SharePoint

What is our primary use case?

What is most valuable?

What needs improvement?

For how long have I used the solution?

What do I think about the stability of the solution?

What do I think about the scalability of the solution?

How was the initial setup?

What about the implementation team?

What other advice do I have?

What is our primary use case?

How has it helped my organization?

What is most valuable?

What needs improvement?

For how long have I used the solution?

What do I think about the stability of the solution?

What do I think about the scalability of the solution?

How are customer service and support?

How would you rate customer service and support?

Which solution did I use previously and why did I switch?

How was the initial setup?

What about the implementation team?

What's my experience with pricing, setup cost, and licensing?

Which other solutions did I evaluate?

What other advice do I have?

Which deployment model are you using for this solution?

SharePoint is appreciated for its simplicity of use out-of-the-box, though derided for problems (and the expenses) customizing the user experience (design, navigation and information architecture).

SharePoint is replete with functionality and applications, and is the most comprehensive intranet development platform on the market. It is, unfortunately, expensive, and most of the feature set that we use, and that our clients use, fall short of expectations, and often below best-of-breed. SharePoint isn’t a niche product that is supposed to be superb at web content management, or social networking; it’s a broad solution, one that has something for everybody; a solution that can please some, but not all.

SharePoint’s greatest strength is that it’s an all-in-one solution – it’s a portal, a content management system, a search engine, a social collaboration platform, a web development platform, and so much more. Its greatest weakness is that it’s an all-in-one solution – everything and the kitchen sink; a jack-of-all-trades, a master of none. Some argue that SharePoint is a “mile wide, but a foot deep.” It offers so much, but many features are seen as sub-par. 

SharePoint is part enterprise content management (ECM) solution, part portal solution, part web development platform, part social media platform. It offers many, many solutions and functions – often too much for most organizations – but it is Microsoft’s hope that it will become everything to everybody including the de facto platform for the company intranet, website(s) and extranet(s). In sum total, it is an amazingly powerful solution, but often fails to live up to expectations.

SharePoint 2013 was a fair solution, with an abundance of time, patience… and money, it could work; SharePoint 2016, is even better, but still requires a lot of care, and investment.

The latest, SharePoint 2019 (and SharePoint Online in Office 365), further improves upon previous versions, notably the mobile experience and the user experience. 

SharePoint has a new mobile app, so you can access your intranet using a phone app, instead of using the browser. Outside of the app, SharePoint has a new, clean mobile experience – greatly enhanced over the mobile experience in SharePoint 2016.

Another big, major improvement to SharePoint is the new user experience (UX) design and general usability of SharePoint. It is noticeably superior to previous versions of SP. It’s very clean and modern, with a major emphasis on images, and video.

“SharePoint 2019 has the most UX (improvements) than we’ve ever delivered before in a SharePoint release,” Hani Loza, of the Microsoft SharePoint team.

Among the new UX features, particularly noticeable in the new SharePoint Communications Sites, are drag-and-drop web parts for image galleries, slideshows, hero slideshow, and video.

Microsoft has released a new video function and portal, called Stream. Using Microsoft Stream, videos will play automatically in a page, and it includes auto transcription, face detection, and enhanced sharing and tagging. The Stream team say “audio transcriptions and face detection make finding relevant content easy—even for specific words or people shown on screen, whether in a single video or across all your company’s videos.”

From a governance perspective, SharePoint is good, when compared to other platforms. It is not perfect, but no solution is.

Like the content of your website or intranet, planning and governance is technology agnostic; whether it’s SharePoint or another portal or content management platform, the necessity for and the approach to governance is the same. In short, governance lives and dies with its owners, and the rules they put in place, regardless of the technology. Governance is largely applicable to any technology platform and as such is generic to start.

When building a governance model for SharePoint, the major components should include:

• The umbrella ownership model – Centralized? Decentralized? Collaborative?
• Defined ownership structure (names and titles)
• Roles and responsibilities (jobs and duties)
• Decision making process (who is responsible for what and when)
• Authorization (who is responsible for what and when)
• Policy (what is allowed, and what is not allowed)

While governance is generic in nature, regardless of the software and hardware, there are some components of SharePoint that require specific consideration. Site Collections and Team Sites are so easy to deploy, and it is so easy for even the most neophyte web users to create a site (e.g. Team Sites, My Sites, Publishing Sites, etc.), SharePoint sites can easily grow at exponential rates and amount to tens-of-thousands in a short period of time. ‘Baking’ in rules and inheritance to site collections is critical to ensuring a consistent, uniform user experience.

These issues and others are discussed in-depth including, SharePoint governance, and some of the specific, requisite steps and policies for implementing intranet and in the SharePoint Governance white paper.

To learn about the specifics of intranet design with SharePoint, see the Intranet Design white paper.

What is our primary use case?

How has it helped my organization?

What is most valuable?

What needs improvement?

For how long have I used the solution?

What's my experience with pricing, setup cost, and licensing?

Which other solutions did I evaluate?

Which deployment model are you using for this solution?

What is our primary use case?

How has it helped my organization?

What is most valuable?

What needs improvement?

For how long have I used the solution?

What is our primary use case?

How has it helped my organization?

What is most valuable?

What needs improvement?

For how long have I used the solution?

What do I think about the stability of the solution?

What do I think about the scalability of the solution?

How are customer service and technical support?

Which solution did I use previously and why did I switch?

How was the initial setup?

What about the implementation team?

What was our ROI?

What's my experience with pricing, setup cost, and licensing?

Which other solutions did I evaluate?

What other advice do I have?