DEX Maturity Model

In aviation, visual flight means navigating by what you can see out the cockpit window. It works in clear conditions. But it gives the pilot only a fraction of the information they need, and it fails entirely when conditions are poor. For IT organizations, the cockpit window is the help desk queue. If an employee doesn't call, the problem doesn't exist.

At Stage 1, IT operates almost entirely from the ticket. The primary data source is the support request. Response is triggered by employee escalation, not by data. Because 45% of employee technology issues are never reported, a Visual Flight organization is navigating blind on nearly half of the actual experience landscape. Resolution times may look acceptable for reported issues. The larger population of silent, unresolved friction goes undetected.

Most Stage 1 organizations believe they are operating reasonably well because their ticket metrics look good. This is the defining characteristic of this stage: the metrics being tracked look acceptable, while the metrics that matter are not being tracked at all.

At Stage 2, the organization has installed the instruments. Monitoring tools are in place. Dashboards exist. Some alerts are configured. Resolution times improve. But the pilot is still primarily looking out the window. The operational model is still fundamentally reactive: action is triggered by escalation or alert, not by the data streams now available.

The distinction between Stage 1 and Stage 2 is speed, not posture. Stage 2 organizations are faster at addressing problems that surface. They are not yet finding problems that do not surface. The help desk is still the primary mechanism for discovering employee experience issues, even if dashboards exist alongside it.

Many organizations confuse Stage 2 with progress toward instrument flight. Installing gauges is not the same as flying on them. The instruments create data. Making primary navigation decisions from that data, before employees feel the impact, is a different capability. It requires process design and operating discipline, more than technology deployment.

Stage 3 is the most significant transition in the maturity model, and the reason is specific: this is where intelligence enters the model. At Stage 2, the organization has data. At Stage 3, the organization has a model that acts on it. That is a fundamentally different capability, not a process improvement. Primary navigation shifts from the ticket queue to data streams, and the system begins recognizing patterns, correlating signals, and triggering action before any human escalates anything. Before AI, correlating signals across a large fleet was a manual task bounded by what a human analyst could hold in mind simultaneously. The data volume was the constraint as much as the analytical skill. AI-assisted investigation tools (Nexthink Workspace is one example) change what is analytically possible: the system can consume the full telemetry stream, surface patterns across thousands of devices, and present findings in plain language. The analyst's role shifts from correlation to judgment.

VFR (Visual Flight Rules) is still active. The help desk queue doesn't disappear. But the instruments are now in command. Telemetry identifies degraded experience before it generates a ticket. The IT team reaches out to affected employees rather than waiting for employees to reach out to them. Sentiment data is regularly collected and used alongside telemetry to confirm that what the data shows corresponds with what employees actually experience.

This is the stage at which a self-reinforcing cycle begins to turn. Employees notice that IT is solving problems they never reported. Trust increases. Willingness to engage with sentiment collection increases. The quality of the data improves. The ability to act on it improves. The cycle builds momentum.

Autopilot does not mean the pilot leaves the cockpit. It means the systems execute so the pilot can focus on higher-order decisions. VFR (Visual Flight Rules) and IFR (Instrument Flight Rules) are both active; the instruments are fully in use and the automation layer is now handling routine execution at scale and in near real-time without a manual trigger. Remediation scripts run automatically on affected devices. Targeted employee communications deploy without human intervention. Known failure patterns trigger resolution before they are ever reported. AI remediation agents (Nexthink Spark is one example) extend this to the employee layer directly: diagnosing device issues, executing approved fixes, and resolving problems without a ticket ever being filed.

Stage 4 organizations use historical patterns to prevent problems before they occur. Device refresh cycles are driven by experience data, not by age alone. Application deployments are modeled against the existing endpoint fleet before rollout. Network changes are tested for experience impact. The DEX program has predictive capability, more than detection capability.

Constraint-first prioritization is mature at Stage 4. The organization has a systematic way of identifying which experience improvements will generate the greatest business value, prioritizing accordingly, and measuring whether those improvements were realized. DEX spending is justified by outcomes, not by tool counts.

In aviation, situational awareness is the complete, integrated picture: position, altitude, airspeed, weather, traffic, and systems status. All active, all informing decisions in real time. No single instrument tells the full story. At Stage 5, the DEX program achieves the same integration. The cockpit window, the instruments, and the automation layer are all operating together. Endpoint telemetry, employee sentiment, application performance, AI adoption signals, and business outcomes are unified into a single operating picture that IT and business leadership share and act on together.

At Stage 5, Digital Employee Experience is a business metric, not an IT metric. The DEX program is aligned with business strategy, and experience outcomes are reported alongside financial and operational performance indicators. IT and business leadership share a common language for employee experience and a common set of expectations for what the technology investment should deliver.

AI adoption, workforce productivity, employee retention, and talent competitiveness are all informed by DEX data at Stage 5. The organization can demonstrate, in business terms, what its technology investment is producing for the people who use it. This is the ultimate destination: the stage at which DEX becomes a genuine competitive advantage rather than an IT discipline.