Given SharePoint’s abundance of features and extensive content management capabilities it’s no wonder that the term, “SharePoint sprawl,” is used in referring to the never-ending expansion of sites within the suite.
Today’s SharePoint is not unlike it’s 2010 iteration when it comes to implementing a quick start, thanks to it’s basic install option to allow committees, groups and team members begin collaborating and sharing across its platform.
But, therein lies the problem as new users often give little thought to an overall plan on how they intend to organize, store and share information.
As such, sites can take on a growth of their own exhibiting a ‘sprawl’ that most certainly could be avoided if proper steps and training were in place at the initial start up. Moreover, and regardless if the responsibility falls to the a SharePoint architect, or an IT staffer, the need for security, policies and procedures trumps any quick-and-easy, “grassroots implementation” of the suite.
With the growth of file sharing sites, like DropBox and GoogleDrive, for example, workers rely on the portability of their files; this, at the expense of throwing confidential information out into the digital landscape, be it the cloud or on-premise networks.
The tools we use today today for content management come from an array of “cross technologies” with many obstacles to overcome when addressing corporate concerns for governance and security within ever-changing environments:
“Probably one of toughest jobs is being a SharePoint Admin because there are so many changes happening within organizations. Admins have to be ready to make environment changes quickly. This is where policies and procedures come in handy.”
Along with this perspective comes the need to drill down on the overall needs of the organization and initiating the right governance and security measures before SharePoint is launched.