11
Susan Jacobs Best Practices for Strategic Integration of xAPI with Your LMS with TJ Seabrooks, Hugh Seaton, and Megan Torrance

Best Practices for Strategic Integration of xAPI with Your LMS

  • Upload
    others

  • View
    4

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Best Practices for Strategic Integration of xAPI with Your LMS

Susan Jacobs

Best Practices for Strategic Integration of xAPI with Your LMS

with TJ Seabrooks, Hugh Seaton, and Megan Torrance

Page 2: Best Practices for Strategic Integration of xAPI with Your LMS

Copyright© Copyright 2018 Adobe Systems Incorporated and The eLearning Guild. All rights reserved. Adobe, the Adobe logo, and Captivate are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. The eLearning Guild and the eLearning Guild logo are either registered trademarks or trademarks of The eLearning Guild in the United States and/or other countries. All other trademarks are the property of their respective owners.

Contact InformationAdobe Systems Incorporated 345 Park Avenue San Jose, CA 95110

[email protected]

The eLearning Guild 120 Stony Point Road, Suite 125 Santa Rosa, CA 95401

[email protected]

AuthorsSusan Jacobs with TJ Seabrooks, Hugh Seaton, and Megan Torrance Note: The contributors to this paper do not necessarily endorse Adobe’s products or the products of any other company.

ReviewersAshwini Jaisim and Nipun Sharma, Adobe Systems

Page 3: Best Practices for Strategic Integration of xAPI with Your LMS

1Best Practices for Strategic Integration of xAPI with Your LMS

It has always been a breeze for L&D to track compliance and record the completion of formal instructor-led training and

eLearning courses with a learning management system (LMS). However, a great deal of modern workplace learning occurs

informally, and not all of that content is delivered through an LMS.

The Experience API, which was called Project Tin Can when it debuted and now is commonly referred to as xAPI, has

revolutionized the practice of tracking learning activity. Unlike SCORM, the ubiquitous standard in eLearning, xAPI facilitates

seamless tracking of an almost unlimited array of learning experiences, tools, and applications—allowing organizations to

collect more robust data about their learners’ activities. This has become more crucial as firms strive to document informal

learning. In practical terms, xAPI enables a firm to track the fact that an employee watched a work-related video on YouTube,

read a pertinent industry blog post on his or her mobile phone, or consulted with a subject matter expert to solve a problem.

Although it is still young, xAPI has had a profound impact on the learning industry. Within a relatively short period of time,

protocols have been drafted and many vendors now offer varying degrees of support for xAPI. The open-source initiative has

captured the imagination of instructional designers and developers, who are incorporating the game-changing specification

into their work. It has also piqued the curiosity of L&D leaders interested in leveraging xAPI data to more accurately assess

employee performance.

INTRODUCTION

Page 4: Best Practices for Strategic Integration of xAPI with Your LMS

2Best Practices for Strategic Integration of xAPI with Your LMS

xAPI enables L&D leaders to look at training and performance by topic or domain, rather than by tool or vendor. “This means

that all safety training and activity or all leadership development activity can be assessed at once—rather than looking at chat

activity separately from activity that occurs in the workflow or within the LMS,” notes an industry expert who has been at the

forefront of the xAPI movement. “Using xAPI presents a huge opportunity to better serve our organizations’ needs as L&D

professionals, since many of our existing tools don’t provide the data needed to measure the impact of learning activity.”

This paper explores the promise of xAPI, and provides L&D professionals with practical suggestions and guidelines on how to

strategically integrate it at their enterprises.

xAPI in a nutshell At its most basic level, xAPI is a language that creates statements describing learners’ activities. It uses the syntax of

Someone→Did→Something. As Marc Rosenberg points out in his Learning Solutions article “The xAPI Breakthrough,” a typical

statement might be “Josh watched a video,” “Louise reviewed a technical manual,” “Olivia performed a simulation,” or “David

passed an assessment.”

