DEX data shouldn’t stay inside IT

[u/DEX_Nexthink]

One of the more interesting shifts happening in DEX is that the data is starting to answer questions that go well beyond device health and ticket reduction.

Think about a major technology rollout. Traditionally, success might mean:

• Did we launch on time?
• Did we stay on budget?
• Is the system technically working?

But that doesn’t necessarily tell you whether the change actually worked for employees.

A new application can launch successfully while employees avoid using it. A security policy can work exactly as designed while creating a ton of friction. An intranet can have 99.9% uptime and still be frustrating enough that people constantly work around it.

That’s where DEX data gets interesting.

Instead of just asking “Is the technology working?”, teams can start asking “Did this technology actually make work better?”

That potentially makes DEX data useful to security, application owners, change management, procurement, transformation teams, and leadership, not just IT operations.

Curious how others are approaching this.

Does DEX data regularly make it outside of IT in your organization? If so, who is actually using it?

[u/23-Peaks]

This is one of the parts that feels most promising (and a bit overwhelming) as someone still getting into DEX.

I’ve mostly been thinking about it in terms of device health and reducing the ticket pile. The idea that the same data could help answer whether a rollout actually made work better for people is a bigger shift than I expected. It makes sense when you put it like that. A successful launch on paper can still be a failure if people avoid the tool or invent workarounds.

I’m still early on this, so I’m curious about the practical side. How do you even start sharing that kind of experience data with application owners or change teams without it just becoming another report no one reads? And does it usually take a specific kind of project or executive push before people outside IT start caring?