Evidence Base

DEX Research & Data

DEX is not a preference: it is measurable, and the evidence for its business impact is well-documented. This page compiles the key studies, surveys, and data points that establish the case for investing in employee experience programs.

Last reviewed November 2026

What Organizations Cannot See

The foundational challenge in DEX is not fixing known problems: it is discovering the problems that employees never report. These studies quantify the scale of that gap.

56%
of employee technology issues are never reported to IT

Nexthink’s 2023 State of the DEX Industry survey, conducted by Vanson Bourne, found employees report only 44% of the technology issues they experience, so more than half never surface as help desk tickets. Employees absorb friction silently: they work around broken tools, accept degraded performance, and stop expecting technology to work reliably. The result is a systematic undercount of the actual experience burden employees carry.

This finding has direct implications for how IT organizations interpret their ticket metrics. Low ticket volume is not the same as a healthy experience. It may indicate an environment where employees have learned not to report problems: a significantly worse outcome.

The trend is moving the wrong way. In Nexthink’s earlier Experience 2020 survey, employees reported 55% of their issues; four years later the figure had fallen to 44%.

Reporting is getting worse, not better

Employees reporting the technology issues they experience, as measured in two Nexthink and Vanson Bourne surveys

Employee reporting of technology issues, 2019 to 2023 In the 2019 survey, 55 percent. In the 2023 survey, 44 percent. Reporting fell by 11 points in four years. 0%20%40%60% 55% 44% 2019 survey 2023 survey Experience 2020 Report State of the DEX Industry
An 11-point drop in four years. Axis starts at zero. Sources: Nexthink / Vanson Bourne, The Experience 2020 Report (fieldwork late 2019) and State of the DEX Industry Report (2023).
Nexthink / Vanson Bourne, State of the DEX Industry Report (2023), 1,000 IT decision makers and 1,000 office workers. Earlier comparison: Nexthink / Vanson Bourne, Experience 2020 Report, 3,000 IT professionals and end users across the United States, United Kingdom, France, and Germany.
14
negative digital experiences per employee, every week

Telemetry, not survey answers. Nexthink's 2025 analysis of anonymized data from more than 20 million endpoints across 474 businesses counted device crashes, application glitches, and slow load times as employees actually experienced them. The average negative event lasts just under three minutes, and the number of disruptive events per week was almost identical across industries.

Because this is measured at the endpoint, it sidesteps the reporting gap entirely: it shows what employees live with whether or not they ever call the help desk.

A typical week: 14 interruptions nobody reports

The measured weekly average, spread across a working week. The mix of event types is illustrative.

Mon
App crashSlow loadVPN drop
Tue
FreezeSlow loadSign-in
Wed
App crashCall qualitySlow load
Thu
FreezeVPN dropSlow load
Fri
App crashPrinter
14 negative experiences per week ~167 sec each, on average ~39 min lost per employee per week, before refocus time
Count and duration: Nexthink, Cracking the DEX Equation (September 2025), telemetry from more than 20 million endpoints. Weekly minutes are calculated from those two averages (14 x 167 seconds). Event labels are examples, not measured proportions.
Nexthink, Cracking the DEX Equation: The Annual Workplace Productivity Report (September 2025). Aggregated, anonymized telemetry from organizations largely in the early stages of DEX management.
1 in 3
employees report that technology issues affect their ability to do their job every day

Daily technology friction is not an edge case: it is a widespread, chronic condition across enterprise workforces. Most of it never generates a ticket. It accumulates as background noise: the slow application, the unreliable VPN, the authentication failure that resolves after three attempts. Each incident is small enough to absorb. Collectively, they represent significant lost productivity and growing employee frustration.

Nexthink / Vanson Bourne (2020). Survey of 3,000 IT professionals and end users.

The studies above measure how much goes unreported. They do not ask why. The original Nexthink and Vanson Bourne research did not break the reasons down, and no single study since has produced a complete, ranked list. Several recent surveys come close, and together they point the same way: most issues go unreported because reporting does not feel worth the effort, not because employees distrust IT.

What employees say they do instead of reporting

Each bar is a separate survey question. Read them side by side, not as parts of one total.

Decided an IT problem was not worth reporting82%
Buchanan Technologies, 2026 (850 US office workers)
Saw a ticket marked resolved while the problem remained80%
Buchanan Technologies, 2026
Avoid contacting IT at least sometimes because it feels like more effort than it is worth76%
Standley Systems, 2026 (500 desk workers)
Used their own tool or AI instead of IT support72%
Buchanan Technologies, 2026
Solve IT problems themselves because it is faster than waiting (approximate)~40%
Ivanti, 2025 Digital Employee Experience Report

Different surveys, samples, and wording; percentages are not additive or directly comparable. Full sources are listed below each finding.

82%
of office workers have decided an IT problem was not worth reporting

Half of them make that call more than half the time. The same survey found that 72% had used their own tool or AI instead of IT support, and 26% described that as their usual response. Most of these workers did not lack confidence in IT: 81% said they were completely or fairly confident their support team would solve their problems.

The implication matters for anyone who manages from the ticket queue. When small problems are routinely judged not worth a ticket, a healthy dashboard can sit alongside a frustrated workforce.

Buchanan Technologies survey, reported by IT Brief (October 2026). 850 US non-IT office workers who had contacted IT support in the previous three months, surveyed through Pollfish.
76%
of desk workers avoid contacting IT at least sometimes because it feels like more effort than it is worth

58% said their first response to a technology issue is to try fixing it themselves. Reporting competes with simply getting on with the work, and for a problem that costs a few minutes, reporting usually loses.

