In my previous article, I shared the five challenges that nearly derailed our virtual reality (VR) training program as we scaled from a pilot at limited facilities to deployment across North America. Here I’ll outline the framework we developed — five principles that helped us succeed where most learning technology initiatives fail.

These principles aren’t specific to VR. Whether you’re deploying mobile learning, artificial intelligence (AI)-powered training or simulation platforms, these lessons apply across learning technologies and industries.

The Scaling Gap

Most learning technology initiatives follow a familiar pattern: exciting pilot with impressive results, leadership enthusiasm and funding, attempted rollout to dozens of locations, gradual decline in adoption and quiet conclusion within eighteen months.

After deploying immersive training technology across hundreds of facilities, I’ve identified five principles that separate successful scaling from failed attempts.

Principle 1: Pilot for Scale, Not Just for Proof

Most pilots prove the concept works under ideal conditions. That’s necessary but insufficient. You must also prove you can support it at scale, in challenging and evolving conditions, with limited resources.

Organizations naturally select their best facilities for pilots — sites with strong technical support, reliable infrastructure and motivated users. This creates a dangerous illusion. The pilot succeeds because everything was optimized, not because the solution is scalable.

The better approach: deliberately test at facilities at the other end of the spectrum. Choose sites with limited technical support, unreliable connectivity, skeptical staff and high operational pressure. If your solution works there, it can work anywhere.

The key question to ask: “If we had to deploy this to fifty locations next month, what would break?” Then fix those things during the pilot instead of discovering them during rollout. Organizations that succeed at scaling spend their pilot period solving logistics problems rather than celebrating learning outcomes.

Principle 2: Obsess Over the Boring Stuff

The exciting parts are obvious: innovation, immersive experiences and improved outcomes. The critical parts are less exciting: charging stations, sanitation protocols, shipping logistics, network bandwidth and support response times.

These unglamorous operational details determine whether your program succeeds or fails at scale. In successful deployments, organizations spend more time designing equipment shipping processes than selecting technology platforms. Hygiene documentation runs longer than curriculum guides.

Every operational detail that goes wrong creates cascading failures. One damaged headset from poor packaging means a facility can’t run training for a week. Inadequate charging means only half the trainees can participate. Unclear protocols mean staff improvise inconsistently.

Budget accordingly. In our deployment, operational logistics consumed a substantial portion of our total program investment, significantly exceeding initial planning estimates. This included facility readiness assessments, standardized equipment kits, tiered technical support, hygiene protocols and equipment replacement pipelines.

Principle 3: Scale Is a Change Management Problem

Technology is the easy part. People are the hard part.

Every learning technology deployment changes how work gets done. Instructors, facility managers, operations leaders, learners — everyone’s role shifts. In deployments across various industries, the critical adoption factor is consistently frontline staff buy-in. When instructors or trainers embrace new technology, facilities succeed regardless of technical challenges. When they resist, facilities struggle even with perfect infrastructure.

Resistance takes predictable forms:

• Philosophical: “Technology can’t replace human expertise.”
• Practical: “I don’t have time to learn this.”
• Existential: “Will this make my job obsolete?”

Each requires different approaches:

• Philosophical resistance needs reframing — technology enables expertise to focus on higher-value activities.
• Practical resistance needs resource commitment — dedicated training time and ongoing support.
• Existential resistance needs role evolution — make staff the technology experts. Give them new status rather than obsolescence.

Successful organizations build advocates deliberately through champion programs, training select staff to become local experts. They communicate relentlessly with success stories, metrics updates and recognition. They allocate 15-20% of program budgets to change management, including training, communications and recognition programs.

In our deployment, facilities with engaged local champions consistently maintained significantly higher sustained usage rates — often two to three times higher — compared to relying primarily on corporate communications and mandates. The technology was identical across all sites. The infrastructure was comparable. The difference in sustained adoption was entirely attributable to local champion engagement and active change management.

Principle 4: Build Flexibility Into Your System

What works at location one won’t work identically at location 300. Geographic differences, facility constraints, operational priorities, local culture, regulations and workforce characteristics create variation.

Design your program to accommodate variation within guardrails rather than demanding perfect uniformity. Pursuing perfect standardization creates two outcomes: facilities comply superficially but disengage, or facilities innovate locally without telling you, creating unsupported shadow implementations.

The better approach: a core-plus-flex model. Define 60-70% standardized content covering fundamental skills everyone needs. Make 30-40% flexible, addressing region-specific scenarios, role-specific applications and local adaptations.

This requires infrastructure to support managed variation: centralized content libraries with version control, clear processes for local creation and quality review, regional administrative rights within defined parameters and systems to track both core and flexible content.

Organizations that acknowledge variation explicitly and manage it intentionally outperform those that pretend it doesn’t exist.

Principle 5: Commit to Sustaining, Not Just Launching

Launching a program at scale is a sprint. Sustaining it is a marathon requiring different strategies.

Launch does not equal success. Most programs are managed as projects with defined end dates. The result: programs launch successfully, six-month metrics are celebrated, then usage declines over the following year.

Sustaining programs requires ongoing commitments. Content must evolve continuously with quarterly updates. Continuous improvement processes must be institutionalized. Program management must remain dedicated even after launch. Long-term resource commitment extends to equipment refresh, content updates, platform evolution and support infrastructure.

Integration with core operations makes the difference between survival and decline. Programs that remain “supplemental” rarely survive. Integration means making technology mandatory, embedding it in standard processes and aligning it with operational metrics and leadership priorities.

Year one costs are primarily development and deployment. Years two and three have significant ongoing costs equally essential for success. Programs budgeted only for year one consistently fail in year two.

The Framework in Action

These five principles enabled sustained success in my company: many facilities actively using new systems, high engagement maintained multiple years post-launch, measurable performance improvements, documented operational value and ongoing evolution.

But this required accepting uncomfortable truths. Successful organizations invest more in logistics than innovation. They spend more time on change management than technology selection. They plan for year three before launching year one.

This feels wrong repeatedly. Shouldn’t we focus on exciting technology rather than shipping containers? Shouldn’t we standardize everything? Shouldn’t we declare victory after launch?

The answer is consistently no. Every time organizations prioritize speed over thoroughness or launch over sustainability, they create problems that take months to fix.

The Bottom Line

Learning technology can work at scale. But “works in principle” and “works at scale” remain profoundly different challenges.

Pursue learning technology if you have genuine use cases, can commit to operational complexity, have stakeholder buy-in for long-term investment and are prepared to iterate based on feedback.

Don’t pursue it if you’re chasing innovation without clear objectives, expect technology to solve people or process problems, aren’t ready for ongoing program management or if scale is an afterthought.

The question is whether your organization is ready to do the hard, unglamorous work that scaling requires.

For those facing similar challenges, I hope this framework helps you succeed faster and more efficiently than learning these lessons through trial and error.