PRISM Video: Why XR projects fail or stall (“Pilot Purgatory”) - Barriers between Inception and Implementation

Sam del Greco is a vastly experienced Senior Researcher (XR - Virtual, Augmented and Mixed Reality), XR lead at IMR (Irish Manufacturing Research, a member of Eirmersive), who founded IMR’s XR department ~8 years ago. During those years he has delivered demos to thousands of people and scoped 70+ projects, including the completion of 7 multi-company XR projects with ~35 companies. IMR is hardware-agnostic and focuses is on best-fit solutions in terms of devices. It works at mid-level TRL (3–6), focusing on implementation challenges rather than off-the-shelf solutions.

The following is a summary of Sam’s presentation, which you can watch in full below

Core Theme

Why XR projects fail or stall (“Pilot Purgatory”) - Barriers between inception and implementation, and why projects often die after the pilot phase.

Key Challenges

1. Technology vs Implementation

   • Hardware is mature, accessible, and performant (high TRL).

   • Main barrier: implementation—integrating XR into existing processes and systems.

2. Return on Investment (ROI)

   • Hard to quantify benefits and justify cost to senior management.

   • Projects need clear objectives and measurable outcomes to avoid premature cancellation.

3. Integration

   • XR cannot exist in isolation; must link to existing workflows, infrastructure, and data streams.

   • Example: Training must integrate with HR systems for certification tracking.

4. Scope Creep

   • Lack of clear objectives leads to chasing “shiny” features or new devices.

   • Edge cases and exceptions consume budget unnecessarily.

5. Content Issues

   • Biggest blocker: Companies rarely have XR-ready content.

   • Three approaches: Capture (real-world objects), Create (digital modelling), Convert (optimise existing CAD/BIM files).

   • XR Digi project (€400k) focuses on content creation and conversion.

6. Data Availability

   • Digital twins need live data—but many companies lack sensors or IoT infrastructure.

   • XR projects often require parallel IoT/data initiatives.

7. Adoption & Culture

   • Engage end-users early; consider ergonomics, health & safety, and IT/security constraints.

   • Example: Network restrictions can block remote assistance apps.

   • Involve managers and secure a senior sponsor to champion the project.

8. Hardware Risks

   • Avoid vendor lock-in; choose hardware-agnostic solutions.

   • Past examples: Companies stranded after device manufacturers ceased support.

Practical Advice

• Define clear wins and objectives early.

• Plan content first—everything in XR is content or data.

• Secure senior sponsorship for continuity.

• Stress-test use cases—don’t assume XR is the right solution.

• Consider update cycles—XR training must match the pace of process changes.

• Factor in IT, HR, and health & safety from the start.

Closing Insight

XR is often an enhancement of existing processes (e.g., training), not a completely new paradigm. Success depends on:

• Clear ROI,

• Integration with existing systems,

• Robust content strategy,

• Organisational readiness and cultural adoption.