So, you’re ready for DEX?
Great.
But before you dive into dashboards, automations, or shiny scorecards, it’s essential to step back and realize something fundamental: DEX is not just a tool. It’s a mindset shift. And like any mindset shift, it requires a clear operating model to support it.
Without an experience-centric operating model, even the best DEX platform will fall short. Not because the technology is flawed, but because the organization lacks a structured approach to utilizing it. Over the years, I’ve seen this play out repeatedly across various industries, including insurance, biotech, financial services, consumer goods, healthcare, and manufacturing. The patterns are almost always the same.
Let me share a few examples.
When DEX fails to take hold
1. Limited adoption
One global insurance provider deployed a best-in-class DEX platform through a managed service provider (MSP). Technically, everything was set up perfectly. The tool collected telemetry. Automations were built. The reporting looked beautiful.
But there was one major problem: no one internally actually knew how to use it. Teams weren’t trained. Dashboards weren’t reviewed. The MSP produced reports, but the organization had no internal champions to interpret or act on them. As a result, the insights never reached the C-suite. The tool drifted into obscurity, another icon on the IT desktop, until it was eventually removed because it was deemed to have “no value.”
This is a classic early-stage pitfall: the assumption that DEX is “plug and play.” In reality, it's more in line with a continuous delivery model.
2. Difficulty justifying ROI
Another common trap: when DEX is viewed as “just another IT tool,” it becomes an easy target during budget cycles. Leaders face pressure to consolidate tools, cut overlap, or switch to “good enough” capabilities baked into larger suites.
This happens when the value of DEX isn’t clearly tied to business outcomes. If the narrative is “DEX helps IT run better,” that’s not strong enough. IT is always expected to run better. However, when DEX reflects a broader shift in operating model, toward employee productivity, trust, and experience outcomes, the stickiness grows exponentially.
Organizations that operationalize DEX see it become a strategic capability, not a line item.
3. Missing the experience boat
Some teams deploy DEX to reduce tickets and nothing more. If fewer tickets are the only success metric, you’ll miss the bigger, human-centric issues that impact experience.
For example, at one organization, DEX data indicated that device performance was satisfactory. Latency was low, CPU utilization was normal, and stability ratings were high. Yet employee feedback told a very different story. Workers felt overwhelmed by communication channels, were confused about where to find documents, and struggled with outdated workflows.
These issues would never surface in a ticketing system. When experience becomes reduced to “break/fix,” you lose sight of the broader digital journey.
4. Infighting between IT teams
The most surprising and frequent failure pattern is internal friction. If different IT teams don’t trust the DEX data, don’t understand its meaning, or don’t see themselves represented in the insights, resistance grows quickly.
A large biotech company I worked with faced this exact issue. Their engineering teams didn’t trust the DEX telemetry. When service desk teams presented data to the engineers, the engineers didn’t trust it at all, and as a result, they refused to approve or build automations based on that data.
When DEX threatens domain expertise, people push back. However, when DEX becomes a unifying layer that aligns teams with shared truths, the possibilities are endless.
The key insight: Adoption drives value
Here’s the bottom line:
DEX value scales with adoption.
The more people and teams that rely on the DEX platform, the greater its organizational value. This includes end users, service desk, applications, security, HR, procurement, and entire business units.
And that requires a strong operating model. In fact, the organizations that get the most value from DEX don’t just use the tool. They structure around it. They create roles, rituals, and rhythms that embed experience into the fabric of the digital workplace.
That structure is what I call the experience-centric operating model, and it has four components:
- Leadership
- Insights
- Impact
- Governance
Let’s unpack each one.
1. Leadership: The people side of DEX