Many learning management systems (LMSs) are limited to tracking only basic information, such as who takes or completes a course. In most educational programs, designers and developers put together curricula with learning outcomes in mind, but have no way to prove the curricula are supporting those outcomes. The Experience API (AKA Tin Can API or xAPI) and learning record stores (LRSs) remove the constraints placed by old eLearning standards, allowing you to track and report learning experiences beyond the LMS. The Experience API opens a world of possibilities for tracking learning experiences and correlating them with real-world outcomes, but it can be difficult to make the transition from LMS to xAPI without understanding why the API is important for future learning frameworks.
Participants in this session will discuss the Experience API and the importance of the LRS. You’ll learn how these new technologies enhance freedom in the design and content of learning experiences, and how you can use them to better measure training effectiveness and learning outcomes. These measurements will allow you and your organization to invest in learning activities and programs that work and to adjust activities or programs that don’t. They can also help to validate learning and development departments.
In this session, you will learn:
- What the Experience API is
- The importance of a learning record store (LRS)
- How the Experience API and LRS open new possibilities for tracking learning experiences
- How you can use an LRS to better understand the impact that learning has on performance
Novice-to-advanced designers, developers, project managers, managers, and directors. This session assumes some level of knowledge about SCORM and the Experience API, but those without that knowledge will still find value.