What Four Leadership Circles Revealed About Operationalizing DEX
Earlier this year, I spent time with technology leaders across four major cities – San Diego, Boston, London and Dallas, as part of four Leadership Circles.
Taken together, the conversations reinforced how far digital employee experience has matured for many organizations. The focus has shifted from understanding why DEX matters to exploring what it takes to operationalize its success.
San Diego focused on the changing role of IT and the strategic case for DEXOps. Boston explored operational intelligence, AI and measurable value. London looked at governance, accountability and organizational design. Dallas considered the leadership behaviours and execution disciplines needed to sustain transformation.
Although the emphasis varied from one city to the next, the discussions pointed to four connected priorities for organizations looking to scale and operationalize DEX.
1) Recognize the need for a different operating model
One of the things that stayed with me from the San Diego Leadership Circle was how much the demands placed on IT have changed.
Traditional IT operating models were built for a workplace where technology was less integrated, responsibilities were more clearly divided, and support was largely about responding when something went wrong. That is no longer the environment most organizations are operating in.
The digital workplace is constantly changing; employees are increasingly dependent on technology and AI is adding another layer of complexity. In that environment, siloed teams and reactive support models are struggling to keep pace. To combat this, DEX needs to be understood as a workforce-enablement capability, not simply a support function.
Collectively, the room agreed that this demands a different operating model: one designed around the experience technology enables, rather than the IT activity required to support it.
2) Design the operating model around experience
The London Leadership Circle made it clear that DEX needs to extend beyond EUC and Digital Workplace teams.
Employee experience is shaped by infrastructure, applications, security, service management, HR, Facilities, Finance and business operations. That makes cross-functional collaboration essential, and means DEX needs to operate above individual technology towers, with clear accountability for the end-to-end experience and the optimization of the Digital Workplace environment.
What stood out to me was the importance of considering this enterprise positioning at the beginning of a DEX initiative, rather than addressing it only once the technology is in place.
If responsibility remains concentrated within one team, organizations will struggle to address problems that cross technical or departmental boundaries. DEX is not an isolated IT programme, it is an enterprise capability, and the operating model needs to reflect that.
3) Build the operational capability to turn intelligence into action
Once the question of ownership had been addressed, the conversation in Boston moved to what organizations can do with the information they already have.
Many enterprises already have access to significant amounts of telemetry. The next step is using it to make sense of the wider environment - not just seeing what is happening but understanding its significance and deciding how to respond. This was the shift towards operational intelligence discussed in Boston.
AI naturally formed part of that conversation, and leaders agreed that it can play an important role in supporting diagnosis, prioritization and increasingly automated remediation. But they also recognized that technology alone cannot create operational change. Teams still need the skills, processes and accountability to act on the intelligence they receive.
The technology may make more possible, but it is how organizations use it that determines whether DEX becomes operational.
4) Embed DEXOps throughout leadership
The question of what teams need in order to act on DEX intelligence also brings the role of leadership into focus. In Dallas, there was broad agreement that leadership is essential to making DEXOps a lasting organizational capability.
Access to DEX technology isn’t a competitive differentiator. The real difference lies in whether leaders can create the conditions for it to be used consistently across teams, with clear ownership, sustained executive sponsorship and accountability for outcomes.
Closely connecting to the changing role of IT discussed in San Diego, the role of IT has evolved, and communication is now just as important as technical expertise in modern technology leadership. How leaders communicate the value of DEX and champion its adoption will ultimately determine whether it remains an IT initiative or becomes a shared capability across the organization.
What does this mean for leaders?
Although each leadership circle brought a different perspective to the discussion, together they pointed to the same conclusion. Operationalizing DEX is becoming a broader leadership and operating model conversation.
The organizations that make the greatest progress will be those that recognize DEX as more than just a technology implementation. It means rethinking how IT operates, clarifying accountability, redefining how success is measured, encouraging stronger collaboration across teams and ensuring DEX remains a leadership priority.
Providing the visibility is a great starting point but it is the leadership capability that determines what happens with that insight and whether DEX becomes embedded across the organization.
That is the shift from DEX to DEXOps.
Learn more about operationalizing DEX and explore four key DEXOps process improvements to help your IT team move beyond reactive support and embed more proactive, experience-driven ways of working.