What I've discovered across organizations, cultures, and acquired whiffs for change management scentors, is that SharePoint upgrades are lightning rods for taking in new thinking and taking out your enterprise trash
What we call things and how we define them will and does vary widely based on language, geography, culture and industry. Were there an international set of terms that on a global scale we all accepted and embraced, some of this issue might be lessened
In many of the discussions I have had regarding this topic, the biggest barrier seems to be one of culture and trust. I often hear “How do I know the employee is really working and not just playing golf?”
Our biggest challenge is culture change. More specifically, changing from a paper-centric worldview to one of electronic records and a totally new way of working with metadata and not folders
Introduction (BYOD | MDM) Remote workers and internal or onsite workers empowered with “ bring your own device ” (BYOD) policies can push the boundaries of IT and the typical IT-driven culture. A lot of IT organizations are playing catch-up around governance and their information management policies and have pushed back on BYOD due to the added complexity it brings and ultimately forces specific polices to be approved
SharePoint 2013 provides for four main community categories as follows: Communities of practice: Community for a group of people who share a unique skill, role or profession to share experiences, best practices and advice Communities of purpose: Community that exists to accomplish a specific goal, need, or mission Communities of interest: Community consisting of a group of people who share a common interest or passion for a topic or domain Communities for social interaction: Community consisting of a group of people who primarily interact for the sake of interaction and socializing to build new relationships based on a common characteristic, culture or geography commonality Within the four main community categories, there are also four main types of communities as follows: Private community: Available to only specified members Permissions allow for the site to only be shared with specific users or group There are no approval settings available Closed community: Everyone can view the content of the site, but only members who have approved requests for membership can contribute Permissions allow you to grant visitor permissions to everyone within the organization so that they can view the site and request to join The approval settings allow you to enable access requests on the site Open community with explicit join settings: Everyone can view the site and can automatically join to contribute to the site Permissions allow you to grant visitor permissions to everyone within the organization so that they can view the site and automatically join as a member The approval settings are set to auto-approval to allow users to automatically join the site Open community without explicit join: Everyone can contribute to the community Permissions allow you to share the site with everyone in the organization and grant member permissions so the new users can all contribute The approval settings do not provide for a join button so be visible and the auto-following for new members is not enabled There is a centralized community portal template that can be created as a central hub for showcasing the various communities within your organization to your user base
There is also a new and growing “App” culture that is causing organizations to take a good look at their underlying application and custom development processes, standards, and available environments that directly coincides with the moving pieces described above which can make for a perfect storm of major technology decisions that need to be made that will affect the company for at least the next 3 or 4 years
8403 Colesville Rd #1100Silver Spring, MD 20910USA
Phone: (301) 587-8202Toll free: (800) 477-2446Fax: (301) 587-2711Email: hello@aiim.org
JoinBenefitsLearn More
About UsTerms of Use