<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=15552&amp;fmt=gif">
Top
1.800.628.2783
1.800.628.2783
April 2013
Issue Map
TD Magazine

Three Reasons to Use the xAPI to Capture Learning

These days most employee learning happens through unstructured situations and various tools, including the Internet, employees' own mobile devices, and social learning platforms such as Yammer. How can training and development professionals track and aggregate all of this learning in a consistent, reliable way?

Enter the Experience API (xAPI), an e-learning software specification that allows learning content and systems to record and track all types of learning experiences.

Advertisement

According to John Delano and Ali Shahrazad, authors of the April 2013 Infoline, "Using the Experience API to Track Learning," it's worth looking into the xAPI for your organization if you are unhappy with:

  • what you currently know about employee effectiveness and performance based on the effort and money you put into creating and deploying training
  • the fact that you have little knowledge and understanding of what is being learned in the natural workflow of your internal customers
  • the way technology is hindering your ability to support and understand learning and development in your organization.

For the xAPI to be effective in your organization, you will need to assess design tools and systems, employee adoption, and leadership readiness.
These tips were adapted from the April 2013 Infoline, "Using the Experience API to Track Learning." For more information, go to www.astd.org/infoline.

About the Author
The Association for Talent Development (ATD) is a professional membership organization supporting those who develop the knowledge and skills of employees in organizations around the world. The ATD Staff, along with a worldwide network of volunteers work to empower professionals to develop talent in the workplace.
Be the first to comment
Sign In to Post a Comment
Sorry! Something went wrong on our end. Please try again later.