SharePoint is Microsoft’s most popular product. It’s used for creating company Intranets which are basically private websites dedicated to a company or organization that only that organization’s employees or members can enter.
When anyone has a subscription to Microsoft Office 365 they typically will receive a “One Drive” account. (If you have access to 0365 through a corporate account, One Drive is automatically included and it’s normally, by default, available to all users. It is however possible for your corporate IT Department to “turn off” One Drive. (This is sometimes done for security reasons)
Building a SharePoint Intranet is like rubbing Aladdin's lamp…
People know it’s powerful but they rub it before they've formulated their wish. And just like all the stories you hear, the results are funny, unless you are the one holding the lamp.
The analogy really holds true. Most organizations fail to adequately plan their SharePoint projects and so they fail. But while only about 10% of SharePoint projects (on average) are considered initially successful by their project teams, less than 1% of customers switch to a different platform.
Recently we undertook a project to create a “textbook” Records Management system for a municipal utility. It was going to be built in SharePoint 2016 (on premise) and they wanted the entire implementation to be without the use of custom code.
Their criteria for a true SharePoint-based Records Management System was…
The benefits to supplying your organization with a high-quality implementation of Office 365 closely integrated with a SharePoint Intranet and Microsoft Exchange are irrefutable. Having these three powerful application environments skillfully implemented and professionally maintained by Microsoft eliminates an enormous amount of technical headaches while saving most organizations considerable cash.
in order to try to drive much higher rates of adoption for SharePoint in the enterprise. Over the last year an enormous amount of attention has been given to weaving various types of social communication systems into the SharePoint environment. The theory seems to be that since these types of communication systems are popular as stand-alone systems, blending them into a SharePoint environment will provide a reason for more employees to enter the SharePoint environment.
So your organization needs some IT Development done…
Let’s say an intranet, public facing portal or similar project. Let’s also say you’re the lucky manager that gets tasked with directing the outsourcing of the project.