Skip to main content

Forget SharePoint Adoption; Focus on Utilization!

SharePoint Adoption


    Many SharePoint deployments stall or are never implemented throughout an organization.  These less than desired results are often use the excuse of a lack of SharePoint "adoption".

Problems with "Adoption"


     The whole idea of SharePoint "Adoption" implies a passive approach to rolling out a SharePoint deployment and a style of "build it and they will come" philosophy.  Generally, users, especially non-technical users, continue to do what they've always done out of habit or previous training.  Users will ONLY change their day-to-day tasks or tools if they are told to do so by their boss or if they're convinced a new tool or method can save them time or solve some obvious problem, such as daily tasks.


Active Approach to drive Utilization



     Any successful SharePoint deployment has to be proactively driven on a based on providing real and current solutions.  SharePoint deployments should have a larger focus on on-going training and platform evangelism.  SharePoint admins need to actively seek out new internal customers and encourage current successful customers as "champions" to help promote the use of SharePoint.
     In general, people will continue to do the same actions out of habit and there are always tasks that can be further optimized.  The real success of SharePoint is not merely a collaborative platform, but it forces businesses to re-evaluate how they actual handle common administrative tasks, such as file management or workflow processes.


Win over the "emotional" leaders of the organization



     Many SharePoint deployments likely have "buy in" from IT and maybe from senior management, but often top C-level executives don't understand nor care about the actual application or platform to provide real business solutions.  Internally within an organization, project and team managers often depend on upper management to provide support for application platforms, while overlooking the "actual" decision-makers, the office admins.
     SharePoint admins should consider office staff, such as the office admin as the central customer.  Most executives feel they are the "leaders" of their organization, when in reality, they are in position, while in actual practice, the office admin is the one deciding how tasks should be processed.  They are often the central touch point for all work-streams and whatever they request, most likely, gets fulfilled.  By winning over the office admin to use SharePoint implicitly forces other staff to use SharePoint as well.  This approach is a more effective and organic growth of SharePoint utilization.  Quickly, the concern of SharePoint "adoption" wanes while the power of SharePoint because more obvious to the office worker.


Comments

Popular posts from this blog

SharePoint 2013 - Event ID: 8319

EventID: 8319 This is the error and this is the EVENT NAME Table  SqlIo Data _Partition27 has 443957248 bytes that have exceeded the max bytes 442857142 Which is the SQL IO Usage event To know the database name Go to Central Admin  First, we must get the logging database name The database name is in this example "WSS_Logging" Now we need to find which table is taking most of the space inside the WSS logging Database. You can check from the  SQL Server Login to  SQL Server  Management Studio -> Select your logging Database (Right Click) -> Reports- > Standard Reports -> Disk Usage by Top Tables The SQL IO Usage event We can reduce the retention period of any events (default is 14) Table SqlIoData_Partition27 has 443957248 bytes that has exceeded the max bytes 442857142 In my case its SQL IO Any way if we couldn’t know exactly which identity is causing the problem we can just Set them all to any number o...
Automating Version History Trim in All Document Libraries in a SharePoint Online Site Collection Using PowerShell Managing version history in SharePoint Online is essential for maintaining an organized and efficient document library. By setting automatic version history trim, you can control the number of versions retained for each document, ensuring that your storage is used effectively and that users can easily access the most relevant versions. In this blog post, we'll walk you through the process of setting automatic version history trim on all document libraries in a SharePoint Online site collection using PowerShell. Why Set Automatic Version History Trim? Versioning in SharePoint Online allows you to track changes to documents and restore previous versions if needed. However, without proper management, versioning can lead to excessive storage consumption and cluttered document libraries. Setting automatic version history trim helps you: Optimize Storage : By limiting the num...