This is the fifth post in my series about Caveman User Adoption. The first was an overview of 4 Caveman Tenets of user adoption that together create an environment where SharePoint and Office 365 will grow organically. This article is a deeper dive on the fourth and final tenet – Help that is actually helpful. The core idea here is to make changes to your support and training models to increase your users’ comfortable level. Doing this requires a strategic shift, but it is probably the most powerful of all 4 of the caveman tenets. All by itself, it can make or break your adoption efforts.
Many years ago, I came to the conclusion that thoroughly training end users on SharePoint is a waste of time for both the users and the trainer. You may or may not agree, but this is my conclusion after seeing myself and others like me be unsuccessful attempting this for many years. Read further on how I came to this conclusion and my thoughts on what works in regard to helping SharePoint users.
To make tasks simpler and easier for VisualSP subscription administrators, 3 new updates have been added to VisualSP Online:
This is the fourth post in my series about Caveman User Adoption. The first was an overview of 4 Caveman Tenets of user adoption that together create an environment where SharePoint and Office 365 will grow organically. This article is a deeper dive on the third tenet – Simple Solutions. The core idea here is to solve common pain points with something that is satisfyingly simple. Don't design the proverbial solar-powered rocket launcher with GPS and cup-holders when all the users really needed was a club. Clubs are easy to replicate. They cost little to maintain. They have a short learning curve. They are satisfying to use. When you've got a new club - everything looks like a nail.
When your end users are humming along and efficiently completing tasks because of the great custom help items you have been creating, you will likely be motivated to provide even more step-by-step guidance.
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.