This is the third post in my series about Caveman User Adoption. The first was an overview of 4 tenets that together create an environment where SharePoint and Office 365 can grow. This article is a deeper dive on the second of those tenets. Measuring adoption is an area where a lot of times we overthink things. We track the wrong things (like page hits and unique visitors for a site) and build solutions that are way more complicated than we needed in order to tell our adoption story.
This is the second post in my series about Caveman User Adoption. The first was an overview of 4 tenets that together create an environment where SharePoint and Office 365 can grow. This article is a deeper dive on the first tenet – Simple Governance Policies.
Filling out forms for a variety of purposes is a daily way of life for all end users. I have seen people struggle with filling out complex forms, hosted on SharePoint, all the time. Then of course, You, the SharePoint guy or gal gets the call to help the person. Just because the form is hosted on top of SharePoint, you become responsible for supporting the users on it as well. There is a better way...
I’ve been doing some speaking lately on the topic of user adoption. It’s an important subject, not least of which because so many times we, as an industry, get it wrong. We either ignore it (build it and they will come) or treat it like a project (training classes will be complete by August 1). In my experience, neither of those things work. Success is not rocket science, though. There are many books and posts out there that discuss adoption from more conceptual perspectives related to vision, communications, and human behavioral changes. Those discussions are certainly valid, but I plan to tackle the topic from a more functional perspective and discuss strategies and activities as they apply to the team behind the platform.
In many companies, employees engage in collaborative projects frequently. They attend multiple meetings, hold numerous conversations, move around a lot of documents, follow several processes, and end up using a variety of tools from different places.
The modern document library in SharePoint is still a work in progress. Folks still tell me at times that they flip between the classic and modern views to get the best of both. Over time, things will definitely stabilize and we'll have just one view to work with. For now though, it's best to be familiar with both.
Topics: modern document library
VisualSP founder and CEO Asif Rehmani wrote an article for CMSWire a while back on the virtues of migrating to SharePoint 2016. He explains that, while investment in any technology comes with challenges and issues, a move to SharePoint 2016 is a good one from a business output perspective.
Topics: SharePoint 2016
Does your IT team or your SharePoint Power Users get asked the same "how-to" questions all day long? The solution to this common problem may be making SharePoint Online or SharePoint 2013 or whichever version you have easier for the end user.