InformXR Case Study

My Role & Approach

Sole Designer, Whole Ecosystem

I was the sole designer from start to finish. I collaborated closely with PMs, devs, and customer success, but ultimately led the entire UX/UI strategy - transforming technical chaos into a scalable, user-friendly system - while leaning on essential data from the previous designer.

This historical insight gave me a head start in identifying recurring pain points and guided my design decisions.

‍

Here’s how I tackled it:

Leveraging Existing Data

Starting with detailed user feedback and internal documentation, I identified the core issues without needing to run fresh primary research.

Mapping the Landscape

I dug into LMS protocols and analyzed legacy feedback from enterprise admins and ISVs, which made it clear where users were getting stuck.

Whiteboarding & Prototyping

Iterative sketches and wireframes evolved into a guided setup flow that could flexibly accommodate both standard and edge-case LMS configurations.

Contextual Support

Rather than cramming all information into a one-size-fits-all modal, I designed and engineered inline guidance and provided direct links to LMS-specific support docs, maintaining clarity without overwhelming the user.

System Integration

Audited and refined our Figma design assets, ensuring that every UI element could integrate seamlessly with ArborXR’s broader ecosystem.

Design System Cleanup

I rebuilt the component structure to promote consistency and future scalability.

OVERVIEW

Bridging Immersive Learning with LMS Ecosystems

Immersive VR training has the potential to transform how organizations educate, certify, and upskill their workforce. But without LMS integration, it's just a black box.  An LMS (Learning Management System) is a digital platform companies use to deliver, track, and report on training programs.

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.

InformXR’s clients needed VR training data to show up in their LMS - just like every other course.
‍
“We just want our VR training to show up in the LMS like everything else.”

Simple request. Brutally complex in reality.

With over 500 LMS platforms in the wild - each with different protocols, permissions, privacy configurations, terminology, and UI disasters - this project became a deep dive into chaos, technical nuance, and UX systems thinking. This “simple request” turned into one of the most complex integration challenges I’ve tackled as a designer.

THE PROBLEM

LMS Chaos, Hidden in Plain Sight

Customers needed to connect InformXR’s immersive VR training modules to existing LMS/BI platforms, but lacked the tools or support to do so efficiently.

Fragmentation: LMSs like Moodle, Canvas, Workday, and Cornerstone all used different standards (LTI, SCORM, xAPI) and implemented them differently.
Zero consistency: Even when supporting the same protocol, each LMS had its own quirks - from backend keys to where users find their Client ID.
No centralized control: Admins had no unified view across apps or insight into whether connections were live, broken, or inactive.
Overreliance on support: With unclear flows and inconsistent terminology, even tech-savvy users frequently needed help from support teams.

This was more than a design refresh - it was about untangling a complex ecosystem where backend unpredictability and technical variation were the norm. It was a full systems overhaul - UX, dev handoff, support enablement, and documentation strategy all rolled into one.

THE Design Solution

Think Big, Start Small: Designing a System for Scale

Centralized LMS Hub

One place to see and manage all integrations.

1. View, edit, and monitor multiple SCORM/LTI connections per app

2. Real-time status labels (Success, Error, Can’t Connect, Unused)

Contextual Help System

Inline support - only when and where it’s needed.

1. Linked to evolving external documentation (connected to ArborXR Help Center)

Scroll here -

Error Handling & Permissions

Clarity at every turn.

1. Tooltip explanations for confusing terminology

2. Copy buttons for tokens and keys

DATA AND RESEARCH

Legacy Insight + Technical Immersion = Directional Clarity

Instead of running new interviews, I leaned on rich existing research and feedback collected by the previous designer. My job was to absorb, synthesize, and design forward.

‍

01

PRD Review with PM

Aligning on business objectives and pinpointing where current integrations were falling short.

Goals & Business Objectives

Enable seamless LMS & BI integration

Improve setup experience and reduce developer overhead

Build foundation for AI/BI insights

Lower support requests through better error handling

Prepare flows and components for ArborXR merger

02

Explored Competitor Tools

Analyzing how other players in the market were approaching LMS integration provided critical benchmarks and inspiration. The following was inspo from the competition:

03

Customer & Developer Insights

Although direct interviews weren’t re-run, existing insights from enterprise admins, content developers, and technical deep dives with devs on LMS protocols were invaluable.

Target Users

Enterprise Admins: 
Manage compliance, reporting, and training rollouts across departments. Need visibility and reliability. LMSs like Moodle, Canvas, Workday, and Cornerstone all used different standards (LTI, SCORM, xAPI) and implemented them differently.
Independent Software Vendors (ISVs): 
Distribute VR training at scale to enterprise clients and need plug-and-play compatibility with their LMS systems.

04

Legacy Data Analysis

Detailed data from past user feedback highlighted recurring pain points such as “Data not working,” unclear integration statuses, and the absence of centralized monitoring.

05

Whiteboarding & Early Sketching Sessions

Early sessions helped map out the labyrinthine LMS landscape and explore potential solution pathways.

06

Internal Testing & Slack Feedback

Iterative testing with LMS-savvy users and ongoing feedback via internal channels confirmed the need for a more guided and robust integration flow.

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

Ensuring an Efficient Developer Handoff

With clearly recorded videos, documented logic and specs, the hand-off to the development team was smoother, reducing ambiguity and speeding up the integration process.

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

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

Impact & Results

The redesigned flow now supports integration with 60+ apps - a robust system built to grow with emerging needs.
Reduced LMS setup support tickets
Increased successful integration/setup rate
Established foundation for future analytics layer
By merging design clarity with operational insight, InformXR is now well-poised for a seamless merger with ArborXR and future tech expansion.

Reflection

In this project, success wasn’t found in a fancy icon or modal window. It was in the holistic approach - melding UI, support documentation, and back-end technical support to transform an unwieldy process into a smart, scalable ecosystem. We weren’t simply integrating LMS systems; we were making immersive learning measurable, accessible, and downright user-friendly.