If you look at the overall budget to implement a best practices SharePoint 2013 or 2010 implementation, is 5% of it around driving end users to actually use SharePoint?
I believe this is something missing from the community and I am hopeful this will help in the development of not only SharePoint end-user training for your organization but Train-the-Trainer and Power User Training for which EPC Group finds so valuable to ensuring a succesful SharePoint Implementation
no search term matches found in comments.
Power users self-identify as stakeholders...Power users straddle the line between trying anything once and building on what works
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
This is certainly true in terms of the myriad things a non-technical user can do in SharePoint without writing code
Heading into SharePoint Saturday #4 | Boston tomorrow and as always, I look forward to partaking in the festivities and learning. For the “un-enlightened”, SharePoint Saturdays is a unique phenomena in the technology world like no other I have experienced. In a nutshell, a bunch...
For example, end-users will be managing Web sites while power users will be managing a range of Web site administrative tasks including the security of the information that resides in SharePoint
The latest AIIM Industry Watch report is out today, and it has some great insights into the love/hate relationship between SharePoint and its users
Doug, interesting study but perhaps even more interesting are the reasons behind the numbers. 55% of the respondents felt it was the right decision while 8% felt it was as poor decision – compare that to your third bullet in the “Key Findings” that 68% of the implementation decision were made by IT while only 8% were made by the user community (actually, in “Job Roles” p. 21, only 6% of the respondents were LOB exec., dept. head or process owner
When SharePoint 2013 and/or Office 365 is architected without future phases in mind you also risk the possibly of losing buy-in and support from the user base which can stifle the momentum and long-term adoption of the platform
When speaking with the business side of a SharePoint 2013 or Office 365 Hybrid initiative (and even in Azure) you would have to detail what exactly an "App" was and with those users in organization's with previous experience in either SharePoint 2007 or SharePoint 2010 and Web Parts, with the ability to add an "App Part" to a Site site definitely can get confusing for end users and Power users alike. The Power Users have asked, "So I can add a new document library to a site but that is done via selecting a new App and then I add that to the page in the same way I added a document library "web part" (i.e