DEX Glossary

A lightweight software process installed on employee devices that continuously collects telemetry data and sends it to the DEX platform. The agent is how platforms like Nexthink gather real-time endpoint metrics without requiring manual data collection. In most enterprise deployments, the agent is deployed silently via endpoint management tools and runs with minimal system resource impact. Stakeholder questions about agent overhead and privacy implications are common during DEX platform procurement.

Artificial intelligence that takes autonomous, multi-step action to resolve a problem rather than simply generating a recommendation for a human to act on. In the DEX context, an agentic AI system can detect a degraded application, diagnose the root cause, execute a remediation, verify the fix, and notify the employee, all without human intervention. Agentic AI represents the next evolution beyond automated remediation: where automation executes a pre-scripted fix, agentic AI can reason about novel problems and determine the appropriate response. Nexthink Spark is an example of an employee-facing agentic AI system.

The condition in which IT teams receive so many automated alerts that they begin to ignore or deprioritize them, including legitimate critical alerts. Alert fatigue is a common problem in environments that have deployed monitoring tools without establishing meaningful thresholds or signal prioritization. A DEXOps operating model addresses alert fatigue by tuning monitoring rules to surface only high-signal, actionable conditions and by assigning clear ownership for alert triage.

Nexthink's ITSM integration module that surfaces DEX context, diagnostics, and automated remediation options directly inside service management tools such as ServiceNow and Jira. When a technician opens a ticket, Amplify displays real-time device health, application performance, and recent experience events for that user, enabling faster resolution without switching tools or requesting information from the employee.

The automatic execution of a corrective action triggered by a telemetry alert or rule condition, without requiring human intervention. In DEX platforms, automated remediation typically involves a script or workflow that runs on the affected device: restarting a service, clearing a corrupted cache, updating a configuration, or reapplying a policy. Automated remediation is the operational layer that converts proactive detection into proactive resolution. See also: Self-Healing IT, Remediation Playbook.

A measured reference point for a metric at a defined point in time, used to evaluate whether conditions have improved, degraded, or remained stable after a change. In DEX, baselines are established for metrics such as application response time, boot duration, crash rate, and experience scores. Without a baseline, it is impossible to demonstrate program impact or detect regression. Baselines should be recalculated after significant environment changes such as a hardware refresh, OS migration, or major application update.

A Nexthink term for a targeted micro-survey delivered to a defined group of employees in context. Campaigns are triggered by conditions such as a device event, an application interaction, or a time interval, and are designed to be brief: typically one to three questions. Campaigns are the primary mechanism for collecting sentiment data in a Nexthink deployment. The term is Nexthink-specific; other DEX platforms refer to similar functionality as surveys, pulse checks, or in-app feedback.

Microsoft's branded Desktop as a Service (DaaS) offering, delivered through Windows 365. Cloud PC streams a full Windows environment from Microsoft's Azure infrastructure to any device, with no local virtualization layer required. It is licensed per user per month at fixed pricing, which distinguishes it from traditional VDI licensing models. Cloud PC is an increasingly common deployment target for enterprises replacing physical device fleets or extending access to contractors and remote workers. See also: DaaS, VDI.

Dexterity Digital's application of the Theory of Constraints to experience operations: identify the top constraint, the single improvement that would generate the greatest measurable benefit for the greatest number of employees, fix it, re-measure, and find the next one. The top constraint is determined by combining telemetry data (scale of the problem), sentiment data (severity of employee frustration), and business context (impact on critical workflows or high-value employee segments). This discipline also provides the language for communicating DEX program value to business stakeholders in business terms rather than IT metrics.

A cloud delivery model in which a complete desktop environment, including the operating system, applications, and user data, is hosted in a cloud data center and streamed to the end user's device. DaaS eliminates the need for organizations to own and manage on-premises virtualization infrastructure. Microsoft Cloud PC (Windows 365) and Amazon WorkSpaces are common examples. The employee experience in a DaaS environment is heavily dependent on network quality and data center proximity. See also: VDI, Cloud PC.

The category name formalized by Gartner for platforms and practices that measure, analyze, and improve the digital employee experience. Gartner's Magic Quadrant for DEX Management Tools uses this label and evaluates vendors across criteria including telemetry depth, sentiment collection, AI-driven analytics, automated remediation, and experience scoring. DEEM is used interchangeably with DEX in analyst research, though DEEM tends to refer specifically to the vendor market and technology category rather than to the employee experience itself.

