InformXR Case Study

CONTEXT + MY ROLE

What is Arbor Insights?

ArborXR Insights is a tool that gives organizations visibility into what’s actually happening inside VR headsets — from time spent on tasks to learning outcomes. It enables teams to link apps, collect usage data, and sync it directly with LMS and BI platforms. Before being acquired, InformXR focused on solving this exact challenge.

At InformXR, I led the design of a dashboard feature to help developers quickly connect their VR apps to headsets and view usage analytics. This included:

Mapping the user flow for app-to-headset linking
Designing a clean, UI Data Analytics Dashboard
Integrating LMS tools to support education and enterprise use cases

Watch the video below to see the launch in action.

THE PROBLEM

XR training is accelerating, but most organizations can’t measure if it’s actually working. XR training needed a unified analytics layer give to give organizations visibility into how their VR apps are performing.

“You can deploy content, but you don’t know what’s really happening in the headset.”

Core Constraints

Developers lacked a fast, reliable way to link apps to headsets and start collecting structured data — causing delays, errors, and missed insights.

System Fragmentation

LMSs like Moodle, Canvas all use different standards (LTI, SCORM, xAPI) and are implemented differently causing VR data to remain disjointed

High Integration Costs

Custom development is often needed just to connect training data consuming time and resources

Enterprise Adoption Gaps

Security and compliance gaps preventing wider adoption

Monitoring Limitations

Designs didn’t show connection status or offer diagnostic control

Design Process

Turning LMS Complexity into Clarity

Through customer insights, industry research, and close collaboration with engineering, we reimagined how LMS integrations are designed, set up, and managed — creating a scalable foundation that simplifies the experience for both developers and enterprise teams.

‍

01

Product Requirement (PRD) Review

We kicked off the project by reviewing the product requirements with the PM to understand business goals, integration pain points, and technical constraints.

Project Scope

500+ LMS platforms, each with their own quirks
Supporting both manual and dynamic configurations (e.g., LTI Advantage vs. SCORM uploads)
Designing for both enterprise-scale users and content distributors
‍

Goals & Business Objectives

Enable seamless LMS & BI integration
Improve setup experience and reduce developer overhead
Build foundation for AI/BI insights

Enable seamless LMS & BI integration

Improve setup experience and reduce developer overhead

Build foundation for AI/BI insights

02

Exploring Current Industry Insights

We began by reviewing the product requirements with the PM to align on business goals and uncover where current integrations were falling short.

⏱️ Slow integration timelines — setup could take weeks or even years without dedicated support
🧠 High need for guidance — first-time users often needed hands-on help to integrate data
❓ Lack of feedback — users couldn’t tell if data was syncing correctly, leading to false confidence
🔌 Resource strain — integration often pulled dev teams away from higher-priority work

The Goal: Get Data synced

The path to get there...

Before we built a native LMS solution, users had to complete 50+ steps across various platforms -- most of it outside the app -- just to connect VR training data to their LMS.

03

User Research Insights

Insights from customer calls, enterprise admins, and deep dives with developers helped shape the design strategy. Since this was a highly technical landscape, we prioritized workflows that supported reliability, system compatibility, and reduced developer overhead.

Target Users

Enterprise Admins: 
Manage compliance, reporting, and training rollouts across departments. Need visibility and reliability.
Independent Software Vendors (ISVs): 
Distribute VR training at scale to enterprise clients and need plug-and-play compatibility with their LMS systems.

04

Whiteboarding & Early Sketching Sessions

Early collaboration with our PM and developers helped surface edge cases, technical constraints, and integration complexities. These sessions critical to mapping a viable core flow, aligning with business goals, and benchmarking against competitive solutions.

We reimagined how LMS connections are created and managed.

Instead of hiding this functionality inside individual app settings, we proposed moving it to a dedicated LMS tab in the main navigation, offering a centralized, scalable solution.

THE Solution

Centralized Learning Management System (LMS) Hub

I designed a streamlined setup flow enabling enterprises to connect and access training data, offering a centralized scalable solution to see and mange integrations.

View, connect, and monitor multiple connection types per app

Troubleshoot connection errors with log descriptions and Time of error

Linked to evolving external documentation (ArborXR Help Center)

Scroll here -

Access real-time visibility, actionable insights

With Data now flowing, organizations can track learner progress, session completion, and performance metrics — ready to sync with over 500 LMS and BI Tools

Value Proposition

01 FOR ENTERPRISE ADMINS

A centralized interface to manage, monitor, and troubleshoot LMS integrations across apps - streamlining compliance and reducing setup headaches.

02 FOR ISVs & CONTENT PROVIDERS

Reliable tools to deliver VR content to clients with less technical overhead, reduced reliance on devs, and scalable configuration and compatibility across LMS types.

Scope

500+ LMS platforms, each with their own quirks
Supporting both manual and dynamic configurations (e.g., LTI Advantage vs. SCORM uploads)
Designing for both enterprise-scale users and content distributors
Cleaning and restructuring the design system to be merger-ready

Constraints

LMS Fragmentation: No standard setup flow - every platform implements things differently.
Documentation Scalability: Embedding instructions for every LMS in-app would become unmanageable.
Monitoring Limitations: Legacy design didn’t show connection status or offer centralized control.
Merging with ArborXR: All designs needed to plug into an evolving ecosystem and help center infrastructure.

DEVELOPER HAND-OFF

Clear Communication for Seamless Execution

Annotated prototypes

With such a technical product, communication and adaptability were necessary. I ensured continuous alignment with the team to keep us moving efficiently.

Video walkthroughs

I created video tutorial scripts and extensive documentation - bridging technical backend demands with an intuitive, guided user experience.

Testing & Iteration

Building on User Insights

I built upon legacy insights and continuously refined the experience with internal usability testing and asynchronous walkthroughs with LMS-savvy users. Feedback loops were everywhere. And fast.

Informed Adjustments

Existing user data pinpointed where the flow was most confusing, allowing for targeted improvements in copy, layout, and error handling.

Iterative Feedback

Backend logs and customer feedback on unclear terminology informed several rounds of iteration, ensuring that every tweak improved the user journey. Collaborated with devs to reduce bugs and streamline edge-case LMS behavior.

Companion Materials