Scott Tompkins

Enterprise LMS Modernization

2 min read

Enterprise LMS Modernization

I architected and led the modernization of critical subsystems in an enterprise learning management system, replacing fragile legacy integrations and improving platform maintainability—all while the system continued serving enterprise customers with contractual uptime requirements.

Context

The LMS I modernized was NetDimensions’ product—the same platform I’d worked on during my years at NetDimensions, but now from a different angle. Both NetDimensions and PeopleFluent were subsidiaries of Learning Technologies Group (LTG), and through an internal reorganization PeopleFluent inherited responsibility for the NetDimensions LMS. I joined PeopleFluent already knowing the product intimately from the mobile and content side, which gave me an unusual vantage point for the modernization work ahead.

The LMS had been in production for years, accumulating both institutional wisdom and significant technical debt. The SCORM interface—the integration surface through which all learning content communicates progress and completion—had become fragile after years of patches and edge-case handling. Extending it for new content standards was increasingly risky. Meanwhile, other subsystems needed modernization, but enterprise customers depended on the existing behavior. A rewrite wasn’t an option.

What Changed

I replaced the legacy SCORM interface with a modern SCORM Engine implementation, improving content compatibility across SCORM versions and reducing the maintenance burden on a critical integration surface. For broader modernization, I introduced strangler patterns and feature flags—isolating legacy subsystems behind clean interfaces, building replacements behind feature flags, validating in production, then cutting over. This let us modernize incrementally without the risk of a full rewrite or disruption to active customers.

The platform became more maintainable, more extensible, and more resilient to future change—without a single big-bang migration.

Why It Matters

Enterprise systems that serve real customers can’t stop for rewrites. The ability to modernize incrementally—to improve a system while it’s running—is one of the most valuable engineering capabilities in enterprise software. This work proved that careful, disciplined modernization strategies produce durable improvements without the risks that make stakeholders (rightly) nervous about legacy refactoring.

  • PeopleFluent — Role context and technical details
  • NetDimensions — Earlier SCORM/xAPI experience from the mobile and content side