The sum of every interaction an employee has with the technology that enables their work: from device performance at login to application reliability throughout the day to the quality of support they receive when something goes wrong. DEX is measured across three dimensions: capability (access to the right tools), reliability (how consistently those tools perform), and sentiment (how employees feel about their technology). A strong DEX enables people to do their best work. A poor DEX creates friction that is often invisible to IT.

A numeric or composite score representing the quality of the digital employee experience across a population of devices or employees. DEX scores aggregate multiple telemetry dimensions (device performance, application reliability, network quality) and sometimes incorporate sentiment data into a single index. Scores are used to track program progress over time, identify lagging employee segments or device cohorts, and communicate program value to business stakeholders. Different DEX platforms calculate scores using different methodologies; scores are not directly comparable across platforms.

The operational discipline behind a high-functioning DEX program. DEXOps defines how a DEX team is structured, how they work, what they measure, and how they connect experience data to business outcomes. The term reflects a deliberate analogy to DevOps: where DevOps bridges software development and operations through shared ownership and continuous feedback, DEXOps bridges data collection and action through defined roles, processes, and measurement cadences.

Any technology-related obstacle that reduces an employee's ability to do their work efficiently. Digital friction includes slow device performance, application crashes, authentication failures, network latency, poor tool usability, and unsupported workflows. Much digital friction is never reported: employees work around it, accept it, or give up on the affected tool. Measuring and reducing digital friction is the core operational objective of a DEX program.

The full set of technologies, applications, and environments through which employees do their work, including devices, collaboration tools, business applications, virtual meetings, and support systems. The digital workplace is the broader context in which DEX operates: DEX measures and improves the employee's experience within it. The term is often used by HR, communications, and workplace strategy teams, while IT teams typically use DEX to refer to the same domain from a measurement and operations perspective.

A defined segment of the workforce characterized by a distinct technology profile, role context, or experience risk pattern. Examples include field workers with intermittent connectivity, executives on managed devices with high availability requirements, contact center agents running latency-sensitive softphone applications, and contractors on unmanaged devices. Persona-based segmentation allows DEX programs to identify which populations are most affected by specific experience problems and to set differentiated experience targets rather than applying a single standard across the entire organization.

The collection and analysis of data generated by employee devices (endpoints): laptops, desktops, mobile devices, to understand device health, application performance, and user behavior patterns. Endpoint analytics is the primary technical infrastructure of a DEX measurement program. Platforms like Nexthink provide endpoint analytics capabilities that form the telemetry foundation of DEXOps.

Quantitative data collected automatically from devices and applications. Telemetry includes metrics such as boot time, crash rates, application response time, CPU load, memory utilization, battery health, network latency, and authentication success rates. Telemetry is continuous, objective, and scalable across an entire device fleet. It answers the question "what is the system doing?" but requires sentiment data and context to answer "what is the employee experiencing?"

A broad industry term covering the devices, applications, and infrastructure that enable employees to do their work: including laptops, desktops, virtual desktops, mobile devices, and the operating systems and management platforms that support them. EUC is the predecessor term to the DEX domain: it describes the infrastructure layer, whereas DEX describes the experience layer on top of it. Many IT teams that manage EUC infrastructure are the primary adopters of DEX platforms. EUC teams typically own endpoint management, VDI infrastructure, device procurement, and application packaging.

An approach to device and software management that maintains systems in a continuously current state through ongoing, incremental updates rather than large, infrequent refresh cycles. In an evergreen model, operating system updates, application patches, and driver updates are deployed continuously and automatically, reducing the accumulation of technical debt and the disruption caused by periodic forced upgrades. Evergreen IT is relevant to DEX programs because unpatched or outdated software is a common and measurable source of digital friction.

The difference between the digital experience employees expect and the experience they actually receive. The experience gap captures the human dimension of IT underperformance: an employee who expects an application to respond in under two seconds and consistently waits five seconds has an experience gap, even if the system is technically within SLA. Closing the experience gap is the core objective of a DEX program. The gap is measured by combining telemetry data (actual performance) with sentiment data (employee expectations and frustration). See also: XLA.

