Where the Magic Happens: Designing eLearning in the Age of Analytics
by Ben Digman, Learning Experience Design Manager at Vacasa
To create anything beautiful and useful, you need the right people and the right tools. Tools, without the right people, can’t create anything. And people, without the right support, are misplaced talent. So when it comes to eLearning, you need that combined creative magic to build beautiful and useful courses that will engage employees and support your company’s business needs.
That’s our eLearning philosophy at Vacasa.
Vacasa recently became the largest full-service vacation rental company in the United States. We manage over 8,000 vacation properties across 20 U.S. states and 15 countries. At our core, Vacasa is a technology and services company. We build technology in-house that we use to scale and work our magic. Vacasa is one of the most disruptive companies in this market, which has led to incredible business growth and outcomes. And, like any company focused on growth, employee training is a critical pillar of our success, especially for a company of more than 2,000 employees.
Searching for the Right Stuff
Prior to starting here, training development at Vacasa was a two-person team that used a learning management system (LMS). The platform just didn’t cut it for learner interactivity and engagement. In 2014, shortly before I joined Vacasa, the company grew 16,000%. As you can imagine, two people trying to scale with an inflexible system was less than ideal.
The LMS itself was reliable, but the fundamental problem was in developing courses and training within a limited platform instead of developing externally using stronger methods and programs. The LMS itself simply wasn’t the right space to author learning content. I had to find a way to make the process more flexible and interactive so training could be more engaging. I also needed to determine how to develop content that could scale with our incredible growth.
Because we needed our lessons and eLearning modules to be SCORM compliant as well, we started to explore solutions like Adobe Captivate, Articulate Storyline, and xAPI but we couldn’t find an eLearning developer who was strong enough in instructional design, and vice versa. We had hired some amazing people who, it turned out, couldn’t fully perform the job they were hired to do using those tools.
We decided to keep looking for a tool that would allow us to build quicker while still remaining modern and visually appealing because that quality seemed to be lacking in many of the tools in the market.
The Real Shift: Advancing eLearning Through Analytics
With all of our requirements and methodologies in hand, we finally found the solution that checked every box: Elucidat. The platform was easy to use and also allowed us to build the quality of courses that we expected.
In addition, a major benefit was Elucidat’s ability to let us develop courses for mobile. When I develop training for housekeepers, property managers, or managers in the field, I can use Elucidat for the whole process. We issue mobile phones to a large swath of our internal employees. We don’t provide computers — nor require they have their own computer — so we have to develop training that works well for those audiences on any device.
But an unexpected benefit of Elucidat was the analytics side of the equation. I like to use data to inform where we’re going and our projects’ effectiveness. But, ultimately, I’m a creative person at heart. I’m not much of a numbers guy.
Yet, I was blown away that Elucidat allowed us to immediately identify problems within our courses we didn’t even know were there. I could see that, of the 700 people who had taken a required lesson over the last year, only 10–15% actually completed it.
With our old LMS, we could see what the completion rates were, but with Elucidat, I can see exactly where people drop off. For that required lesson, I was able to see that on one page I had 500 people, but only 400 on the next. That pinpointed where the problem was so I could go in and figure out what the problem was…
Read the full story here.
