Count on it: if the rollout of SharePoint 2013 is left to IT without polling the key stakeholders, then the result will be a very “tightly-controlled” implementation with questionable benefit to the organization.
The other ‘extreme’ is to offer SharePoint as a “wide-open platform” without the usual regard for governance, or sharepoint data security. In fact, this strategy with the underlying “‘sprawl’” of files and documents, as well as random Wikis and proliferation of websites can only heighten concerns about SharePoint security issues
As noted in the post on EinNews, “How to Plan the Ultimate Sharepoint 2013 Rollout,” Michael McNett, a strategist for ICC, notes how the two options come with their own downside:
"One is left so open that it becomes the Wild West. The other is locked down so tight that users can't really do much of anything to make them more productive or effective so they just don't use it. Neither is an optimum case."
SharePoint enterprise users may find solace in ICC’s rollout guidelines. They include steps such as collecting input on expected requirements within the organization; highlighting priorities and what defines ‘success criteria.’
What’s more, a comprehensive look at IT’s mapping requirements, as well as establishing a governance plan tied to the business’s requirements, are crucial.
Also important, is the understanding of the ‘technical architecture’ and how IT plans to implement their strategy.
Prior to final analysis, comes the execution of the agreed on plan, making adaptations as needed while measuring the benefits and successes.
‘Training.’ obviously will become a priority, as key stakeholders are brought in to aid in adaptation throughout the organization.