The percentage of support interactions resolved during the initial contact, without escalation or callback. FCR is a standard service desk performance metric. In the DEX context, FCR improves when agents have immediate access to device and application context at the time of the call, and improves further when self-healing automation resolves issues before employees contact the service desk at all. A high FCR rate indicates that the support model is well-matched to the types of issues employees experience. See also: Ticket Deflection, Shift Left.

A measure of whether IT systems are functioning from a technical standpoint: servers up, services available, uptime percentages, error rates within threshold. Infrastructure health is a necessary but insufficient measure of IT effectiveness. A system can be technically healthy while delivering a poor employee experience. Infrastructure health and experience health are not the same metric and should not be conflated.

The set of practices, processes, and tools by which IT teams manage the delivery and support of IT services to the organization. ITSM encompasses the service desk, incident management, change management, problem management, and asset management. Platforms like ServiceNow, Jira Service Management, and Ivanti are common ITSM systems. DEX platforms integrate with ITSM systems to enrich tickets with experience context, trigger automated remediation, and measure whether service interactions result in improved employee experience. See also: SLA, XLA.

The operational pattern in which every endpoint management task (software deployment, patching, scripts, policy enforcement, compliance checks, reboots) completes cleanly across the first 90% of the fleet, then encounters disproportionate resistance in the final 10%. The slope reflects underlying device health: the same endpoints appear at the tail of every operation because they share root health issues such as configuration drift, aging hardware, corrupted system components, or missed update chains. The last few percent typically require physical intervention: hands-on repair or a full OS reimage, driving the effort curve nearly vertical. DEX telemetry identifies the at-risk population before operations run, allowing IT to address the underlying health issues proactively rather than discovering them mid-rollout. See also: Proactive Engineer, Constraint-First Prioritization.

The average time elapsed between when an IT issue is identified and when it is fully resolved. MTTR is a standard IT performance metric. DEXOps programs aim to reduce MTTR through faster detection (telemetry alerts rather than waiting for tickets), richer diagnostic context at the point of triage, and automated remediation that eliminates manual execution steps. Proactive IT programs aim to make many MTTR calculations irrelevant by resolving issues before they are ever reported. See also: Proactive IT, Ticket Deflection.

A term from Nexthink's DEXOps guidance: the initial outcome a DEX program must achieve in order to secure further investment. An MVO should be specific, achievable, and measurable, and is typically demonstrated through a focused pilot before scaling. Related concept: Constraint-First Prioritization, Dexterity Digital's approach to deciding what to fix first once a program is operating.

The primary enterprise DEX platform used by Dexterity Digital in client engagements. Nexthink provides endpoint analytics, sentiment measurement, automated remediation, and experience scoring across large-scale enterprise device fleets. It is the technology layer through which most DEXOps operating models are executed. Nexthink is not the only DEX platform on the market, but it is the platform Dexterity Digital has deployed and optimized at scale: including one of the largest Nexthink deployments in the world.

The ability to infer the internal state of a system from its external signals. In DEX, observability means combining telemetry (device and application performance data) with sentiment (employee feedback) to understand what is actually happening in the employee experience: not just what the infrastructure metrics report. Observability is the goal of a DEX measurement program: the ability to answer the question "what is it like to be an employee in this environment today?"

An IT role specifically dedicated to finding and resolving employee experience problems before they generate help desk tickets. The Proactive Engineer works from telemetry dashboards and experience alerts rather than the ticket queue. Their success metric is not ticket resolution speed: it is issues identified and resolved before they surface as employee complaints. In some organizations this is a dedicated headcount; in others it is a defined responsibility within the existing team. The role is a defining characteristic of a Level 3 (Proactive) DEXOps operating model.

An IT operating model in which teams identify and resolve experience problems before employees are aware of them or before those problems generate support tickets. Proactive IT is enabled by continuous telemetry monitoring, automated alerting, and defined response processes. It contrasts with reactive IT, which responds to employee-reported issues after disruption has already occurred. Proactive IT is a core goal of DEXOps and corresponds to maturity Level 3 (Proactive) in the Dexterity Digital DEX Maturity Model. See also: Self-Healing IT, Proactive Engineer.

A monitoring approach that collects performance data from actual user sessions in real time, as opposed to synthetic monitoring, which simulates user activity on a schedule. RUM captures what employees actually experience: application load times from their specific device, on their specific network, during their actual working session. RUM data reflects the full variability of the production environment, including the effect of competing processes, local network conditions, and individual device state. Most DEX platforms are primarily RUM-based by design.