Standley Systems, 2026 Office Technology Report (April 2026). 500 desk-based workers, surveyed through Pollfish in February 2026.
80%
have seen a ticket marked resolved while the problem remained

Past experience shapes future reporting. When a ticket is closed without a real fix, or an employee has to explain the problem from scratch at every handoff (55% said this happens most or every time), the lesson learned is that reporting does not pay off. Nearly a quarter of those with a "resolved" ticket that was not fixed were still relying on a workaround or had given up on the issue.

~40%
of employees solve IT problems on their own because it is faster than waiting on the help desk

Speed drives self-help. Ivanti's chief security officer described the resulting shadow IT as coming from employees' desire to do their jobs when the official route is not enabling them to.

Five reasons, in plain terms. Read together, the research suggests five recurring reasons employees do not report technology problems. This grouping is Dexterity Digital's synthesis; no single study measured all five.

  1. It does not seem worth a ticket. The problem feels too small, too brief, or too routine.
  2. Reporting takes effort. Finding the portal, describing the issue, and waiting for a response feels slower than living with it.
  3. Self-help is easier. Employees fix it themselves, ask a colleague, or turn to an AI tool, so IT never hears about it.
  4. Past tickets did not pay off. Closed-but-not-fixed tickets and repeated explanations teach people not to bother.
  5. It feels normal. In the 2020 Nexthink and Vanson Bourne research, 61% of respondents agreed that IT downtime is an accepted norm in their organization. Once friction is normal, it stops being reportable. Source: Nexthink / Vanson Bourne, The Experience 2020 Report.

The common thread is process friction, not distrust. That is why visibility has to come from the endpoint and from employees directly, not from the ticket queue: the queue will always miss what people decide is not worth reporting.

These are vendor-sponsored surveys with different samples and question wording, so the percentages are directional and should not be combined. Verify against each original report before citing them in proposals.

470,000
hours lost per business, per year, to poor digital experience

Nexthink's 2025 telemetry analysis puts the average annual cost of poor DEX at about 470,000 hours per business, roughly the work of 226 full-time employees. It also found that every 10-point increase in an organization's DEX score returns an average of 22 productive minutes per employee each week, and that retail, healthcare, and financial services lose about 1.7 times as much time as the technology sector.

Nexthink, Cracking the DEX Equation: The Annual Workplace Productivity Report (September 2025). Based on more than 20 million endpoints across 474 businesses.

The Cost of Poor Digital Experience

The productivity impact of digital friction is measurable: and significant. These findings help translate the DEX conversation from IT metrics to business outcomes.

28 min
lost each time an employee has an IT problem

Nexthink's Experience 2020 survey found employees lose an average of 28 minutes every time they have an IT-related problem. IT decision makers estimated employees hit about two issues a week, which Nexthink put at nearly 50 hours a year. Because employees said only just over half of their issues are reported, Nexthink estimated the real figure is close to 100 hours, or two work weeks, per employee per year.

These figures capture time spent dealing with problems directly. They do not include the time it takes to regain focus afterward, or the effect on deadline-sensitive work.

Nexthink, Experience 2020 Report press release (April 2020). Survey by Vanson Bourne of 1,000 IT decision makers and 2,000 employees. The two-work-weeks figure is Nexthink's estimate from the survey results.
$25M
Nexthink's estimate of the annual cost of IT downtime for a 10,000-person organization

Nexthink reached this figure by assuming about two hours of IT downtime per employee per week and an average US salary of $48,672, which works out to roughly $2,400 per employee per year. It is a salary-cost estimate, not a measured result, and it excludes help desk labor, remediation, device replacement, and attrition.

To model your own organization with current inputs, use our cost-of-friction calculator, which uses Nexthink's 2025 telemetry averages and lets you set your own salary cost.

How Employees Feel About Their Technology

Employee sentiment about workplace technology affects engagement, retention, and willingness to use new tools, including AI.

49%
of employees say their company's technology makes them feel less productive

Nearly half of the enterprise workforce believes their technology is actively working against them, not for them. This sentiment is not a perception problem, it is a signal. It indicates that technology deployments are not meeting the needs of the people they were designed to serve. When employees feel less productive because of technology, they disengage from IT-led initiatives, reduce their willingness to report problems, and become resistant to new tools, including AI.

Nexthink / Vanson Bourne (2020). Survey of 3,000 IT professionals and end users.

Why DEX Determines AI ROI

Deploying AI at scale requires a healthy digital foundation. Organizations that have not invested in DEX measurement are poorly positioned to realize the productivity outcomes AI promises.

Practitioner perspective. We have not found published research that quantifies the link between DEX maturity and AI tool results, so this section states our reasoning rather than a statistic. AI tools need compute, memory, and network capacity that many enterprise endpoints were not configured to deliver. Without endpoint visibility, IT cannot tell which devices are ready for AI workloads, which employees will have a degraded experience from day one, or which deployments are at risk. Organizations with mature endpoint visibility and structured sentiment programs can find usage barriers early (device performance, network constraints, application conflicts), fix them, and reach the right employees with credible guidance. DEX measurement is not a prerequisite for buying an AI tool. It is a prerequisite for deploying one well.

A note on sources: The data on this page reflects published research from Nexthink, Vanson Bourne, and related industry studies. Where specific figures are estimates or extrapolations, this is noted. All statistics should be verified against current primary sources before use in proposals, presentations, or financial projections. Research methodology details and primary source documents are available from Nexthink at nexthink.com.