Figure 1: xAPI syntax, courtesy of Marc Rosenberg

Statements such as these, which can describe an infinite number of experiences and knowledge-sharing activities, are

kept in a learning record store (LRS) where they can be retrieved, evaluated, and analyzed. The information can then be

combined with more traditional training data from the LMS to offer a more comprehensive portrait of an employee. The result,

according to Rosenberg, is that “training records begin to look more like résumés, and the focus shifts from test scores to

accomplishments.”

Page 5: Best Practices for Strategic Integration of xAPI with Your LMS

3Best Practices for Strategic Integration of xAPI with Your LMS

Comparing the APIsAPI is an acronym for application program interface. It is the way programs, systems, or apps communicate. The most popular

API in the learning and development industry is SCORM, an acronym for Shareable Content Object Reference Model.

SCORM was released in 2001 and has played a pivotal role in enabling the eLearning industry to develop into a thriving,

interchangeable marketplace. There is widespread support for the stalwart specification among vendors.

SCORM handles only structured data, which usually arrives in classic “rows and columns” format. It offers details about

completion of courses, scores, and feedback. In contrast, xAPI is an unstructured data specification that permits users to

collect and analyze unstructured data about employees’ informal activities. With xAPI, almost any kind of information can be

collected and tagged in a predefined manner, making it a dynamic and powerful analytic tool.

SCORM and xAPI share some important similarities. Functionally, both enable L&D to capture and store employee-related

learning activity. And xAPI is shepherded by the US federal government’s Advanced Distributed Learning (ADL) initiative, just

like SCORM was.

Adobe Captivate Prime and xAPI

Adobe Captivate Prime has always had a learning record

store (LRS) and the ability to accept xAPI statements. With

the introduction of xAPI into the LMS, the advantages of

leveraging the LRS have increased, as has the ability to

provide a uniform interface for reporting and tracking

various activities.

The following points encapsulate the ways in which Prime

has integrated xAPI into the learning management system

to allow for an enhanced user experience. A future-facing

integration, Prime offers customers:

1. Unified learning tracking interface. Prime leverag-

es xAPI to provide tracking and resume support for

a variety of content types, including those that are

traditionally not trackable, such as externally sourced

videos, virtual classes, ILTs, or documents.

2. Ability to track learning outside the LMS. Prime

offers an interface to its well-developed LRS that

allows organizations to track all learning experiences,

including those outside the LMS, by using xAPI. These

learning activities do not need to originate within

Prime, and Prime does not need to have information

about the activities in advance.

3. Tighter LMS and LRS integration. Traditional LMSs do

not allow the tracking of external learning (formal or

informal), or they have difficulty with integration and

implementation, and therefore with tracking comple-

tion and success. Prime provides a hybrid model that

allows these activities to be created as stubs for the

original activities, but these will be marked as “com-

plete” automatically when the activities are completed

and the corresponding xAPI statements are sent to the

Prime LRS.

4. Analytics and learner engagement. It is difficult to

measure learner engagement and gain meaningful

analytics about learner behavior. It is even more chal-

lenging when an LMS straddles the formal and infor-

mal learning worlds. Prime’s informal learning is built

on Prime’s xAPI and LRS. Looking forward, admins

will be able to download a full data dump containing

all the informal and social activities of the learner and

mine it to gain further insights. Admins will be able to

accurately track learner behavior across both worlds.

Page 6: Best Practices for Strategic Integration of xAPI with Your LMS

4Best Practices for Strategic Integration of xAPI with Your LMS

Although it is an older specification, SCORM may be perfectly adequate for organizations that are primarily interested in

creating and tracking compliance-based learning and do not need to connect multiple systems, or that do not offer or track

learning outside of the LMS.

But SCORM has limitations, which is why it may not be the best solution for a lot of contemporary organizations today. SCORM

does not allow L&D to record:

• Activities other than eLearning

• More information about the learning than a test score, answer choices, time spent, bookmark, score, and completion

