Many companies that deploy digital tools find it hard to attain intended business outcomes. Often, the problem is not the tools but the low and incorrect usage of them. The problem is poor digital adoption.
If your digital workplace is heavily based on teamwork, you can take full advantage of one of the most powerful services within the Office 365 suite: Office 365 Groups.
Now, here is a common scenario: you tell your team members to make use of a tool; they open the tool but don't know where to start. This happens even after everyone has gone through sessions of training.
Not knowing how to use a tool is one of the greatest barriers to better usage.
Wouldn't it be great if there was a timeline of 'adoption enhancing activities' to follow when rolling out a new SharePoint-based intranet (or relaunching an existing one)? I mean, let's get real and talk about concrete things instead of vague concepts.
Team collaboration, task automation, data security, employee productivity, and return on investment are the common business pursuits. Toward those goals, companies have deployed SharePoint and Office 365.
However, all these business goals are only attainable to the extent that employees actually use the platforms. At the same time, SharePoint and Office 365 adoption remains a major challenge to organizations of all sizes. The idea of "build it; they will come" seldom translates into reality.
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.
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.
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.
For those of you wondering if a migration to SharePoint 2016 makes sense, we've got the inside scoop. VisualSP is teaming up with Bill Baer to explain the benefits of this latest release, the investments Microsoft has made to improve SharePoint, and why a migration might make sense for your organization. We are hosting Bill on February 22, 2017, 12 – 1:00pm EST, live on the web.
Wouldn't it be nice to have a timeline of 'adoption enhancing activities' to follow when rolling out a new SharePoint-based intranet (or relaunching your existing one)? I mean, let's get real and talk about concrete things instead of vague concepts. Let's do this!
Topics: SharePoint Adoption