A documented, repeatable procedure for resolving a specific type of IT issue, either through automated execution or guided manual steps. In DEX platforms, remediation playbooks are typically encoded as scripts or workflow automations that can be triggered by a telemetry alert or deployed manually by a technician. A well-maintained library of remediation playbooks is a key operational asset for a DEXOps team: it enables consistent, fast resolution and makes institutional knowledge durable beyond individual team members. See also: Automated Remediation, Self-Healing IT.

A system capability in which devices or applications automatically detect a degraded or failed condition and execute a corrective action without human involvement. Self-healing IT combines continuous telemetry monitoring with automated remediation: when a defined threshold is crossed, such as a service failing, a process consuming excessive CPU, or a configuration drifting from policy, the system corrects itself and optionally notifies IT. Self-healing IT is a defining capability of mature DEX platforms and a key operational goal of DEXOps programs operating at Level 3 and above. See also: Automated Remediation, Proactive IT.

Employee feedback about their technology experience, collected through targeted, contextual surveys. Sentiment data captures the human context that telemetry cannot: whether employees trust their tools, whether they find IT responsive, whether frustration is building around a specific application or workflow. Sentiment answers the question "what is the employee experiencing?" and is most powerful when used alongside telemetry to provide a complete picture of the digital experience. Without sentiment, a DEX program can detect technical problems but cannot understand their human impact.

A strategy of moving issue resolution to earlier stages in the support chain: from Level 2 specialist technicians to Level 1 service desk agents to self-service portals to proactive prevention. Each step left reduces cost per resolution and reduces the time an employee is disrupted. In DEX, shifting left means ensuring that more issues are resolved before they reach the service desk, and that the issues that do reach the desk are resolved at first contact rather than escalated. See also: FCR, Ticket Deflection.

A formal commitment defining the minimum performance standard IT must deliver for a service, typically expressed in terms of availability (99.9% uptime), response time (tickets acknowledged within 4 hours), or resolution time (critical incidents resolved within 2 hours). SLAs define IT's obligations from a systems perspective. They do not measure the employee experience of those systems. An IT environment can be fully SLA-compliant while delivering a consistently poor employee experience, which is why SLAs alone are an insufficient measure of IT effectiveness. See also: XLA, Experience Gap.

See Endpoint Telemetry.

The prevention of a help desk ticket through proactive resolution, self-service tools, or automated remediation. Ticket deflection is one of the primary ROI metrics for DEX programs: each deflected ticket represents cost savings (eliminated technician time), reduced employee disruption (faster resolution than waiting in a ticket queue), and improved experience quality. Ticket deflection is measured by comparing the volume of issues detected and auto-resolved against the historical rate of similar tickets. See also: Self-Healing IT, Shift Left, MTTR.

A platform category that provides centralized management of all employee devices, including Windows and macOS laptops, mobile devices, and virtual desktops, from a single console. UEM platforms such as Microsoft Intune, Omnissa Workspace ONE, and Ivanti Neurons for MDM handle policy enforcement, software deployment, patch management, and compliance reporting. UEM is the management layer beneath DEX: it controls what is on devices and how they are configured, while DEX measures what employees actually experience as a result. See also: EUC, Endpoint Analytics.

A technology architecture in which employee desktop environments run as virtual machines on centralized servers, with the desktop image streamed to the employee's local device. VDI allows organizations to centralize desktop management, extend device life, and support remote and contractor workforces without issuing managed physical devices. The employee experience in a VDI environment is sensitive to server resource contention, session broker performance, and network latency between the user and the data center. Citrix and VMware Horizon are the leading VDI platforms. See also: DaaS, Cloud PC.

A performance commitment defined in terms of employee experience outcomes rather than system availability metrics. Where an SLA might commit to 99.9% application uptime, an XLA commits to a specific employee experience quality level: for example, that 95% of employees in a given persona rate their application experience as satisfactory or better. XLAs require sentiment data and DEX scoring to measure and enforce, which is why they are typically adopted by organizations at higher DEX maturity levels. XLAs align IT's success criteria with outcomes that matter to the business: employee productivity, not infrastructure uptime. See also: SLA, DEX Score, Sentiment.