status

• Activity occurring outside the LMS or offline

• Activities of multiple people at once

• Results from multiple learning experiences

• Business results alongside learning data

Advantages of xAPI Some say xAPI was not designed to replace SCORM—or any other API, for that matter. (A “competing” specification, the IMS

Global Caliper specification, is similar to xAPI and generally enforces a more standardized data set than xAPI, but it is a closed

specification as opposed to open-source xAPI, and is narrower in its scope—focusing primarily on education.)

Others have touted xAPI as the “next generation” SCORM. That is debatable, but the xAPI specification is certainly more

flexible and robust than its predecessors. It does not need to be launched from within an LMS; a browser session is not

required; it can track a wider set of activities; and it removes the single-learner limitation.

While it’s possible to remove these limitations with other APIs, bespoke or otherwise, xAPI is unique in that it provides built-in

functionality that make it easy for a user to transition to using xAPI after using previous eLearning technologies. For example,

xAPI includes support for the CMI data model, which allows one to use xAPI to pass data that would have previously been

recorded with SCORM. The user could combine that SCORM-like data with new data points and event tracking unique to xAPI.

xAPI can be used to track all sorts of data, including learning experiences that occur in the digital world. This is important as

more learners turn to video, social networks, group forums, and virtual and augmented reality for the information they need

to do their jobs. xAPI can report data from sensors, robots, bots, and other high-tech equipment. It can also transmit data

on interpersonal interactions provided by peers and colleagues, such as observations, mentoring systems, and electronic

performance support systems. Finally, it can incorporate data from human capital systems such as HRISs, as well as LMSs and

LRSs inside and outside of the organization.

Page 7: Best Practices for Strategic Integration of xAPI with Your LMS

5Best Practices for Strategic Integration of xAPI with Your LMS

In essence, L&D can track virtually everything with xAPI, and then mine the data for valuable insights. With xAPI, learning

leaders can:

• Learn more about the learning experience—not just eLearning

• Understand more about performance

• Correlate learning with performance

• Offer more targeted training

• Support performance more effectively

• Use data to learn with others

• Compare performance and learning across learners

• Deliver and track training outside of the LMS

There are other benefits. As with SCORM, xAPI enables organizations to switch vendors, add new tools, and swap out

platforms with relative ease. And xAPI can also be used to link multiple platforms within an organization. For example, if the

marketing department uses one LRS and sales relies on another, the L&D LRS can connect the two—providing insights into

learner behavior across the ecosystem.

Industry pundits report very few downsides to xAPI. “xAPI provides a framework by which two systems can talk to each other

about the things a person does. Its flexibility is both a blessing and a curse,” explains one expert. “xAPI can be used to express

anything, which can be challenging from a consistency and reporting point of view.”

Do you need an LMS and an LRS? The answer to this question depends on the unique needs of your organization; however, learning management systems and

learning record stores serve different functions. Many organizations will discover that they need both types of systems, or at

the very least, an integrated solution that accommodates the two.

In general, the LMS focuses on formal learning assets and materials. It can:

• Host eLearning

• Offer ILT and vILT class sessions

• Manage instructor schedules, rosters, etc.

• Manage offline materials

• Keep track of employees’ formal learning transcripts

• Assign training based on employee demographics

• Assign required and compliance training, and track completions

• Generate reports

Page 8: Best Practices for Strategic Integration of xAPI with Your LMS

6Best Practices for Strategic Integration of xAPI with Your LMS

Assignment and delivery of content to learners is a key function of the LMS. An LRS does not do this. Although it may have

other capabilities, its primary role is to record and store events. The LRS receives valid data statements, stores them, and

returns them when queried—often providing richer and more flexible reporting and visualization capabilities than an LMS.

Organizations can opt for stand-alone systems or a crossover approach. A growing number of prominent LMS providers are

bundling LRSs into their packages or incorporating LRS functions into their systems. xAPI is one way to create a consistent

