Here are a few EPC Group best practices I want to share with around driving SharePoint's end user adoption and keeping it relevant to maximize your ROI
It really brought my attention back to something that I hadn’t thought about in a while and that is the lag between identification and adoption
In order to do these things correctly, and to ensure adoption, an organization has to possess a broad array of skills that fall into the following categories: IT Pro Information Architecture Software Development Evangelist & Trainer The IT Pro’s job is to set up and configure the platform which requires, at a minimum, a firm understanding of hardware, virtualization, Windows Server, IIS, Active Directory, SQL Server and SharePoint (configuration and administration)
Thereโs also a duality between the power userโs role as SharePoint consumer and producer โ someone on the hook for scaling the productivity gains of a wider adoption. Power users straddle the line between trying anything once and building on what works
1 Comment - no search term matches found in comments.
Time Three factors were mentioned here, but for our purposes, the innovation’s rate of adoption is the one factor that is most important
Technical features are taught in isolation without regard to the greater concerns of Information Architecture, eDiscovery, Scalability, Reuse/Extensibility, User Adoption, etc. In my experience, the type of education that is most impactful in terms of setting organizations up for success with SharePoint is aimed at IT and business Decision Makers and provides a broad understanding of how SharePoint maps to various business-technical needs. The focal point should be: How SharePoint fits into the business objectives of the organization at the enterprise level What organizational structures need to be put in place to define and support the use of SharePoint (e.g. a Governance Committee, User Adoption Strategy, Content Taxonomy) How various SharePoint features can be used and/or combined to replace or complement existing systems and processes (e.g. the Corporate Intranet, Line of Business Applications, legacy ECM solutions) At a minimum, I think Decision Makers need to understand, at a high level , what the following features are and how they might be used to solve common business-technical problems: Various options for implementing Web-based Data Input Forms and Workflows in SharePoint Document Libraries, Document Sets, the Document ID Service and Remote Blob Storage Enterprise Content Types & the Managed Metadata Service Content Organizer, Drop-off Library and Content Organization Rules In-place Records Management in SharePoint 2010 Integration Support including Business Connectivity Services (BCS), the Business Data Catalog, SharePoint Web Services, etc
Recent AIIM Research reveals that the rapid adoption rate for SharePoint has created confusion in many organizations regarding their future strategy for information management,particularly those with existing and established ECM (Enterprise Content Management), RM (Records Management) and BPM (Business Process Management) systems
It’s best to measure adoption in a generic survey, rather than one that is dedicated to SharePoint, and we did this in the Process Revolution Industry Watch in February. 83% of the largest (5,000+) companies have SharePoint in use but only 45% of 10-500 employee organizations
2 Comments - no search term matches found in comments.
Many speakers were talking about how business drivers should be moving the adoption of SharePoint and not coming to the solution beforehand (something that I’ve discussed at length )
Outside of Powershell entities need to be added one at a time. Can you imagine adoption of MMS one tag at a time?
8403 Colesville Rd #1100Silver Spring, MD 20910USA
Phone: (301) 587-8202Toll free: (800) 477-2446Email: hello@aiim.org
JoinBenefitsLearn More
About UsTerms of Use