Many learning teams invest in xAPI only to end up with "data exhaust": lots of statements, but no trusted answers to the questions leaders actually ask. Completion rates still dominate reporting, dashboards get debated instead of used, and measurement becomes an afterthought rather than a design input.

In this case study session, we will share a practical, repeatable approach for turning learning activity data into decision-ready evidence. You will see how we moved from stakeholder questions to a measurement plan for Eli Lilly, including designing an xAPI statement strategy that stayed usable across learning modalities and systems, established data quality and Articulate Storyline authoring practices so reporting could be trusted, and translated analytics into data leaders could act on. We will focus on the process, templates, and lessons learned that you can apply with your own ecosystem—whether you are just starting with xAPI or trying to scale past a pilot.

You will actively participate through a short "measurement-to-xAPI mapping" exercise, peer discussion, and a dashboard storyboard activity you can take back to your team.

In this session, you will learn: 

• How to translate a business or performance question into a measurement plan (KPIs, data sources, and success criteria)
• A simple pattern for designing and documenting xAPI statements so your data stays consistent and reusable at scale
• Lightweight data quality checks and governance practices that make dashboards credible (and reduce rework)
• How to storyboard a data story that moves stakeholders beyond completions to evidence of impact
• The top pitfalls we encountered—and what we would do differently—so you can avoid them

Attendees should be familiar with common L&D measurement practices (completion rates, surveys, basic dashboards) and the idea that learning data can come from multiple systems (LMS/LXP/content tools). We will briefly define xAPI/LRS terminology, but the session focuses on measurement planning, data collection, Articulate tool authoring, and communicating insights, not coding or specific data formats.