communication framework between an LMS and an LRS, but some platforms offer built-in integrations, and others make it

easy for L&D to simply upload a CSV file with the data.

Moving forward, it is clear that xAPI will be an integral part of a healthy ecosystem of interconnected technology infrastructure.

As Pamela Hogle notes in her Learning Solutions article “xAPI Primer”: “Neither xAPI nor the LRS replaces the LMS; xAPI will

work with a compatible LMS and track formal training that takes place within the LMS. Within an xAPI ecosystem, the LMS and

LRS can coexist.”

Strategic integration of xAPI with an LMSAn organization has several options for incorporating xAPI as a component of its learning ecosystem:

• An LMS with an integrated conformant LRS will accept statements from eLearning hosted on the LMS, as well as

external learning record providers

• An LMS that sends xAPI data about its transactions to an LRS will manage training and then send data about that to

the LRS

• An eLearning course that sends SCORM to the LMS and xAPI to an external LRS satisfies the LMS’s need for

compliance and tracking, along with the organization’s need for more flexible data

If you work with outside eLearning vendors and plan on incorporating xAPI, make sure that their offerings are xAPI

conformant. Select or require that their vendor ecosystem generate xAPI statements.

When integrating xAPI with an LMS, the primary question to consider is: Are you looking for the LMS to receive statements

(thereby serving as an LRS) or do you want the LMS to send statements about learner activity to another LRS? cmi5 is a

standard that sits on top of xAPI. It defines the manner in which credentials are shared with a launched course, and defines the

data that must be sent back from the course.

When sending statements, it is important to determine which activities in the LMS actually matter. Do you care to record the

fact that a learner logged in? Or that they launched a course, answered a question correctly, and exited? Do you want to track

which screens they visited? The bottom line is that the outfitting of any activity to support xAPI must begin with an analysis

of what actually matters to the organization. It ends with, “Can the LMS record those things and send corresponding xAPI

statements?”

Page 9: Best Practices for Strategic Integration of xAPI with Your LMS

7Best Practices for Strategic Integration of xAPI with Your LMS

Problems one might encounterAlthough the goal is always a seamless integration, problems inevitably arise. Following are some examples of problems one

might encounter when attempting to integrate xAPI with existing systems:

• Rejection of statements. The LMS may not follow the xAPI specification. It may reject statements from outside the

LMS, or otherwise modify them to fit a predefined data model.

• Poorly formatted statements. If an LMS can ingest an xAPI file, it should be able to use xAPI. There might, however,

be issues with how the xAPI statements are served and formatted. An LRS requires well-formatted xAPI statements in

order to work.

• Limited functionality. The LMS reporting functionality may be too limited to handle data from the unstructured xAPI

stream.

• Insufficient support. LMS vendors are quick to say that they support xAPI; however, learning leaders must clarify

what they mean by xAPI support. Bear in mind that the xAPI industry is still young. Many LMSs do not fully support

xAPI.

• Technical glitches. The learning record provider does not provide an identifying key (person identification) that

allows for matching the data of a single person sent in from multiple sources.

10 important considerations 1. Before even considering xAPI, identify the learner experience you’re trying to create and the workflow required to

support it. This will provide context into the way you’ll use xAPI and help answer questions that provide insight into

your ideal integration.

2. Think about what xAPI data sources (including launched content or LMS events) you plan to use.

3. Decide how learners will navigate the system. If they log in to the LMS, will xAPI statements automatically be sent to

the LRS?

4. Evaluate security. It is crucial that the LRS is integrated with the LMS in a secure fashion.

5. Consider credentials. Can you generate single-use LRS credentials, or do you have to use hard-coded LRS credentials?

6. Decide on what verbs to use. Communities of practice are looking to standardize this, but it remains a huge challenge

at present.

7. How will you get the systems to work together? The easiest solution is an integrated system. Otherwise, will you be

able to bring the LMS and the LRS vendors together?

