A learning ecosystem can quickly grow and evolve into a complex web of unique tools and technologies serving specific needs. So inevitably, gaining meaningful L&D insights from these disparate systems can be difficult.
The good news is that your learning analytics platform can bring all that L&D data together so you can track and explore all your learning in one place. But first, you’ll need to ensure you’re getting all the data you need and that it’s in the proper format. This blog post covers data requirements for different systems and the questions you should be asking your vendors.
L&D Data Requirements for Learning Analytics
Throughout this blog series, we’ve outlined some key principles of data integration and explored system requirements, opportunities, and quirks in many of the platforms that make up your learning ecosystem.
So whether you’re working on an integration with an existing platform, writing an RFP, or discussing learning solutions with a vendor, you’ll be able to ask the right data requirement questions for:
- Learning management systems (LMS)
- Learning experience platforms (LXP)
- Video platforms
- Survey tools
- Digital badging and credentialing services
- Observation checklist apps
- Human resource information systems (HRIS)
- BI tools
- Instructor-led training (ILT) and virtual instructor-led training (vILT)
- Augmented reality (AR) and virtual reality (VR)
- Other data sources (e-learning, intranet, learning games, assessment tools, and quizzing platforms)
5 Top Tips for L&D Data Requirements
We want to leave you with some parting words of wisdom as we wrap up this series, so here are our top five tips for successful data integrations:
- Discuss your L&D data requirements with your vendors. It’s important to make sure that your vendors understand your needs and that everyone has a clear and well-documented plan for integration from the start.
- Base your data requirements on reporting requirements. Don’t just pick the data you think would be nice to have. Take time to think about what reporting you and your stakeholders will need and define your requirements to support those needs.
- Review the documentation with your techies. It’s not uncommon for misunderstandings to arise about integration functionality when talking to non-technical salespeople. So when speaking with vendors, discuss what functionality they have to extract data. Get a copy of their documentation for your technical team or your learning analytics platform (LAP) vendor’s technical team to review.
- Use xAPI where possible, but CSVs exported via API are a good plan B. Ideally, choose products with xAPI support, but a product with CSV data export functionality can also work well. Be aware that not all xAPI implementations are good—or even usable—so be sure you know the details of the xAPI tracking before assuming it will meet your requirements.
- Consider ongoing maintenance. If a vendor is developing integration functionality for you or does not have existing clients using that functionality, make sure you discuss ongoing integration maintenance. Ensure your contract requires the vendor to maintain your integration, and talk with the vendor about how tracking for any future product features will be implemented.
Keep your data tidy with xAPI Governance.
If you’ve found this series helpful, you might also enjoy our xAPI Governance guide. It talks about how to set up processes and procedures to ensure the quality and compatibility of your data as you bring it all together from various sources.
About the author
Subscribe to our blog