8. Make sure that your learning record providing tools are identifying users in the same way so that all the incoming data

can be matched.

9. Emphasize your need for flexible reporting in the LRS on all parts of the xAPI activity statement.

10. Select an LRS (stand-alone or part of an LMS) that meets the ADL conformance specification.

Page 10: Best Practices for Strategic Integration of xAPI with Your LMS

8Best Practices for Strategic Integration of xAPI with Your LMS

Adobe’s LMS solution, Captivate Prime, provides support for xAPI. Click here to learn more about Adobe Captivate Prime.

Adobe’s LMS Solution: Captivate Prime

What does the future hold for xAPI?Although many visionaries and early adopters have jumped on board the xAPI bandwagon, the movement is still young and

growing. “I’m seeing real traction with big organizations and real projects using xAPI,” says one consultant. She notes more

client RFPs from the government and private sector specifying xAPI, and more product and platform vendors offering varying

degrees of xAPI support. She has also noticed a decided uptick in registrations for xAPI boot camps and workshops.

Yet L&D needs to be ready for an xAPI future. “Almost no one in the learning ecosystem is used to the level of feedback and

data analysis that xAPI makes possible, so the biggest single obstacle to xAPI adoption is demand,” says an xAPI advocate.

“L&D teams aren’t used to producing this level of report, and their internal clients aren’t used to asking for it. This is why

you see LRS providers talking so frequently about the business case(s) for xAPI—they are in a position to educate the entire

industry on the power of data.”

He adds that L&D is going through this big-data revolution later than other industries. “The marketing industry went from very

limited, structured data to virtually unlimited, unstructured data in the 2000s, and it completely changed both the advertising

and media industries,” he says. He predicts that the big-data revolution will shake up the L&D industry in a similar manner.

Page 11: Best Practices for Strategic Integration of xAPI with Your LMS

9Best Practices for Strategic Integration of xAPI with Your LMS

ABOUT THE AUTHORS

Susan Jacobs is a senior editor with The eLearning Guild. She has a deep-rooted interest in

and passion for education and technology. Prior to this position, she was a senior content

producer at Bright Business Media, a leader in the meeting and events industry. Susan is a

graduate of Northwestern University’s Medill School of Journalism.

SUSAN JACOBS

TJ Seabrooks is CEO of Rustici Software, which helps companies conform to eLearning

standards like SCORM and xAPI. Prior to that, he served as director of products. TJ has

been influential in the evolution of eLearning standards; he played an integral role in the

contribution to two Broad Agency Announcements (BAAs) awarded to Rustici and has been

a key contributor to the xAPI specification since 2012. TJ has an MS in computer science from

Vanderbilt University and a BS in computer science from Mount Vernon Nazarene University.

TJ SEABROOKS

Hugh Seaton is CEO of Aquinas, which he founded in 2015 with the mission of creating the

next generation of personalized learning delivery software. A passionate fan of data and data

science, Hugh founded the New York xAPI Meetup and has spoken extensively about xAPI and

its value in modern learning. Prior to Aquinas, Hugh ran training at Connecticut’s largest startup

incubator while holding an adjunct professorship at Sacred Heart University. Hugh spent the

first 18 years of his career in marketing and advertising, running data-driven campaigns in the

US and China. Hugh holds an MBA from Columbia University.

HUGH SEATON

Megan Torrance is the CEO and founder of TorranceLearning, which helps organizations

connect learning strategy to design, development, data, and ultimately performance. She

has over 25 years of experience in learning design, deployment, and consulting with or-

ganizations large and small. TorranceLearning projects have won IELA and Brandon Hall

(2012, 2014, 2016) awards, the 2014 xAPI Hyperdrive contest at DevLearn, and back-to-back

eLearning Guild DemoFest Best in Show awards (2016 and 2017). A graduate of Cornell

University with a degree in communication and an MBA, Megan is a published author and a

frequent speaker at conferences nationwide.

MEGAN TORRANCE